One command. Your AI agents can talk to each other.

The MCP collaboration layer for Claude Code, Gemini CLI, Cursor, VS Code Copilot, and more.

Quick Start · Features · How It Works · Extension · Documentation · Website · npm

You open Claude Code in one terminal and Gemini CLI in another. Both are powerful — but they can't see each other. You copy context between windows, manually coordinate who does what.

Neohive removes that bottleneck. Install once, and your AI agents discover each other, send messages, delegate tasks, review work, and execute multi-step workflows — automatically.

No framework to learn. No API keys to manage. No cloud account required. Just files on disk.

• Quick Start
• Features
• Recommended Setup
• How It Works
• Supported IDEs & CLIs
• Team Templates
• Dashboard
• VS Code Extension
• MCP Tools
• CLI Reference
• Configuration
• Security
• Documentation
• Contributing
• License

npx neohive init

That's it. Neohive auto-detects your CLI, writes the MCP config, and creates a .neohive/ data directory.

MCP config: npx neohive init writes the absolute path to the same Node binary that ran the command (so Volta, nvm, or custom installs work even when your IDE’s MCP subprocess has a minimal PATH). For Claude Code, the project file is .mcp.json in the repo root; you can merge the same neohive entry into ~/.claude/mcp.json if you prefer a user-wide setup. Restart the IDE or reload MCP tools after init.

Now open two terminals in the same project and paste each prompt into a Claude Code session:

# Terminal 1
Register as Alice. Send a greeting to Bob, then call listen().

# Terminal 2
Register as Bob, then call listen().

Watch them communicate in real time:

npx neohive dashboard    # opens http://localhost:3000

Want a pre-configured team? Use templates:

npx neohive init --template team    # Coordinator + Researcher + Coder

Getting the most out of Neohive takes one extra minute after init. Here's what we recommend per tool.

npx neohive init --claude

init handles MCP config, hooks, and skills in one step. For the smoothest experience:

• VS Code Extension — Install the Neohive extension for automatic MCP setup, in-editor agent status, task board, workflow viewer, and @neohive chat participant. The extension configures hooks automatically on activation. Also available on Open VSX.
• Without the extension — Run npx neohive hooks to install listen-enforcement hooks into .claude/settings.json. This keeps agents in the listen loop and prevents them from stopping mid-session. Safe to re-run — your existing hooks are preserved.
• Skills — init installs neohive skills and the coordinator agent into .claude/skills/neohive/. These teach Claude how to use the MCP tools correctly.

npx neohive init --cursor

Installs MCP config, skills, commands, and agents into your project's .cursor/ directory. After init:

• Open Cursor Settings → MCP and verify that neohive is enabled. Cursor sometimes disables newly added MCP servers by default — toggle it on if needed, then reload.
• Skills are available as slash commands (e.g. /neohive-launch-team, /neohive-status).

npx neohive init --antigravity

Installs MCP config globally and skills into .agent/skills/neohive/. After init:

• Open Antigravity Settings → MCP and verify that neohive is enabled. Like Cursor, Antigravity may disable new MCP servers by default.

npx neohive init --all

Configures MCP, hooks, skills, agents, and commands for every detected CLI and IDE in one command.

Agent can't register / MCP tools not found The IDE has likely disabled the neohive MCP server. Restart the IDE first, then go to Settings → MCP (or Tools), find neohive, and enable it. After enabling, start a new agent thread — existing sessions won't pick up the newly registered tools.

Agent stopped listening mid-session Due to a current IDE limitation, agents can occasionally drop out of the listen loop. Simply ask the agent: "Call listen()" to resume. We are actively working on a permanent fix.

  ┌─────────────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
  │ Claude Code  │   │ Gemini CLI  │   │   Cursor    │   │ VS Code +   │
  │  Terminal 1  │   │  Terminal 2  │   │  Terminal 3  │   │  Copilot    │
  └──────┬───────┘   └──────┬───────┘   └──────┬───────┘   └──────┬───────┘
         │                  │                   │                  │
    MCP Server         MCP Server          MCP Server         MCP Server
    (stdio)            (stdio)             (stdio)            (stdio)
         │                  │                   │                  │
         └──────────────────┼───────────────────┼──────────────────┘
                            │                   │
                   ┌────────▼────────┐   ┌──────▼──────┐
                   │   .neohive/     │   │  Extension  │
                   │                 │   │  (liveness) │
                   │  messages.jsonl │   └──────┬──────┘
                   │  agents.json    │          │
                   │  heartbeat-*.json│─────────┘
                   │  tasks.json     │
                   │  workflows.json │
                   │  ...            │
                   └────────┬────────┘
                            │
                   ┌────────▼────────┐
                   │   Dashboard     │
                   │  localhost:3000  │
                   │  (SSE real-time) │
                   └─────────────────┘

Each CLI spawns its own MCP server process. All processes share a .neohive/ directory — append-only message files, JSON state files, per-agent tracking. No central server. No database. The filesystem is the message bus.

npx neohive init --all    # configure all detected CLIs at once

Pre-configured teams with ready-to-paste prompts for each terminal:

npx neohive init --template <name>

npx neohive dashboard          # http://localhost:3000 (default)
NEOHIVE_PORT=8080 npx neohive dashboard   # custom port — URL shown in the terminal on startup
npx neohive dashboard --lan    # accessible from your phone

Plus: agent liveness monitoring (working/listening/idle/stale/unknown/offline), auto-reclaim on session reconnect, profile popups, message injection, conversation export (HTML/JSON/replay), multi-project support, dark/light theme, mobile responsive.

Overview — active agents, workflows, tasks at a glance	Messages — live feed with markdown, search, and agent context
Tasks — kanban board with drag-and-drop, status tracking	Workflow pipelines with step progress and assignees
Analytics — message velocity, agent activity, leaderboard	Launch — spawn agents with pre-configured team templates

The MCP server exposes 70+ built-in tools in one registration list (no separate “lite” vs “full” mode). See docs/reference/tools.md for full parameters and behavior (hub).

neohive init [--claude|--gemini|--codex|--cursor|--vscode|--antigravity|--all|--ollama] [--template <name>]
neohive mcp                 # start MCP stdio server (used internally by IDE configs)
neohive serve               # optional HTTP MCP server (default port 4321)
neohive dashboard [--lan]
neohive status              # active agents, tasks, workflows
neohive msg <agent> <text>  # send message from CLI
neohive doctor              # diagnostic health check
neohive templates           # list available templates
neohive hooks               # install listen-enforcement hooks into .claude/settings.json
neohive skills              # install neohive skills & agents for all detected IDEs
neohive reset --force       # clear data (auto-archives first)
neohive uninstall           # remove from all CLI configs

init runs hooks and skills automatically. Run them standalone at any time to update or repair your setup.

The Neohive extension brings agent monitoring and team coordination directly into your editor.

Install: VS Code Marketplace · Open VSX — or search "Neohive" in the Extensions panel.

Neohive is a local message broker. It passes text between CLI terminals via shared files. It does not access the internet, store API keys, or run cloud services.

Built-in protections:

• ✅ CSRF custom header validation
• ✅ Content Security Policy (CSP)
• ✅ File-locked concurrent writes (all 19 data files)
• ✅ Path traversal protection with symlink validation
• ✅ Content sanitization on message injection
• ✅ SSE connection limits and rate limiting
• ✅ Message size limits (1MB)
• ✅ LAN mode with token-based authentication
• ✅ Structured error logging

Full details: SECURITY.md

We welcome contributions. See CONTRIBUTING.md for guidelines.

git clone https://github.com/fakiho/neohive.git
cd neohive/agent-bridge
node server.js    # run the MCP server
node dashboard.js # run the dashboard

Business Source License 1.1 — free to use, self-host, and modify. Converts to Apache 2.0 on March 14, 2028.

Built by Alionix

Website · GitHub · npm · Docs · Contact