agent-config-bridge
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-config-bridge Detect agent configs in this repo and migrate to Codex and Cursor, dry run first."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agent-config-bridge
An MCP server that moves your coding-agent setup between Claude Code, Codex CLI, Cursor and Gemini CLI: instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, .cursorrules, GEMINI.md) and MCP server configs (mcpServers JSON ⇄ Codex config.toml ⇄ Gemini settings.json).
Runs locally over stdio. No network calls, no telemetry. It writes files only when you call migrate_project with write: true.
Prefer a web UI? Use the same converter in your browser at getaicodingagent.com.
Tools
Tool | What it does |
| Instruction text from one tool → files and paths for the others. Can also share one AGENTS.md through a symlink or an |
| MCP servers: Claude Code / Claude Desktop / Cursor JSON ⇄ Codex |
| Scans a project read-only for every agent config file and skills folder, and lists which tools have no config yet |
| Generates the missing configs from the existing ones. Dry run by default. Existing files are skipped unless |
| Where each tool reads its config, with official doc links and a verified date. Anything the official docs don't state is returned as |
Related MCP server: codex-mcp-tool
Install
You need Node.js 18 or later and npm 10 or later (npm 9.2 fails to run GitHub packages through npx). The package is not on npm. Run it straight from GitHub (dist/ is committed, so there's no build step):
npx -y github:onehumanbeing/agent-config-bridgeClaude Code
claude mcp add agent-config-bridge -- npx -y github:onehumanbeing/agent-config-bridgeCodex CLI
codex mcp add agent-config-bridge -- npx -y github:onehumanbeing/agent-config-bridgeor add this to ~/.codex/config.toml:
[mcp_servers.agent-config-bridge]
command = "npx"
args = ["-y", "github:onehumanbeing/agent-config-bridge"]Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Gemini CLI: .gemini/settings.json or ~/.gemini/settings.json:
{ "mcpServers": { "agent-config-bridge": { "command": "npx", "args": ["-y", "github:onehumanbeing/agent-config-bridge"] } } }MCPB bundle: download agent-config-bridge-0.1.0.mcpb from the v0.1.0 release and open it in an MCPB-compatible client (for example, double-click it to install in Claude Desktop). Dependencies are bundled.
From a clone
git clone https://github.com/onehumanbeing/agent-config-bridge && cd agent-config-bridge
claude mcp add agent-config-bridge -- node "$PWD/dist/index.js"MCP Registry name: io.github.onehumanbeing/agent-config-bridge
Example prompts
"Detect the agent configs in this repo and migrate them to Codex and Cursor (dry run first)."
"Convert this Claude Desktop config to Codex TOML."
"Where does Gemini CLI read its MCP config? Use compat_matrix."
Links
Web converter and compatibility table: https://getaicodingagent.com
Config matrix for 17 agents: https://getaicodingagent.com/config/
Compare coding agents: https://getaicodingagent.com/compare
Develop
npm install && npm test # builds, then runs unit tests plus an MCP client smoke testMIT © onehumanbeing
Available Tools
5 toolscompat_matrixConfig compatibility matrixARead-only
Where Claude Code, Codex CLI, Cursor and Gemini CLI read instructions, MCP config and skills, with official doc links and the date each was verified. 'unknown' means not stated in the official docs.
Inputs: no named parameters.
convert_mcp_configConvert MCP server configA
Convert MCP server definitions between Claude Code/Claude Desktop/Cursor JSON (mcpServers), Gemini CLI settings.json (httpUrl/url) and Codex config.toml [mcp_servers.*]. Returns target files; writes nothing.
Inputs: text (required), format, targets.
convert_rulesConvert instruction filesA
Convert agent instructions (CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, .cursorrules, GEMINI.md) into the files Claude Code, Codex CLI, Cursor and Gemini CLI read. Returns file paths + contents and a shell command; writes nothing.
Inputs: text (required), link, source, targets.
detect_agent_configsDetect agent configs in a projectARead-only
Scan a project directory (read-only) for CLAUDE.md, AGENTS.md, GEMINI.md, .cursor/rules, .cursorrules, .mcp.json, .cursor/mcp.json, .gemini/settings.json, .codex/config.toml and skills folders.
Inputs: dir (required).
migrate_projectMigrate a project's agent configADestructive
Generate target-tool config files from the project's existing instructions and MCP config. DRY RUN by default: returns the plan. Files are written only when write=true; existing files are skipped unless overwrite=true (Gemini settings.json is merged).
Inputs: dir (required), targets (required), from, link, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
convert_rules and convert_mcp_config target clearly different artifacts (instruction files vs MCP server definitions), and detect_agent_configs is unambiguously read-only discovery. migrate_project partially overlaps with the two convert_* tools since it composes them into a write-capable plan, but its description makes the distinction (orchestration + optional writes) explicit.
Four of five tools follow a verb_noun snake_case pattern (convert_rules, convert_mcp_config, detect_agent_configs, migrate_project). compat_matrix breaks the pattern as a noun phrase, but the convention is otherwise predictable and readable.
Five tools is well-scoped for a config-bridge server: discovery, two artifact-specific conversions, an orchestration/write path, and a reference lookup. Each tool occupies a distinct role with no filler.
The surface covers discovery, conversion, migration and a reference matrix for instructions and MCP config across four agents, which is strong lifecycle coverage. Minor gap: skills are detected and documented in compat_matrix but there is no dedicated skills conversion/write path, leaving that artifact half-covered.
Maintenance
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
FixMyPrompt is a remote MCP server for coding agents. It saves the steps your agent worked out as project memories and fetches them in later sessions, scores and rewrites prompts, and checks CLAUDE.md and AGENTS.md files. Works with Claude Code, Codex and Cursor. Free plan available.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables conversion of coding agent sessions between Claude Code, Codex CLI, and OpenCode, including full support for OpenCode's SQLite storage.41MIT
- AlicenseBqualityBmaintenanceMCP server connecting Claude/Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode.13107 npm24MIT
- AlicenseAqualityBmaintenanceBridges multiple CLI coding agents (Codex, Cursor, OpenCode, Claude, Antigravity) into any MCP client, enabling delegation of prompts, parallel execution, and code review workflows.675 npmMozilla Public 2.0
- AlicenseBqualityBmaintenanceEnables MCP-compatible AI clients like Claude Code, Cursor, and Codex to invoke Google Antigravity's Gemini coding agent for repository-aware file operations, command execution, code review, test generation, and quota checks, while also providing a standalone dual-mode CLI.7MIT