NEAT — Claude Code MCP server: what it does, how to install
Fuses static code analysis with live OpenTelemetry traces into an exact system graph. Feeds AI coding agents targeted incident data without manual grep.
claude mcp add --env NEAT_CORE_URL=<NEAT_CORE_URL> --transport stdio neat -- npx -y @neat.is/mcpWhat NEAT does
NEAT connects raw repository files to actual execution telemetry. A syntax parser inspects files, routes, and database interactions at symbol depth. Live OpenTelemetry spans map directly onto those exact code locations. The engine avoids calling language models to build this graph, keeping every link deterministic.
Every connection retains its origin tag. The graph tracks whether an edge was extracted from static files, observed in production traces, or marked stale when traffic ceased. Agents pull structured incident reports, dependency paths, and blast radius mappings through dedicated MCP queries instead of scanning directories blind.
On Windows, running npx neat.is fails because the operating system treats the dot extension as an unknown file association. You must install the package globally via npm i -g neat.is and invoke the neat binary directly. Populating live edges requires launching your application with the generated .env.neat file or under opentelemetry-instrument.
What it helps with
- identify the root cause of runtime failures across service boundaries
- calculate blast radius before modifying critical functions
- spot divergence between static code declarations and production telemetry
- verify architectural rules without manual codebase searches
Example prompts for the agent
- Fetch the incident card for node service:checkout via NEAT
- Calculate the blast radius for billing.ts before refactoring
- Inspect divergence between declared routes and observed network traffic
How to install NEAT
Platform CLI
claude mcp add --env NEAT_CORE_URL=<NEAT_CORE_URL> --transport stdio neat -- npx -y @neat.is/mcpReplace <…> with your own values
Platform CLI
codex mcp add neat --env NEAT_CORE_URL=<NEAT_CORE_URL> -- npx -y @neat.is/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"neat": {
"command": "npx",
"args": [
"-y",
"@neat.is/mcp"
],
"env": {
"NEAT_CORE_URL": "<NEAT_CORE_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"neat": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@neat.is/mcp"
],
"env": {
"NEAT_CORE_URL": "<NEAT_CORE_URL>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e NEAT_CORE_URL=<NEAT_CORE_URL> neat npx -y @neat.is/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about NEAT
How to install NEAT in Claude Code?
Run claude mcp add neat -- npx -y @neat.is/mcp. If you run a hosted daemon, supply the address: claude mcp add --env NEAT_CORE_URL=<NEAT_CORE_URL> --transport stdio neat -- npx -y @neat.is/mcp.
How does NEAT investigate system failures?
It queries a deterministic graph fusing static source symbols with OpenTelemetry spans. The server pinpoints the exact file and line where an error began, tracing causes without using an LLM.
Why does npx neat.is fail on Windows?
Windows interprets the .is suffix as a file extension rather than an executable command. Fix this by installing globally with npm i -g neat.is and running the neat command.
