IDE Integration

Specific configuration instructions for each supported IDE.

Why This Matters

Each IDE stores MCP configuration in a different location with slightly different formats. This guide shows exactly where to put your ChorumAI configuration.

Claude Code (Claude Desktop)

Claude Desktop is Anthropic’s official desktop app with built-in MCP support.

Configuration File Location

Configuration

Create or edit the config file:

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx"
      }
    }
  }
}

Verification

1. Restart Claude Desktop
2. Start a new conversation
3. Type: “List my ChorumAI projects”
4. Claude should use the chorum_list_projects tool

Cursor

Cursor is a VS Code fork with AI-first features and MCP support.

Configuration Location

Settings → Features → MCP Servers

Or edit directly:

• macOS/Linux: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json

Configuration

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx"
      }
    }
  }
}

Verification

1. Restart Cursor
2. Open the MCP panel (usually in the sidebar)
3. Verify “chorum” appears as connected
4. Test with: “What invariants exist for this project?”

Windsurf

Windsurf is Codeium’s AI-powered IDE with MCP support.

Configuration Location

Check Windsurf’s documentation for the current config path, typically:

• macOS/Linux: ~/.windsurf/mcp.json
• Windows: %USERPROFILE%\.windsurf\mcp.json

Configuration

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx"
      }
    }
  }
}

Verification

1. Restart Windsurf
2. Check the MCP status indicator
3. Test with a query about your project patterns

VS Code + Continue

Continue is an open-source AI coding assistant that runs as a VS Code extension.

Configuration Location

Continue stores its config in:

• macOS/Linux: ~/.continue/config.json
• Windows: %USERPROFILE%\.continue\config.json

Configuration

Add the MCP server to your Continue config:

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx"
      }
    }
  }
}

Verification

1. Reload VS Code (or restart)
2. Open the Continue sidebar
3. Verify the MCP server is connected
4. Test with: “Query my project memory for authentication patterns”

Common Configuration Options

Using a Specific Project

To default to a specific project, add it to your config file:

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx",
        "CHORUM_DEFAULT_PROJECT": "proj_abc123"
      }
    }
  }
}

Debug Mode

To see detailed MCP communication logs:

{
  "mcpServers": {
    "chorum": {
      "command": "npx",
      "args": ["chorum-mcp", "--debug"],
      "env": {
        "CHORUM_API_TOKEN": "chorum_xxxxxxxxxxxxx"
      }
    }
  }
}

Troubleshooting by IDE

Claude Code

Cursor

Windsurf

VS Code + Continue

Testing Your Connection

After configuration, test with these prompts:

1. List projects: “What ChorumAI projects do I have?”
2. Query memory: “What patterns does my project use for error handling?”
3. Get invariants: “What rules must I never break in this project?”
4. Get context: “What’s the tech stack for my current project?”

If the agent successfully uses ChorumAI tools, you’re connected!

Security Reminder

• Don’t commit your token — Add your IDE’s config file to .gitignore
• Use separate tokens — One per IDE makes revocation easier
• Review pending learnings — AI proposals require your approval

Related Documentation

• MCP Overview — What MCP is and why it matters
• Setup Guide — Token generation and initial setup
• Tools Reference — Detailed tool documentation