Nucleus MCP server

Nucleus is an MCP server with 28 tools an agent can call, among them nucleus_agents, nucleus_audit, nucleus_ccr_arm. It answers at https://relay.nucleusos.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status

Answering

Tools

Reliability

6 of 6 checks

Response time

916 ms

Transport

streamable HTTP

Last checked

22 October 2026

Sovereign Agent OS — Persistent Memory, Governance & Compliance for AI Agents.

Description as the publisher wrote it.

The 28 tools Nucleus offers

Tool	What it does
`nucleus_agents`	Agent spawning, critic, swarm, memory, ingestion & dashboard tools. Actions: spawn_agent - Spawn Ephemeral Agent. params: {intent, execute_now?, persona?, confirm?}. HITL: requires confirm=true. apply_critique - Apply critique fixes. params Inputs: action, params
`nucleus_audit`	W8 Team-tier tamper-evident audit log (SHA-256 hash chain). Actions: log_event - Append an audit event to the chain. params: {event_type, actor, resource, outcome, metadata?, team_id?, ts?} query - Single-tenant query. Rejects team_id='*'. Inputs: action, params
`nucleus_ccr_arm`	One-shot convenience: resolve canonical inbox + arm long-poll subscription. Per PR #2 (CCR server-side auto-arm) — IDE-agnostic relay-arrival arming. This is the RECOMMENDED entry point for SessionStart auto-arming across all MCP clients (C Inputs: role, timeout_seconds
`nucleus_delegate`	Hand a coding or review task to a cross-vendor lane — a cheap, non-Claude agent that does the work for you. Use this INSTEAD OF shelling out to any CLI: it picks the vendor, injects the correct per-vendor permission flags, captures all outp Inputs: action, params
`nucleus_engrams`	Engrams, health, observability, DSoR & tier system tools. Actions: health - Get system health status version - Get Nucleus version info export_schema - Export MCP toolset as JSON Schema performance_metrics - Get perf metrics. params: {expor Inputs: action, params
`nucleus_features`	Feature tracking, proof generation & MCP server mounting. Actions: add - Add a feature. params: {product, name, description, source, version, how_to_test, expected_result, status?, tags?} list - List features. params: {product?, status?, ta Inputs: action, params
`nucleus_federation`	Federation management for multi-brain coordination. Actions: status - Get comprehensive federation status join - Join a federation via seed peer. params: {seed_peer} leave - Leave the federation gracefully peers - List all federation peers Inputs: action, params
`nucleus_governance`	Governance, Hypervisor & security tools for the Nucleus Agent OS. Actions: auto_fix_loop - Auto-fix loop: Verify->Diagnose->Fix->Verify (3 retries). params: {file_path, verification_command} lock - [HYPERVISOR] Lock a file/dir immutable (ch Inputs: action, params
`nucleus_infra`	Infrastructure: file changes, cloud, marketing & strategy tools. Actions: file_changes - Get pending file change events gcloud_status - Check GCloud auth status gcloud_services - List Cloud Run services. params: {project?, region?} list_ser Inputs: action, params
`nucleus_lane_feedback`	Report friction/bugs/enhancements to the nucleus team. WHEN TO USE: when the lane misbehaves, a task fails unexpectedly, the SPEC.md format is confusing, or you have an improvement idea. Creates a GitHub issue on the public nucleus-mcp repo Inputs: feedback_type, subject, body, reporter, repo_path
`nucleus_lane_init`	Set up an autonomous task-execution loop in a git repo. WHEN TO USE: you have a list of tasks (bugs, features, tests) you want executed automatically without manual prompting — the lane runs watcher/executor/secretary daemons that claim tas Inputs: repo_path, spec_path, role, vendor, tag, force
`nucleus_lane_start`	Start autonomous lane daemons (watcher + executor + secretary) in background. WHEN TO USE: after nucleus_lane_init and SPEC.md is written — this launches the loop that autonomously claims and executes tasks. The executor invokes an LLM CLI Inputs: repo_path, executors, no_secretary, no_watcher
`nucleus_lane_status`	Check lane status: task counts (PENDING/IN_PROGRESS/DONE/CONFIRMED), daemon health, spec verification. WHEN TO USE: after starting a lane to monitor progress, or before starting to check if a lane is already running. Inputs: repo_path
`nucleus_lane_stop`	Stop all running lane daemons. WHEN TO USE: when all tasks are CONFIRMED or you want to pause autonomous execution. Inputs: repo_path
`nucleus_next_message`	Get the next unread relay message. One call — returns full message body and auto-acks. Long-poll (60s timeout). This is the agent's idle loop. Call it, get a message or None, act or re-call. No separate inbox + ack dance. The agent's loop: Inputs: recipient
`nucleus_orchestration`	Satellite view, commitments, loops, patterns & metrics. Actions: satellite - Unified satellite view. params: {detail_level?} scan_commitments - Scan artifacts for new commitments archive_stale - Auto-archive commitments older than 30 days e Inputs: action, params
`nucleus_plan_execute`	Execute a plan file autonomously. WHEN TO USE: you have a plan file (.brain/plans/*.md) you want executed autonomously — parses the plan, creates tasks, starts a mission with budget/time limits. Chains import_plan_as_tasks() then _brain_sta Inputs: plan_path, goal, budget_limit, time_limit_hours
`nucleus_plan_import`	Import a plan file as PENDING tasks without starting a mission. WHEN TO USE: you have a plan file (.brain/plans/*.md) you want loaded into the task store so the executor daemon / sprint mission can pick the tasks up later — but you don't wa Inputs: plan_path
`nucleus_plan_list`	List available plan files in .brain/plans with task counts. WHEN TO USE: you want to discover which plan files exist and how many tasks each contains before importing or executing one. Returns: JSON string: a list of dicts each with ``{"nam
`nucleus_relay`	Relay-substrate facade — post / read / ack / status. Actions: post - Send a relay envelope. params: {to, subject, body, sender?, priority?, in_reply_to?, context?, id?, from_session_id?} sender? auto-fills from your session role when omitte Inputs: action, params
`nucleus_relay_subscribe`	Long-poll subscription that pushes ctx.info() on each new inbox file. Replaces bash polling daemons (watch-relay-*.sh) with server-initiated push. Call once at session start (e.g. via SessionStart hook). Server holds the subscription, watch Inputs: timeout_seconds, role, inbox_filter
`nucleus_route`	W5 tier routing — route a prompt to the optimal model tier. Actions: route - Route a prompt to cheapest capable model. params: {prompt, complexity?, context?, estimated_output_tokens?} complexity ∈ 'routine' \| 'complex' \| 'sovereign' (defau Inputs: action, params
`nucleus_sessions`	Session management, events, state & checkpoint tools. Actions: save - Save session for later. params: {context, active_task?, pending_decisions?, breadcrumbs?, next_steps?} resume - Resume a saved session. params: {session_id?} list - List Inputs: action, params
`nucleus_slots`	Orchestration slots, sprints & mission management. Actions: orchestrate - THE GOD COMMAND. params: {slot_id?, model?, alias?, mode?} slot_complete - Mark task complete. params: {slot_id, task_id, outcome?, notes?} slot_exhaust - Mark slot e Inputs: action, params
`nucleus_sync`	Sync, artifact, trigger & deploy management for multi-agent coordination. Actions: identify_agent - Register agent identity. params: {role, provider, session_id} (per ADR-0005 §D1) OR legacy {agent_id, environment, role?} (coerced per §D5 u Inputs: action, params
`nucleus_tasks`	Task management, depth tracking & ADHD context-switch tools. Actions: list - List tasks. params: {status?, priority?, skill?, claimed_by?, required_role?} get_next - Get highest-priority unblocked task. params: {skills, required_role?} clai Inputs: action, params
`nucleus_telemetry`	LLM tiers, telemetry, PEFS notifications & protocol tools. Actions: set_llm_tier - Set default LLM tier. params: {tier} get_llm_status - Get LLM tier configuration record_interaction - Record user interaction timestamp value_ratio - Get Val Inputs: action, params
`nucleus_wakeup_wait`	Quick scan for a PENDING task. Returns the task directly if one is available, or None if no task is ready within the timeout. Default timeout is 5s (non-blocking). The agent should NOT loop on this — tasks arrive via relay push. This is a f Inputs: required_role, timeout_seconds, skills, agent_id, auto_claim

Add Nucleus to your AI client

Every block below points at https://relay.nucleusos.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal

claude mcp add --transport http nucleus https://relay.nucleusos.dev/mcp

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "nucleus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://relay.nucleusos.dev/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "nucleus": {
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "nucleus": {
      "type": "http",
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "nucleus": {
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "nucleus": {
      "serverUrl": "https://relay.nucleusos.dev/mcp"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "nucleus": {
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: Nucleus
version: 0.0.1
schema: v1
mcpServers:
  - name: Nucleus
    type: streamable-http
    url: https://relay.nucleusos.dev/mcp

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "nucleus": {
      "httpUrl": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "nucleus": {
      "type": "http",
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "nucleus": {
      "url": "https://relay.nucleusos.dev/mcp"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Frelay.nucleusos.dev%2Fmcp&type=streamable_http&id=nucleus&name=Nucleus

Is Nucleus up right now?

It answered our last check on 22 October 2026 in 916 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Nucleus

MemorySync0 tools Recall — persistent memory for agents5 tools MemoFS0 tools Mifactory Agent Memory2 tools memory0 tools MemQ Team Sync0 tools

Questions about Nucleus

How many tools does Nucleus have?

28, as returned by the server's own tools/list on 14 September 2026: nucleus_agents, nucleus_audit, nucleus_ccr_arm, nucleus_delegate, nucleus_engrams, nucleus_features, nucleus_federation, nucleus_governance, and 20 more.

Is Nucleus down?

It answered our last check on 22 October 2026 in 916 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Nucleus to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://relay.nucleusos.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Nucleus need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.eidetic-works. Endpoint host: relay.nucleusos.dev. ARD identifier: urn:air:io.github.eidetic-works:mcp:nucleus. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.