io.github.laurells/outflow-mcp vs NEAT
io.github.laurells/outflow-mcp is an MCP server published by laurells. Marketplaces we read that list it: 1 (Official MCP Registry). NEAT is an MCP server published by neat-technologies. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.laurells/outflow-mcp |  NEAT |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 123 Downloads/week (npm): 14 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.10.9 Downloads/month (npm): 4 440 Downloads/week (npm): 1 833 Forks (GitHub): 1 Stars (GitHub): 22 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.laurells/outflow-mcp | NEAT |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 22 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | On your machine (outflow-mcp) | On your machine (@neat.is/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/laurells/outflow-mcp | github.com/neat-technologies/neat |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.laurells/outflow-mcp
MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents
NEAT
A live graph of your running system, code fused with OTel runtime, that your agent queries over MCP.
How to run each
io.github.laurells/outflow-mcp As a local MCP server: npm package
claude mcp add --env "OUTFLOW_API_KEY=<YOUR_OUTFLOW_API_KEY>" --env "OUTFLOW_WORKSPACE_ID=<YOUR_OUTFLOW_WORKSPACE_ID>" --transport stdio outflow-mcp -- npx -y outflow-mcpRequires: OUTFLOW_API_KEY (secret), OUTFLOW_WORKSPACE_ID
NEAT As a local MCP server: npm package
claude mcp add --transport stdio neat -- npx -y @neat.is/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.laurells/outflow-mcp asks for
OUTFLOW_API_KEY (secret)OUTFLOW_BASE_URLOUTFLOW_WORKSPACE_ID
Only NEAT asks for
NEAT_CORE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.laurells/outflow-mcp · What it can do: NEAT · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.