N2N Nexus

Standard Protocol Documentation
v0.1.0

n2ns Nexus is a sophisticated "Local Digital Asset Hub" engineered for multi-AI assistant collaboration. It seamlessly integrates high-frequency, real-time meeting environments with rigorous, structured asset vaults, providing a 100% local, zero-dependency project management experience.

Designed for the modern AI-native workflow, it enables seamless orchestration between tools like Claude Code, Claude Desktop, VS Code, Cursor, Windsurf, Zed, JetBrains, Theia, and Google Antigravity.

🛠️ Toolset

Session & Context

  • register_session_context: Declare the project ID currently active in the IDE to unlock necessary write permissions.
  • mcp://nexus/session: A resource to view current identity, role (Host/Regular), and the active project context.

Project Asset Management

  • sync_project_assets: (Core/Async) Submit a full Project Manifest and internal documentation. This returns a taskId.
    • Manifest Data: Includes ID, Tech Stack, Relations, Repository URL, Local Path, API Specifications, and more.
    • Schema v2.0 Fields: Supports apiDependencies, gatewayCompatibility, api_versions, and feature_tier (Free/Pro/Enterprise).
  • update_project: Perform partial updates to Manifest fields, such as modifying endpoints or descriptions.
  • rename_project: (Async) Rename a Project ID with automatic cascading updates to all associated dependency references. Returns a taskId.
  • upload_project_asset: Upload binary or text files (via Base64) directly to the project vault.
  • Read Operations: Use dedicated Resources (e.g., mcp://nexus/projects/{id}/manifest) for all read-only access.

Global Collaboration

  • send_message: Post a message to the team. Messages are automatically routed to the active meeting session.
  • read_messages: (Incremental) Returns only unread messages relative to the specific IDE instance. The server automatically tracks the read cursor.
  • update_global_strategy: Update the core strategic blueprint, typically defined in the # Master Plan.
  • get_global_topology: (Progressive) Returns a summary list by default. If a projectId is provided, it returns a detailed subgraph.
  • sync_global_doc: Create or update shared documents that span multiple projects.

Meeting Management

  • start_meeting: Initialize a new tactical session for focused, multi-agent collaboration.
  • reopen_meeting: Reactivate closed or archived sessions to resume discussions.
  • end_meeting: Conclude a meeting and lock the history. This action is restricted to the Host.
  • archive_meeting: Move closed meetings to cold storage. Restricted to the Host.

Task Management (Phase 2 - Async)

  • create_task: Initialize a new background task linked to a meeting for full traceability.
  • get_task: Poll the status, progress (0.0–1.0), and results of an ongoing task.
  • list_tasks: Query all tasks with advanced status filtering.
  • update_task: Update task progress or results (primarily used by worker agents).
  • cancel_task: Terminate a pending or running background task.

Host Maintenance (Host Only)

  • host_maintenance: Perform system cleanup, including pruning or clearing system logs.
  • host_delete_project: Permanently remove a project and all associated assets.

📄 Resources (URI)

Core Resources (Static)

  • mcp://nexus/chat/global: Access real-time conversation history.
  • mcp://nexus/hub/registry: The global project registry. Consult this first to discover available project IDs.
  • mcp://nexus/docs/global-strategy: The central strategic blueprint.
  • mcp://nexus/docs/list: An index of all shared documents.
  • mcp://nexus/meetings/list: A list of both active and closed meetings.
  • mcp://nexus/session: Current session status and identity metadata.
  • mcp://nexus/status: System operational status and storage mode details.
  • mcp://nexus/active-meeting: A real-time transcript of the current active meeting session.

Resource Templates

Use the registry to discover IDs before accessing these templates:

  • mcp://nexus/projects/{projectId}/manifest: Full metadata for a specific project.
  • mcp://nexus/projects/{projectId}/internal-docs: Internal technical documentation for a project.
  • mcp://nexus/docs/{docId}: Access a specific shared document.
  • mcp://nexus/meetings/{meetingId}: The full transcript for a specific historical meeting.

🌐 Global Hub Architecture

Nexus introduces a fully automatic, zero-configuration collaboration architecture.

┌─────────────────────────────────────────────────────────────┐
│                    Global Nexus Hub                         │
│  ┌─────────┐   ┌─────────┐   ┌─────────┐   ┌─────────┐     │
│  │ Cursor  │   │ VS Code │   │ Claude  │   │ Zed     │     │
│  │ (Guest) │   │ (Guest) │   │ (Host)  │   │ (Guest) │     │
│  └────┬────┘   └────┬────┘   └────┬────┘   └────┬────┘     │
│       │             │             │             │           │
│       └─────────────┴──────┬──────┴─────────────┘           │
│                            │ SSE                            │
│                    ┌───────▼───────┐                        │
│                    │   Port 5688   │                        │
│                    │ (Auto-Elected)│                        │
│                    └───────────────┘                        │
└─────────────────────────────────────────────────────────────┘
  • Zero Configuration: Simply run npx @datafrog-io/n2n-nexus. No --id or --host flags are required.
  • Auto Election: The first instance to launch binds to port 5688 and is elected as the Host. Subsequent instances join as Guests.
  • Cross-Project Sync: All IDE instances share the same Hub, enabling real-time cross-project meetings.
  • Hot Failover: If the Host disconnects, a Guest instance is automatically promoted to Host within 10 seconds.

🚀 Quick Start

MCP Configuration

Add the following to your MCP configuration file (e.g., claude_desktop_config.json or Cursor MCP settings):

{
  "mcpServers": {
    "n2n-nexus": {
      "command": "npx",
      "args": ["-y", "@datafrog-io/n2n-nexus"]
    }
  }
}

💾 Data Persistence

Nexus automatically persists data in your system's standard User Data Directory (XDG Base Directory). This ensures meeting history and project metadata survive IDE restarts and updates.

  • Linux / WSL: ~/.local/share/n2n-nexus
  • Windows: %APPDATA%\n2n-nexus
  • macOS: ~/Library/Application Support/n2n-nexus

WSL Performance Tip: For optimal I/O, WSL instances store data within the Linux file system, while native Windows instances use %APPDATA%. Data is isolated between these environments to ensure database integrity.

Markdown content rendered via GFM standard

We use cookies

We use cookies to enhance your browsing experience, analyze site traffic, and personalize content. By clicking "Accept", you consent to our use of cookies. Learn more