A live graph of your running system, code fused with OTel runtime, that your agent queries over MCP.
Connect Runs on your machine
claude mcp add neat -e NEAT_CORE_URL=<NEAT_CORE_URL> -- npx -y @neat.is/[email protected]
{
"mcpServers": {
"neat": {
"command": "npx",
"args": [
"-y",
"@neat.is/[email protected]"
],
"env": {
"NEAT_CORE_URL": "<NEAT_CORE_URL>"
}
}
}
}
{
"mcpServers": {
"neat": {
"command": "npx",
"args": [
"-y",
"@neat.is/[email protected]"
],
"env": {
"NEAT_CORE_URL": "<NEAT_CORE_URL>"
}
}
}
}
{
"servers": {
"neat": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@neat.is/[email protected]"
],
"env": {
"NEAT_CORE_URL": "<NEAT_CORE_URL>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
NEAT_CORE_URLOptional | URL of the NEAT daemon the server queries. Defaults to the local daemon. |
Details
| Package | @neat.is/[email protected] (NPM, stdio) |
| First published | 17 Oct 2026 |
| Last updated | 17 Oct 2026 |
| Registry name | io.github.neat-technologies/neat |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
