Skip to main content
Glama
README.md
# agent-config-bridge

<!-- mcp-name: io.github.onehumanbeing/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](https://getaicodingagent.com)**.

## Tools

| Tool | What it does |
|---|---|
| `convert_rules` | Instruction text from one tool → files and paths for the others. Can also share one AGENTS.md through a symlink or an `@AGENTS.md` import |
| `convert_mcp_config` | MCP servers: Claude Code / Claude Desktop / Cursor JSON ⇄ Codex `[mcp_servers.*]` TOML ⇄ Gemini `httpUrl`/`url` |
| `detect_agent_configs` | Scans a project read-only for every agent config file and skills folder, and lists which tools have no config yet |
| `migrate_project` | Generates the missing configs from the existing ones. **Dry run by default**. Existing files are skipped unless `overwrite: true`; `.gemini/settings.json` is merged |
| `compat_matrix` | Where each tool reads its config, with official doc links and a verified date. Anything the official docs don't state is returned as `unknown` |

## 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):

```bash
npx -y github:onehumanbeing/agent-config-bridge
```

**Claude Code**
```bash
claude mcp add agent-config-bridge -- npx -y github:onehumanbeing/agent-config-bridge
```

**Codex CLI**
```bash
codex mcp add agent-config-bridge -- npx -y github:onehumanbeing/agent-config-bridge
```
or add this to `~/.codex/config.toml`:
```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`:
```json
{ "mcpServers": { "agent-config-bridge": { "command": "npx", "args": ["-y", "github:onehumanbeing/agent-config-bridge"] } } }
```

**MCPB bundle**: download [agent-config-bridge-0.1.0.mcpb](https://github.com/onehumanbeing/agent-config-bridge/releases/download/v0.1.0/agent-config-bridge-0.1.0.mcpb) from the [v0.1.0 release](https://github.com/onehumanbeing/agent-config-bridge/releases/tag/v0.1.0) and open it in an MCPB-compatible client (for example, double-click it to install in Claude Desktop). Dependencies are bundled.

**From a clone**
```bash
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
```bash
npm install && npm test   # builds, then runs unit tests plus an MCP client smoke test
```

MIT © onehumanbeing

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo issues