Lightweight code intelligence engine for AI agents. Dependency mapping, blast radius analysis, and call graph via MCP.
Recon MCP server exists for a simple reason — assistants are far more useful when they can act on Recon directly instead of describing what you should do. Lightweight code intelligence engine for AI agents. Dependency mapping, blast radius analysis, and call graph via MCP.
Give your AI agent a brain. Index your codebase in 5 seconds.
Once Recon is connected, these are the calls the assistant has available:
Method — PathGET — /api/healthPOST — /api/tools/:namerecon_map — Architecture overview: packages, tech stack, entry points, healthrecon_find — Smart search: exact name, wildcard (*Handler), or natural languagerecon_explain — Full 360° context: callers, callees, flows, cross-language links, testsrecon_impact — The recon_impact tool exposed by this serverrecon_changes — Git diff to affected symbols, risk assessment, and affected testsrecon_rename — The recon_rename tool exposed by this serverrecon_export — The recon_export tool exposed by this serverrecon_rules — Code quality: dead code, circular deps, unused exports, large files, orphansInstallation goes through your MCP client rather than a global install: point it at recon-mcp 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.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Recon's toolset — Method, GET, POST and 8 more — is a fair guide to whether it matches your workflow. It is maintained by jhm1909; 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 |
|---|---|
| Method | Path |
| GET | /api/health |
| POST | /api/tools/:name |
| recon_map | Architecture overview: packages, tech stack, entry points, health. |
| recon_find | Smart search: exact name, wildcard (*Handler), or natural language. |
| recon_explain | Full 360° context: callers, callees, flows, cross-language links, tests. |
| recon_impact | The recon_impact tool exposed by this server. |
| recon_changes | Git diff to affected symbols, risk assessment, and affected tests. |
| recon_rename | The recon_rename tool exposed by this server. |
| recon_export | The recon_export tool exposed by this server. |
| recon_rules | Code quality: dead code, circular deps, unused exports, large files, orphans. |
```json
{
"mcpServers": {
"recon": {
"command": "npx",
"args": ["recon-mcp", "serve"],
"cwd": "/path/to/backend"
}
}
}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.