# What Are the 43 Supported Agent Surfaces in Codebase-Memory-MCP and How to Configure Them

> Discover the 43 agent surfaces in Codebase-Memory-MCP and learn how to configure them via a single install command. Integrate AI coding assistants seamlessly.

- Repository: [Martin Vogel/codebase-memory-mcp](https://github.com/DeusData/codebase-memory-mcp)
- Tags: how-to-guide
- Published: 2026-07-28

---

**Codebase-memory-mcp ships with 43 automatic and conditional client "surfaces" that integrate AI coding assistants with the MCP server, all configurable via a single `install` command that writes settings to each tool's configuration files.**

The `codebase-memory-mcp` repository provides seamless integrations for 43 distinct agent surfaces, allowing various coding assistants to communicate with the Model Context Protocol (MCP) server without custom code. These integrations span popular IDEs, CLI tools, and AI coding assistants, with the complete inventory maintained in the project's documentation. Understanding how these surfaces are detected and configured ensures you can quickly connect your preferred development environment to the MCP server.

## The Complete List of 43 Supported Agent Surfaces

According to the source code in [`docs/llms.txt`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/llms.txt) [L15-L16], the repository supports the following agents:

| # | Agent / Surface | # | Agent / Surface |

|---|-----------------|---|-----------------|
| 1 | Claude Code | 23 | Crush |
| 2 | Codex CLI | 24 | Goose |
| 3 | Gemini CLI | 25 | Mistral Vibe |
| 4 | Zed | 26 | Qoder CLI |
| 5 | OpenCode | 27 | Kimi Code CLI |
| 6 | Antigravity | 28 | GitLab Duo CLI |
| 7 | Aider | 29 | Rovo Dev CLI |
| 8 | KiloCode | 30 | Amp |
| 9 | VS Code | 31 | Devin CLI / Local |
| 10 | Cursor | 32 | Tabnine |
| 11 | Windsurf | 33 | Continue / cn |
| 12 | Augment / Auggie | 34 | Visual Studio |
| 13 | OpenClaw | 35 | TRAE |
| 14 | Kiro | 36 | Roo Code |
| 15 | Junie | 37 | Amazon Q Developer IDE |
| 16 | Hermes | 38 | CodeBuddy Code CLI |
| 17 | OpenHands | 39 | IBM Bob IDE |
| 18 | Cline | 40 | IBM Bob Shell |
| 19 | Warp | 41 | Pochi |
| 20 | Qwen Code | 42 | Pi |
| 21 | GitHub Copilot CLI | 43 | Sourcegraph Cody |
| 22 | Factory Droid | | |

The surfaces divide into **37 automatically-detected** agents that the server discovers at runtime and **6 conditional/explicit** agents requiring manual installation steps.

## How Agent Surfaces Are Configured

The MCP CLI provides an **`install`** sub-command that writes integration snippets into each agent's configuration files. This functionality is implemented in [`pkg/go/cmd/codebase-memory-mcp/main.go`](https://github.com/DeusData/codebase-memory-mcp/blob/main/pkg/go/cmd/codebase-memory-mcp/main.go) and handles all 43 supported agents.

### Preview Changes with Dry-Run

Before modifying any files, preview the exact configuration changes:

```bash
codebase-memory-mcp install --dry-run

```

### Installation Process

Running the install command (without `--dry-run`) executes three steps:

1. Detects the host OS and locates the appropriate config location for each supported editor/IDE.
2. Inserts a small JSON/TOML/YAML block pointing the agent to the local MCP server (host, port, and optional auth token).
3. Optionally enables the UI graph component if the binary was built with embedded UI assets.

The installation logic is documented in [`docs/CONFIGURATION.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/CONFIGURATION.md) under *Agent and Editor Integration Files* [L28-L35]. Ancillary scripts like [`scripts/install-git-hooks.sh`](https://github.com/DeusData/codebase-memory-mcp/blob/main/scripts/install-git-hooks.sh) handle additional setup for specific editors, such as adding Git-hook lines where required.

## Configuration File Examples

The installer generates tool-specific configuration blocks automatically. You can modify these files manually after installation; the MCP server reads the same settings at startup.

### VS Code Configuration

For Visual Studio Code, the installer writes to [`settings.json`](https://github.com/DeusData/codebase-memory-mcp/blob/main/settings.json):

```json
{
  "codebaseMemoryMcp.enabled": true,
  "codebaseMemoryMcp.serverPort": 9749,
  "codebaseMemoryMcp.serverHost": "127.0.0.1"
}

```

### Zed Configuration

For the Zed editor, the installer modifies [`extensions.toml`](https://github.com/DeusData/codebase-memory-mcp/blob/main/extensions.toml):

```toml
[extensions.codebase-memory-mcp]
enabled = true
host = "127.0.0.1"
port = 9749

```

## Key Implementation Files

Understanding the source structure helps with advanced customization:

- **[`docs/llms.txt`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/llms.txt)**: Master registry of the 43 supported agent surfaces [L15-L16].
- **[`docs/CONFIGURATION.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/CONFIGURATION.md)**: Documents where and how MCP reads/writes configuration files [L28-L35].
- **[`pkg/go/cmd/codebase-memory-mcp/main.go`](https://github.com/DeusData/codebase-memory-mcp/blob/main/pkg/go/cmd/codebase-memory-mcp/main.go)**: Implements the `install` sub-command that writes integration blocks.
- **[`scripts/install-git-hooks.sh`](https://github.com/DeusData/codebase-memory-mcp/blob/main/scripts/install-git-hooks.sh)**: Ancillary script used by the installer for editor-specific Git hook integrations.

## Summary

- Codebase-memory-mcp supports **43 agent surfaces** including Claude Code, Codex CLI, VS Code, Cursor, and 39 others.
- The surfaces split into **37 automatically-detected** agents and **6 conditional** agents requiring explicit installation.
- Use **`codebase-memory-mcp install`** to automatically write configuration to all supported tools.
- Run **`--dry-run`** to preview changes before applying them.
- Configuration files vary by editor (JSON for VS Code, TOML for Zed, etc.) and are documented in [`docs/CONFIGURATION.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/CONFIGURATION.md).

## Frequently Asked Questions

### How do I preview configuration changes before applying them?

Use the `--dry-run` flag with the install command. Executing `codebase-memory-mcp install --dry-run` displays exactly which files would be modified and what content would be written, without making any actual changes to your system.

### What is the difference between automatically-detected and conditional agent surfaces?

The 37 automatically-detected agents are discovered by the server at runtime without additional configuration, while the 6 conditional surfaces require explicit installation via the `install` command to enable the integration. Both types are configured using the same CLI tool.

### Where is the master list of supported agents maintained?

The canonical list resides in [`docs/llms.txt`](https://github.com/DeusData/codebase-memory-mcp/blob/main/docs/llms.txt) at lines 15-16 of the repository. This file serves as the registry for all 43 supported integrations, ranging from Claude Code and GitHub Copilot CLI to specialized tools like IBM Bob IDE and Sourcegraph Cody.

### Can I manually edit the configuration files after installation?

Yes. The installer generates standard configuration files (such as VS Code's [`settings.json`](https://github.com/DeusData/codebase-memory-mcp/blob/main/settings.json) or Zed's [`extensions.toml`](https://github.com/DeusData/codebase-memory-mcp/blob/main/extensions.toml)) that you can modify directly. The MCP server reads these same settings at startup, so manual edits take effect immediately on the next server launch.