Nucleus Brain - Multi-Agent Orchestration

Created By
LKGargProjects5 months ago
🧠 The Core of Your AI Agents Multi-agent orchestration MCP server with 10 tools for agent coordination. Features: • Persistent memory via local .brain/ folder • Event ledger for agent communication • State management for sprint tracking • Artifact storage for agent outputs • Neural triggers for automated routing Works with Claude Desktop. Your data stays local. pip install mcp-server-nucleus
Overview

what is Nucleus Brain?

Nucleus Brain is a multi-agent orchestration server designed to coordinate AI agents effectively, providing a core framework for managing their interactions and memory.

how to use Nucleus Brain?

To use Nucleus Brain, install it via pip with the command pip install mcp-server-nucleus, and configure your server settings to manage your AI agents.

key features of Nucleus Brain?

  • 🔧 10 MCP Tools for events, state, artifacts, and triggers.
  • 📡 3 MCP Resources that allow subscribable state, events, and triggers.
  • 💬 2 MCP Prompts with pre-built orchestration commands.
  • 🧪 Tested with 11 pytest tests and GitHub Actions CI.
  • 🔐 Privacy-First approach ensuring all data remains local.

use cases of Nucleus Brain?

  1. Coordinating multiple AI agents for complex tasks.
  2. Managing state and events in AI-driven applications.
  3. Storing and retrieving artifacts generated by AI agents.

FAQ from Nucleus Brain?

  • Can Nucleus Brain work with any AI agents?

Yes! Nucleus Brain is designed to work with various AI agents, including Claude Desktop.

  • Is my data safe with Nucleus Brain?

Absolutely! Nucleus Brain ensures that all data stays local and is not shared externally.

  • How do I set up Nucleus Brain?

Follow the quick start guide provided in the documentation after installation.

Server Config

{
  "mcpServers": {
    "nucleus-brain": {
      "command": "python3",
      "args": [
        "-m",
        "mcp_server_nucleus"
      ],
      "env": {
        "NUCLEAR_BRAIN_PATH": "/path/to/your/.brain"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
LKGargProjects
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago