<strong>📦 Install from npm</strong> | <strong>🐙 GitHub Repository</strong>
📦 Install from npm | 🐙 GitHub Repository. That is what the neuroverse mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
neuroverse on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 5 tools. What each one is for:
Requirements — The Requirements tool exposed by this serverOutput — The key difference: the code decides — not the LLM. If the LLM fails, hallucinates, or returns garbage, the rule engine takes overBenefits — The Benefits tool exposed by this serverRouting — The Routing tool exposed by this serverFallback — If the target agent is unreachable: json { "success": false, "error": "Agent unreachable: ConnectError", "fallback": true }Configuration is passed through the environment: DATABASE_URL, OPENAI_API_KEY, ANTHROPIC_API_KEY, SARVAM_API_KEY, OLLAMA_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Neuroverse's toolset — Requirements, Output, Benefits and 2 more — is a fair guide to whether it matches your workflow. It is maintained by joshua400; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Requirements | The Requirements tool exposed by this server. |
| Output | The key difference: **the code decides** — not the LLM. If the LLM fails, hallucinates, or returns garbage, the rule engine takes over. Deterministic. Reliable. |
| Benefits | The Benefits tool exposed by this server. |
| Routing | The Routing tool exposed by this server. |
| Fallback | If the target agent is unreachable: json { "success": false, "error": "Agent unreachable: ConnectError", "fallback": true } |
{
"mcpServers": {
"neuroverse": {
"command": "npx",
"args": ["neuroverse"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| SARVAM_API_KEY | Credential the server authenticates with. | Yes |
| OLLAMA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
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.