Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add n2n-nexus -- npx -y n2n-nexus@0.12.6Ejecútalo en una terminal.
{ "mcpServers": { "n2n-nexus": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirOne host. Many assistants. Shared project state.
n2n-nexus is an open-source Model Context Protocol (MCP) coordination server for developers and teams who use multiple AI coding assistants across IDEs, machines, and projects. Use it when Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, JetBrains, or other MCP-enabled clients need a shared local coordination layer instead of isolated per-chat context.
If you are searching for:
n2n-nexus is designed for these cases: shared host state, lightweight MCP adapters, project-aware collaboration, local storage and cross-environment IDE workflows.
n2n-nexus gives AI assistants a shared coordination workspace. A long-running local host, n2n-nexus-host, owns project state, meetings, messages, tasks, shared docs, and project assets. Lightweight MCP adapters from the n2n-nexus npm package connect each IDE or assistant to the same host.
Quick summary
n2n-nexus-host with Scoop / Homebrew / a Releases archive; the client with npm i -g n2n-nexus@latest, then n2n-nexus install <claude|codex>┌──────────────────────────────────────┐
│ n2n-nexus-host │
│ Tray app or background service │
│ Owns data, tools, tasks, messages │
└──────────────┬───────────────────────┘
│ HTTP (NEXUS_ENDPOINT)
┌───────┼───────┐
▼ ▼ ▼
MCP-A MCP-B MCP-C
(Win) (WSL) (SSH/VM)
n2n-nexus adapter per IDE
n2n-nexus mcp), which forwards tool calls to the host.NEXUS_ENDPOINT at the same host from different machines or shells. The host listens on 127.0.0.1 by default; turn on LAN access only on a trusted network.n2n-nexus-host, with Scoop, Homebrew or an archive from Releases: Installation guide, steps 1–2.npm i -g n2n-nexus@latest, then n2n-nexus install claude or n2n-nexus install codex): step 3.install codex trusts the n2n-nexus hooks in Codex; if it says it could not, trust them by hand: step 4.Other MCP clients and several machines: see the Installation guide. Using it, troubleshooting and configuration: see the User guide.
The host exposes 36 tools, grouped by purpose:
See Tools reference for parameter schemas and call examples.
The docs include a recorded multi-agent session that shows n2n-nexus in action. Four AI assistants — running in different IDEs and assigned to different projects — used a shared n2n-nexus host to coordinate in real time.
What to look for in the session:
register_session_context tool of that release; current versions pass projectId explicitly instead), then read and wrote to the same host throughout the session.PROPOSAL, DECISION, UPDATE and CHAT tags let assistants signal intent, not just post text; a DECISION in a meeting is also kept in its decisions list.[Augment] Synced global doc: edge-sync-protocol-v1 record actual tool calls. That version wrote them into the chat stream; current versions keep them out of the conversation and expose them as structured events through list_events.No. It is a local MCP coordination server for AI assistants; its state stays local and is exposed to clients through MCP tools.
No. n2n-memory is a local memory tool for a single repository. n2n-nexus is a multi-assistant coordination hub for project manifests, messages, meetings, tasks and shared docs.
Yes, as long as the client can run a local MCP command server. The IDE starts the adapter, and the adapter reaches the local host through NEXUS_ENDPOINT. In the Claude desktop app, register it for Claude Code (n2n-nexus install claude) only, not in claude_desktop_config.json: the app would bridge it into the Code tab and drop the conversation identity (User guide, section 2).
Yes. Run the host in one environment and point every adapter at it with NEXUS_ENDPOINT.
No cloud service is needed. Data stays in the configured local directory. Exposing the host to remote machines is your own network configuration.
No. n2n-nexus coordinates project metadata, messages, meetings, docs, tasks and assets; it does no semantic code search.
settings.json, data and logs.This project is licensed under the Apache-2.0 License.
Built by N2NS Lab, the open-source lab of datafrog.io for practical AI developer tools.
Local-first MCP coordination hub from N2NS Lab for multi-AI assistant collaboration.
{ "mcpServers": { "n2n-nexus": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
N2n Nexus se ejecuta localmente por stdio.
Última comprobación: 2026-11-15. Local-first MCP coordination hub from N2NS Lab for multi-AI assistant collaboration.