Prevent cross-repo architectural breakage before merge. Architecture knowledge graph from static analysis, blast radius in CI, MCP server for AI
Prevent cross-repo architectural breakage before merge. Architecture knowledge graph from static analysis, blast radius in CI, MCP server for AI agents. The coderadius mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Languages — C#, Rubyresolve_service_context — Orient the agent: map a file path, git remote, or repo name to its service, team, and repositorylist_services — Inventory all services with owners, languages, and deployment topologyget_service_details — Deep-dive one service: exposed APIs, endpoint counts, deployment units, CI/CD and Docker infrastructureget_repository_details — Repository posture: services, pipelines, Docker images, tool configurations, build tasks, commit livenessget_data_contract — Exact schema (fields and types) of a payload, event, or database table, before modifying itanalyze_blast_radius — Upstream producers and downstream consumers of a resource (table, channel, endpoint)evaluate_code_change_impact — Blast radius of a proposed change via in-memory topological diff, before committingtrace_data_lineage — Follow a data field across services, brokers, and APIsanalyze_architecture_gravity — SPOFs, shared-database anti-patterns, and coupling hotspots ranked by scoreanalyze_agentic_context — AI-tooling adoption per repository: tools, configurations, skills, workflowsInstallation goes through your MCP client rather than a global install: point it at coderadius on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Coderadius's toolset — Languages, resolve_service_context, list_services and 8 more — is a fair guide to whether it matches your workflow. It is maintained by coderadius-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Languages | C#, Ruby |
| resolve_service_context | Orient the agent: map a file path, git remote, or repo name to its service, team, and repository. |
| list_services | Inventory all services with owners, languages, and deployment topology. |
| get_service_details | Deep-dive one service: exposed APIs, endpoint counts, deployment units, CI/CD and Docker infrastructure. |
| get_repository_details | Repository posture: services, pipelines, Docker images, tool configurations, build tasks, commit liveness. |
| get_data_contract | Exact schema (fields and types) of a payload, event, or database table, before modifying it. |
| analyze_blast_radius | Upstream producers and downstream consumers of a resource (table, channel, endpoint). |
| evaluate_code_change_impact | Blast radius of a proposed change via in-memory topological diff, before committing. |
| trace_data_lineage | Follow a data field across services, brokers, and APIs. |
| analyze_architecture_gravity | SPOFs, shared-database anti-patterns, and coupling hotspots ranked by score. |
| analyze_agentic_context | AI-tooling adoption per repository: tools, configurations, skills, workflows. |
{
"mcpServers": {
"coderadius": {
"command": "cr",
"args": ["mcp", "start"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.