Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"neurohive": {
"env": {
"HIVEMIND_AGENT": "Agent-Backend",
"HIVEMIND_COMPANY": "my-project",
"HIVEMIND_AGENT_ROLE": "backend"
},
"args": [
"neurohive"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Multi-agent memory intelligence — shared knowledge, expertise tracking, and conflict detection for AI agent teams.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'neurohive' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked neurohive against OSV.dev.
Click any tool to inspect its schema.
hivemind://primingStartup context: dashboard + top knowledge for onboarding
hivemind://priming
hivemind://expertiseAll agent expertise data as JSON
hivemind://expertise
hivemind://conflictsUnresolved conflicts as JSON
hivemind://conflicts
hivemind://dashboardFull dashboard data as JSON
hivemind://dashboard
hivemind://agent/{agentId}Expertise profile for a specific agent
hivemind://agent/{agentId}
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / analytics
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Server for GCP environment for interacting with various Observability APIs.
MCP Security Weekly
Get CVE alerts and security updates for io.github.AdelElo13/neurohive and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Multi-agent memory intelligence — shared knowledge, expertise tracking, and conflict detection for AI agent teams.
AI agents in teams forget everything and don't share knowledge. Multiple agents working on the same project re-discover the same facts, contradict each other, and have no collective memory. One agent learns the API timeout is 30 seconds; another assumes 60. Both conclusions sit in separate sessions, never compared.
neurohive wraps neuromcp with a shared intelligence layer. Every memory stored by any agent becomes visible to the team. Searches come back annotated with who discovered what and when. New agents onboard with the team's existing knowledge already loaded. Contradictions get flagged before they cause incidents.
| neuromcp alone | With neurohive | |
|---|---|---|
| Agent knowledge | Isolated per session | Shared across team, attributed |
| Search results | Raw results | Annotated with "discovered by Agent-X, 3 min ago" |
| New agent onboarding | Starts from zero | Primed with team's top knowledge |
| Expertise | Unknown who knows what | Tracked: "Agent-Backend: API (31), Auth (22)" |
| Contradictions | Silently coexist | Flagged: "Backend says 30s timeout, DevOps says 60s" |
| Team overview | None | Dashboard with knowledge map, gaps, activity |
npx neurohive
Drop-in replacement for npx neuromcp. Use the same MCP config — just swap the command. All neuromcp tools and resources are available unchanged, plus three new neurohive tools, five new resources, and automatic cross-agent annotation.
Every search result is annotated with provenance: which agent stored it, how long ago, and how many times it's been retrieved. Agents can see at a glance whether a memory came from a trusted teammate or an unknown source.
When an agent starts up, it reads the hivemind://priming resource to load the team's top knowledge, recent activity, and known gaps. No cold starts.
Every time an agent stores a memory, neurohive updates that agent's expertise profile — tracking which categories they contribute to most. Use hivemind_expertise to route questions: "who knows the most about authentication?"
When two agents store contradictory claims about the same fact, neurohive flags it as a conflict. Conflicts surface in hivemind_conflicts and in the dashboard so the team can resolve them explicitly rather than letting stale data propagate silently.
A single command gives a live view of the collective knowledge base: total memories, active agents, top categories, recent activity, unresolved conflicts, and knowledge gaps.
{
"mcpServers": {
"neurohive": {
"command": "npx",
"args": ["neurohive"],
"env": {
"HIVEMIND_COMPANY": "my-project",
"HIVEMIND_AGENT": "Agent-Backend",
"HIVEMIND_AGENT_ROLE": "backend"
}
}
}
}
{
"mcpServers": {
"neurohive": {
"command": "npx",
"args": ["-y", "neurohive"],
"env": {
"HIVEMIND_COMPANY": "my-project",
"HIVEMIND_AGENT": "Agent-Frontend"
}
}
}
}
{
"mcpServers": {
"neurohive": {
"command": "npx",
"args": ["neurohive"],
"env": {
"HIVEMIND_COMPANY": "my-project",
"HIVEMIND_AGENT": "Cursor-Agent"
}
}
}
}
When Paperclip is running locally, neurohive detects it automatically and reads the company, agent, and role from the Paperclip API. No extra env vars needed — the company namespace is set from the active Paperclip company, an