# NEAT

Fuses static code analysis with live OpenTelemetry traces into an exact system graph. Feeds AI coding agents targeted incident data without manual grep.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 22
- Author: neat-technologies
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/neat-technologies/neat
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/neat

## What it 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`.

## Requirements
- Needs: Node.js (commands run via npx)
- Environment variables: `NEAT_CORE_URL` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env NEAT_CORE_URL=<NEAT_CORE_URL> --transport stdio neat -- npx -y @neat.is/mcp
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add neat --env NEAT_CORE_URL=<NEAT_CORE_URL> -- npx -y @neat.is/mcp
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "neat": {
            "command": "npx",
            "args": [
                "-y",
                "@neat.is/mcp"
            ],
            "env": {
                "NEAT_CORE_URL": "<NEAT_CORE_URL>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "neat": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@neat.is/mcp"
            ],
            "env": {
                "NEAT_CORE_URL": "<NEAT_CORE_URL>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e NEAT_CORE_URL=<NEAT_CORE_URL> neat npx -y @neat.is/mcp
```
Replace <…> with your own values

## When to use it
- 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
- 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

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md