Custom MCP servers
Add project-scoped MCP servers from config files in your repositories.
Superconductor supports project-scoped MCP configuration stored in your repos. If your repo contains an MCP config file, Superconductor merges it into the agent's MCP configuration automatically.
This lets you version-control MCP servers alongside your code so every agent gets the same tools without manual setup.
Supported config files
Each agent reads from its own config file format:
| Agent | MCP config file | Other merged config |
|---|---|---|
| Claude Code | [repo]/.mcp.json | Hooks, plugins, and marketplaces from [repo]/.claude/settings.json; commands and agents from [repo]/.claude/ |
| Codex | [repo]/.codex/config.toml | - |
| Gemini CLI | [repo]/.gemini/settings.json | Commands |
| OpenCode | [repo]/opencode.json | Commands, agents, plugins |
| Amp | [repo]/.amp/settings.json | - |
When there are conflicts between your repo config and the config Superconductor generates from Project Settings, Superconductor's config takes precedence.
When to use repo-defined MCPs
Use repo-defined MCPs when:
- You want the same MCP setup in local development and Superconductor
- You need to pin a server command, environment variable name, or config path
Use Superconductor-provided MCPs when the provider is already listed in Project Settings -> Skills and MCPs. Those settings handle network access and encrypted API key storage for you.