MCP Integration

Claude Code setup

Configure the local stdio MCP server for Claude Code via intent setup or a manual settings.json entry.

Automatic setup

intent setup

Choose Claude Code when prompted. This registers the intentdocs MCP server in ~/.claude/settings.json and also writes twelve .claude/commands/intent-*.md slash commands (/intent-next, /intent-implement, /intent-review, /intent-document, /intent-test, /intent-status, /intent-done, /intent-sync, /intent-propose, /intent-context, /intent-decide, /intent-example) that give Claude Code guided entry points into the same workflow the CLI drives. See CLI Reference → Project setup for the rest of what intent setup does.

Manual configuration

If you'd rather wire it up yourself, or need to configure it per-project instead of globally, add this to ~/.claude/settings.json (or a project-level MCP config):

{
  "mcpServers": {
    "intentdocs": {
      "command": "npx",
      "args": ["intentdocs", "mcp"],
      "cwd": "/path/to/your/project"
    }
  }
}

cwd matters — the server resolves your project's sync config from .intent/config.json relative to it, the same way the CLI does.

Choosing a tool mode

{
  "mcpServers": {
    "intentdocs": {
      "command": "npx",
      "args": ["intentdocs", "mcp", "--mode", "core"],
      "cwd": "/path/to/your/project"
    }
  }
}

Add --mode core or --mode standard to args to shrink the tool list Claude Code has to keep in context. See Tools & resources for exactly which tools each mode includes — the default, if you omit --mode, is all.

Verifying it's connected

Ask Claude Code to read a resource directly, e.g. "read intentdocs://project/status" — no command needed, since resources are auto-discovered once the server is registered. If that doesn't return anything, check that .intent/config.json exists in the directory Claude Code was launched from (or that cwd in the MCP config points at it).