No user-submitted related servers found.
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.