How do I install the Atlas MCP skill?

Run npx skillmds@latest add tomevault-io/atlas-mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Atlas MCP safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Atlas MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Atlas MCP free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Atlas MCP?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Atlas MCP by tomevault-io — Agent Skill

Name: Atlas MCP
Author: tomevault-io

File contents

Runtime projection of SKILL_MCP_001. Edit the canonical, not this file. Source of truth: platform/sdlc/13_skills/active/SKILL_MCP_001.playbook.md

SKILL_ATLAS_MCP_001 — ATLAS MCP Server

Purpose

Use this skill when the user needs ATLAS capabilities exposed to Claude Code or Codex via the Model Context Protocol (stdio transport). The MCP server lives at apps/backend/mcp/ and imports directly from apps/frontend/shell/src/lib/ using relative paths — no Next.js dependency, no ATLAS server required to be running.

Pre-Gates

Confirm node_modules — if apps/backend/mcp/node_modules/ is missing, surface the install command before claiming the server is runnable.
Confirm atlas/src/lib is intact — the MCP server imports localAtlas.ts, atlas-data.ts, and three graph modules. If these files move or are renamed, update the imports in apps/backend/mcp/src/index.ts.
Never run npm install automatically — present the command to the user.

Server Start Steps

Install deps (user runs once):
```
cd apps/atlas-mcp && npm install
```
Dev mode (tsx, no compile step):
```
cd apps/atlas-mcp && npm run dev
```

Production build + run:

cd apps/atlas-mcp && npm run build && npm start

Tool Reference

Tool	Required params	What it calls (source: `src/core.ts`)
`atlas_graph_query`	none (mode defaults to full)	`buildGraph()`, `localGraph()`, `shortestPath()`, `contextPacket()`
`atlas_skill_get`	`skill_id`	`findSkillFile()`, `readText()` — reads `13_skills/active/SKILL_*.yaml` + `.playbook.md`
`atlas_trigger_route`	`phrase`	`routePhrase()` → `execFileSync("python3", ROUTER_CLI, phrase, "--json")`
`atlas_context_compile`	none (scope defaults to full)	`compileContext()` — direct filesystem scan
`atlas_knowledge_search`	`query`	`skillFiles()` + `skillRecord()` + `nodeMatches()`

Claude Code Config

Add to .mcp.json in the repo root (or ~/.claude.json for global):

{
  "mcpServers": {
    "atlas": {
      "command": "npx",
      "args": ["tsx", "apps/backend/mcp/src/index.ts"],
      "env": {}
    }
  }
}

Or after npm run build:

{
  "mcpServers": {
    "atlas": {
      "command": "node",
      "args": ["apps/backend/mcp/dist/index.js"],
      "env": {}
    }
  }
}

Forbidden Actions

Do not switch to HTTP/SSE transport without explicit user request.
Do not use @/ path aliases from inside apps/backend/mcp/ — use relative paths only.
Do not assert graph or skill state without calling the appropriate tool.
Do not run npm install automatically.

Required Outputs

apps/backend/mcp/package.json
apps/backend/mcp/tsconfig.json
apps/backend/mcp/src/index.ts — stdio MCP server with 5 tools
SKILL_ATLAS_MCP_001.yaml + SKILL_ATLAS_MCP_001.playbook.md
Registry + router wired (skills.registry.yaml total updated, trigger_router.yaml target + intent added)
.mcp.json config block
Install command surfaced for user

Validation

After wiring registry + router:

python3 25_automation/validate_skill_router_integration.py

Expected: PASS: skill router integration (180 active skills — all registered and routed)

Source: Bigdez55/SOAE-Dashboard — distributed by TomeVault.

---name: atlas-mcpdescription: ATLAS MCP Server — Claude Code & Codex Integration — Use this skill when the user needs ATLAS capabilities exposed to Claude Code or Use when this capability is needed.---> **Runtime projection of `SKILL_MCP_001`.** Edit the canonical, not this file.> Source of truth: `platform/sdlc/13_skills/active/SKILL_MCP_001.playbook.md`# SKILL_ATLAS_MCP_001 — ATLAS MCP Server## PurposeUse this skill when the user needs ATLAS capabilities exposed to Claude Code orCodex via the Model Context Protocol (stdio transport). The MCP server lives at`apps/backend/mcp/` and imports directly from `apps/frontend/shell/src/lib/` using relativepaths — no Next.js dependency, no ATLAS server required to be running.## Pre-Gates1. **Confirm node_modules** — if `apps/backend/mcp/node_modules/` is missing, surface the install command before claiming the server is runnable.2. **Confirm atlas/src/lib is intact** — the MCP server imports `localAtlas.ts`, `atlas-data.ts`, and three graph modules. If these files move or are renamed, update the imports in `apps/backend/mcp/src/index.ts`.3. **Never run npm install automatically** — present the command to the user.## Server Start Steps1. Install deps (user runs once): ```bash cd apps/atlas-mcp && npm install ```2. Dev mode (tsx, no compile step): ```bash cd apps/atlas-mcp && npm run dev ```3. Production build + run: ```bash cd apps/atlas-mcp && npm run build && npm start ```## Tool Reference| Tool | Required params | What it calls (source: `src/core.ts`) ||------|-----------------|---------------------------------------|| `atlas_graph_query` | none (mode defaults to full) | `buildGraph()`, `localGraph()`, `shortestPath()`, `contextPacket()` || `atlas_skill_get` | `skill_id` | `findSkillFile()`, `readText()` — reads `13_skills/active/SKILL_*.yaml` + `.playbook.md` || `atlas_trigger_route` | `phrase` | `routePhrase()` → `execFileSync("python3", ROUTER_CLI, phrase, "--json")` || `atlas_context_compile` | none (scope defaults to full) | `compileContext()` — direct filesystem scan || `atlas_knowledge_search` | `query` | `skillFiles()` + `skillRecord()` + `nodeMatches()` |## Claude Code ConfigAdd to `.mcp.json` in the repo root (or `~/.claude.json` for global):```json{ "mcpServers": { "atlas": { "command": "npx", "args": ["tsx", "apps/backend/mcp/src/index.ts"], "env": {} } }}```Or after `npm run build`:```json{ "mcpServers": { "atlas": { "command": "node", "args": ["apps/backend/mcp/dist/index.js"], "env": {} } }}```## Forbidden Actions- Do not switch to HTTP/SSE transport without explicit user request.- Do not use `@/` path aliases from inside `apps/backend/mcp/` — use relative paths only.- Do not assert graph or skill state without calling the appropriate tool.- Do not run `npm install` automatically.## Required Outputs1. `apps/backend/mcp/package.json`2. `apps/backend/mcp/tsconfig.json`3. `apps/backend/mcp/src/index.ts` — stdio MCP server with 5 tools4. `SKILL_ATLAS_MCP_001.yaml` + `SKILL_ATLAS_MCP_001.playbook.md`5. Registry + router wired (skills.registry.yaml total updated, trigger_router.yaml target + intent added)6. `.mcp.json` config block7. Install command surfaced for user## ValidationAfter wiring registry + router:```bashpython3 25_automation/validate_skill_router_integration.py```Expected: `PASS: skill router integration (180 active skills — all registered and routed)`---> Source: [Bigdez55/SOAE-Dashboard](https://github.com/Bigdez55/SOAE-Dashboard) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Atlas MCP