Implementation: How to properly integrate MCP servers with Claude Code exten...

Documentation for Sessions

⚙️ Implementation: How to properly integrate MCP servers with Claude Code exten...

📋 Decision Context

Question:

How to properly integrate MCP servers with Claude Code extension in VS Code/Cursor?

Task: Enable mcp-gograb-ai in Claude Code extension while preserving Cursor's native MCP integration

🎯 Decision Made

Chosen:

Use Claude CLI command claude mcp add --transport stdio --scope project to register the MCP server, not just create a config file

Options Considered:

Create workspace-local .claude/mcp.json only
Use Claude CLI to register MCP server
Configure via VS Code settings.json
Use --mcp-config flag when starting Claude
Wait for native extension support

💭 Reasoning

Claude Code extension documentation explicitly states: 'MCP features can only be configured using the command-line interface'. Creating .claude/mcp.json alone is insufficient. The extension requires CLI registration using claude mcp add command. This is confirmed by testing - the config file alone showed no servers, but after running the CLI command, mcp-gograb-ai appeared as 'connected' in the Manage MCP Servers dialog. The --scope project flag ensures workspace-local configuration, and --transport stdio uses the standard input/output communication method that our MCP server expects.

📁 Files Involved

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

🔗 Related

Decision ID: dev_1767895182511_u7eiyjw
Session: 29
Workspace: editor2

Auto-generated by MCP Smart Consolidation