The 43 Supported Client Surfaces in Codebase Memory MCP: Installation and Configuration

The codebase-memory-mcp installer automatically detects 37 client surfaces and conditionally activates 6 additional ones, writing tiered MCP profiles to each agent's documented configuration location via a single curl | bash command.

The DeusData/codebase-memory-mcp repository provides a universal installer that configures 43 supported client surfaces for AI coding agents. This single-command setup eliminates manual configuration by detecting installed clients and writing the appropriate MCP server definitions, durable context files, and skill definitions to each agent's standard configuration path.

The Complete Matrix of 43 Client Surfaces

The installer categorizes agents into 37 automatically detected surfaces and 6 conditional or opt-in surfaces. This distinction ensures the installer never creates new configuration files for agents you have not explicitly installed.

Automatically Detected Surfaces (37)

These agents are discovered by scanning for configuration files or environment markers. When detected, the installer writes Scout, Verify, and Auditor MCP profiles to the agent's config.

Agent	Configuration Location
Claude Code	~/.claude.json
Codex CLI	$CODEX_HOME/config.toml
Gemini CLI	.gemini/settings.json
Zed	Platform settings.json (JSONC)
OpenCode	$OPENCODE_CONFIG or global config
Antigravity	.gemini/config/mcp_config.json
Aider	.aider.conf.yml
KiloCode	.config/kilo/kilo.jsonc
VS Code	Platform Code/User/mcp.json
Cursor	.cursor/mcp.json
Windsurf	~/.codeium/windsurf/mcp_config.json
Augment / Auggie	~/.augment/settings.json
OpenClaw	$OPENCLAW_CONFIG_PATH or openclaw.json
Kiro	$KIRO_HOME/settings/mcp.json
Junie	.junie/mcp/mcp.json
Hermes	$HERMES_HOME/config.yaml
OpenHands	.openhands/mcp.json
Cline	~/.cline/mcp.json + ${CLINE_DATA_DIR:-~/.cline/data}/settings/cline_mcp_settings.json
Warp	UI / Warp Drive (manual skill-only)
Qwen Code	.qwen/settings.json
GitHub Copilot CLI	$COPILOT_HOME/mcp-config.json
Factory Droid	.factory/mcp.json
Crush	.config/crush/crush.json
Goose	.config/goose/config.yaml
Mistral Vibe	$VIBE_HOME/config.toml
Qoder CLI	~/.qoder/settings.json
Kimi Code CLI	$KIMI_CODE_HOME/mcp.json (default ~/.kimi-code)
GitLab Duo CLI	$GLAB_CONFIG_DIR/duo/mcp.json or platform fallback
Rovo Dev CLI	~/.rovodev/mcp.json (or override)
Amp	~/.config/agents/skills/codebase-memory/mcp.json
Devin CLI / Local	~/.config/devin/config.json (platform-specific app-data path)
Tabnine	~/.tabnine/mcp_servers.json
Amazon Q Developer IDE	~/.aws/amazonq/default.json (preserves agents/default.json or legacy mcp.json)
CodeBuddy Code CLI	~/.codebuddy/.mcp.json (preserves legacy file)
IBM Bob Shell	~/.bob/mcp_settings.json (detected by bob presence)
Pochi	~/.pochi/config.jsonc (mcp section)
Pi	~/.pi/agent/AGENTS.md + skill

Conditional and Opt-In Surfaces (6)

These surfaces are configured only if existing configuration files are found (conditional) or require explicit user opt-in.

Agent	Installation Mode	Configuration Location
Continue / cn	Conditional (config exists)	~/.continue/config.yaml or $CBM_CONTINUE_CONFIG_PATH
Visual Studio	Conditional, Windows only	~/.mcp.json
TRAE	Conditional	Existing $CBM_TRAE_CONFIG_PATH
Roo Code	Conditional	Existing $CBM_ROO_CONFIG_PATH
IBM Bob IDE	Conditional (explicit opt-in)	Existing ~/.bob/mcp.json
Sourcegraph Cody	Explicit opt-in	Existing $CBM_CODY_CONFIG_PATH

How the Installer Configures Each Surface

The install.sh script performs automatic detection by scanning for the client’s configuration file or known environment markers. When found, it writes three tiered toolsets—Scout, Verify, and Auditor—into the agent’s config, along with durable instruction files (AGENTS.md, SKILLS.md).

Conditional activation occurs only if the documented config path already exists. For example, Continue is configured only if ~/.continue/config.yaml is present. The installer never introduces new files for these agents unless the user already has them.

All hooks are fail-open and context-only. The installer never flips experimental flags, enables unreviewed plugins, or writes beyond the documented configuration locations.

Installation Commands and Verification

Install the MCP server and configure all detected surfaces using the one-line installer:

# One-line install (macOS / Linux)

curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash

# Install with optional UI

curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash -s -- --ui

Verify that the installer created a client entry for a specific agent:

# Example: Check Claude Code configuration

cat ~/.claude.json | grep codebase-memory-mcp

List all configured client surfaces via the MCP CLI:

# List all 43 supported agents with their tiered profiles

codebase-memory-mcp cli list_agents

# Query a single agent's configuration (e.g., VS Code)

codebase-memory-mcp cli get_agent_config --agent "VS Code"

Source Code Implementation

The authoritative list of 43 supported client surfaces is defined in README.md lines 94-138, which documents the detection logic and installation details for each agent.

In src/main.c at line 524, the runtime prints the "Supported automatic/conditional client surfaces (43)" banner, confirming the compiled binary recognizes the full matrix.

The test suite in tests/test_cli.c (lines 2477-2537) contains automated assertions verifying that the README, CLI help text, and landing page all consistently list exactly 43 surfaces, preventing documentation drift.

The install.sh script in the repository root performs the actual detection and file writing, while scripts/build.sh compiles the static binary and UI variant referenced in the quick-start workflow.

Summary

• 43 total client surfaces are supported: 37 automatically detected and 6 conditional/opt-in.
• The single-command installer (curl | bash) scans for environment markers and writes MCP configurations to each agent's documented location.
• Three tiered profiles (Scout, Verify, Auditor) are deployed to each configured surface.
• Safety guarantees prevent the installer from creating new files for conditional agents or enabling experimental features.
• Source validation occurs in tests/test_cli.c to ensure the README and CLI remain synchronized on the count of supported surfaces.

Frequently Asked Questions

What distinguishes the 37 automatic surfaces from the 6 conditional ones?

The 37 automatic surfaces are configured immediately when the installer detects the agent's presence via configuration files or environment variables. The 6 conditional surfaces—including Continue, Visual Studio, TRAE, Roo Code, IBM Bob IDE, and Sourcegraph Cody—are configured only if the user already has existing configuration files for those agents, preventing unnecessary file creation.

Where does the installer write MCP configuration for VS Code and Cursor?

For VS Code, the installer writes to the platform-specific Code/User/mcp.json path. For Cursor, it writes to .cursor/mcp.json in the user's home directory. Both locations respect the client's documented configuration standards and include the Scout, Verify, and Auditor tiered toolsets.

How can I verify that all 43 surfaces are correctly recognized by the binary?

Run the CLI command codebase-memory-mcp cli list_agents to display all configured agents. Additionally, the source file src/main.c at line 524 explicitly prints the count of supported surfaces at runtime, and tests/test_cli.c (lines 2477-2537) validates that the README and CLI consistently report exactly 43 supported client surfaces.

Does the installer modify experimental flags or enable unreviewed plugins?

No. The installer operates under fail-open safety guarantees. It only writes context and MCP server definitions to documented configuration locations. It never flips experimental flags, enables unreviewed plugins, or modifies agent settings beyond adding the codebase-memory-mcp server configuration.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}