agent-config-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_rulesA | 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. |
| convert_mcp_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. |
| detect_agent_configsA | 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. |
| migrate_projectA | 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). |
| compat_matrixA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.