Docs / usage / mcp-claude

Wire into Claude Code

The MCP server runs locally and talks to your agent over stdio. Same shape works for Cursor, Continue, Aider, or any MCP-capable client — only the config file location differs.

Two servers ship today. Pick one:

• Generic Skill Wiki MCP — 1 tool (prime_query). Works against any compiled corpus. Use when starting from an empty corpus.
• Frontend domain MCP — 5 tools (prime_query, prime_resolve, prime_intent, prime_validate, prime_compile). Bundled with the frontend-design corpus.

1 · Generic Skill Wiki MCP (1 tool)

For a fresh / empty corpus. Exposes only prime_query.

# Clone & install
git clone https://github.com/skill-wiki/prime-system.git
cd prime-system
bun install

# Note the absolute path to the server entry:
#   <repo>/packages/mcp-server-core/src/index.ts

Then point your client at bun /abs/path/to/prime-system/packages/mcp-server-core/src/index.ts with PRIME_DIR pointing at your compiled corpus directory.

2 · Frontend domain MCP (5 tools)

Bundled with the curated frontend-design corpus. Adds resolve / intent / validate / compile on top of query.

# Clone the corpus repo
git clone https://github.com/skill-wiki/prime-corpus-frontend.git
cd prime-corpus-frontend
bun install

# Server entry lives at:
#   <repo>/app/mcp-server-frontend/index.ts

Point your client at bun /abs/path/to/prime-corpus-frontend/app/mcp-server-frontend/index.ts. The corpus this repo ships with is at compiled-v3-final/; use that as your PRIME_DIR.

3 · Editor configs

Claude Code — project-scoped (.mcp.json at project root)

{
  "mcpServers": {
    "prime": {
      "command": "bun",
      "args": ["/abs/path/to/prime-system/packages/mcp-server-core/src/index.ts"],
      "env": {
        "PRIME_DIR": "/abs/path/to/your/compiled/corpus"
      }
    }
  }
}

For the frontend MCP, swap args to ["/abs/path/to/prime-corpus-frontend/app/mcp-server-frontend/index.ts"] and point PRIME_DIR at .../prime-corpus-frontend/compiled-v3-final.

Claude Code — global (~/.claude.json, top-level mcpServers key)

{
  "mcpServers": {
    "prime": {
      "command": "bun",
      "args": ["/abs/path/to/prime-system/packages/mcp-server-core/src/index.ts"],
      "env": {
        "PRIME_DIR": "/abs/path/to/your/compiled/corpus"
      }
    }
  }
}

Claude Desktop (macOS — ~/Library/Application Support/Claude/claude_desktop_config.json)

{
  "mcpServers": {
    "prime": {
      "command": "bun",
      "args": ["/abs/path/to/prime-system/packages/mcp-server-core/src/index.ts"],
      "env": {
        "PRIME_DIR": "/abs/path/to/your/compiled/corpus"
      }
    }
  }
}

Cursor

# Cursor settings → MCP servers → Add
Server name: prime
Command:     bun
Args:        /abs/path/to/prime-system/packages/mcp-server-core/src/index.ts
Env:         PRIME_DIR=/abs/path/to/your/compiled/corpus

Continue (~/.continue/config.json)

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "bun",
          "args": ["/abs/path/to/prime-system/packages/mcp-server-core/src/index.ts"]
        },
        "env": {
          "PRIME_DIR": "/abs/path/to/your/compiled/corpus"
        }
      }
    ]
  }
}

Test the connection

Restart your client. Once connected, ask the agent something the corpus knows:

"What atoms in the corpus describe a 'pan sauce'? Use prime_query."

The agent should return a list of atoms, each with a kind and projection path, and may follow up by calling Read to load specific bodies.

Troubleshooting