MCP servers · adelelo13

neurohive: shared memory, expertise tracking and conflict detection for AI agent teams

An MCP server that wraps neuromcp to share memories across AI agents, annotate search results with their source and flag contradictory claims.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

neurohive adds a shared layer on top of neuromcp. Memories stored by any agent become visible to the whole team, and search results show which agent stored them, how long ago, and how often they were retrieved. It tracks each agent's expertise by category, flags conflicts when two agents store contradictory claims about the same fact, and offers a dashboard of memories, active agents, categories, activity, unresolved conflicts and knowledge gaps. At startup, an agent can load the team's top knowledge through a priming resource.

It suits teams of AI agents working on the same project, where agents re-discover the same facts or contradict each other across separate sessions. It is also useful for onboarding a new agent with existing team knowledge, or for finding which agent knows most about a topic before routing a question to it.

It runs as an MCP server started with the neurohive command over stdio, and it uses the same MCP configuration as neuromcp, with only the command changed. Behaviour is set through HIVEMIND_* variables (company namespace, agent identifier, role, priming count) and NEUROMCP_* variables (database path, log level, embedding provider). CLI commands cover the dashboard, expertise lookup, conflict listing and a health check. It exposes 16 tools, 18 resources and 3 prompts, including the 13 neuromcp tools unchanged.

Limitations and requirements

Requires neuromcp, which neurohive wraps. The default embedding provider is local; OpenAI embeddings need an OPENAI_API_KEY. Paperclip detection works automatically only when Paperclip is running locally; otherwise agent identity must be configured manually.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.AdelElo13/neurohive

    Multi-agent memory intelligence with expertise tracking and conflict detection

    v1.0.2
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026