agent-config-bridge
Related Servers
Alternatives to agent-config-bridge
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceEnables conversion of coding agent sessions between Claude Code, Codex CLI, and OpenCode, including full support for OpenCode's SQLite storage.41MIT
- 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
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Code to delegate coding tasks to a local model through a configurable coding-agent CLI backed by any OpenAI-compatible endpoint, with tools for health checks, task execution, and context-aware file modifications.-
- 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
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.AGPL 3.0
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.