Implementation: How to enable MCP tools in Claude Code extension without bre...

Documentation for Sessions

⚙️ Implementation: How to enable MCP tools in Claude Code extension without bre...

📋 Decision Context

Question:

How to enable MCP tools in Claude Code extension without breaking Cursor's MCP integration?

Task: Setup mcp-gograb-ai for Claude Code CLI while preserving Cursor functionality

🎯 Decision Made

Chosen:

Create workspace-local .claude/mcp.json configuration separate from Cursor's global ~/.cursor/mcp.json

Options Considered:

Wait for native Claude Code MCP support
Use REST API endpoints instead of stdio
Create workspace-local .claude/mcp.json configuration
Share single config file between platforms

💭 Reasoning

Workspace-local configuration prevents conflicts with Cursor's global MCP setup. The MCP server uses stdio transport and can handle multiple clients simultaneously. Platform detection via environment variables (CLAUDE_CODE_AGENT) enables platform-specific behavior while maintaining shared learning. This approach is clean, maintainable, and follows VS Code extension patterns for workspace-specific configuration.

📁 Files Involved

/.claude/mcp.json
/scripts/setup-claude-code-mcp.sh
/docs/english/AI/MCP/CLAUDE-CODE-SETUP.md
/.gitignore
/package.json

🔗 Related

Decision ID: dev_1767893771092_6e2wm19
Session: 29
Workspace: editor2

Auto-generated by MCP Smart Consolidation