CONTROL PLANENEXUSDOCK
Web ConsoleMCP Gateway
RecallWorkflowAuth
Outbound WebSocket connections
AgentDockmacOS
AgentDockWindows
AgentDockLinux
Self-hosted · Open source · Built for AgentDock
One control plane.
Every AgentDock.
Connect your Macs, Windows PCs, servers and containers to one private control center. Share Recall and Workflows, inspect live Runtime state, and expose one MCP endpoint to your AI clients.
One MCP endpoint
Outbound-only nodes
Your data, your infrastructure
ChatGPT
Claude
Codex
NexusDockWeb · MCP · Recall
Mac mini Online
Windows Online
Server Online
AgentDock nodes connect out. No inbound port required.
01Fleet control
02Shared Recall
03Reusable Workflow
04Live Runtime
05Unified MCP
01 / Architecture
Your devices stay local.
Your devices stay local.
Your control plane stays yours.
NexusDock adds a shared layer above AgentDock without replacing the execution layer on each machine.
Private by design
Nodes initiate the connection. You do not need to expose every AgentDock machine to the public internet.
Execution stays local
Files, commands, browser automation and other machine-local capabilities remain on their AgentDock node.
02 / Capabilities
One place to connect.
One place to connect.
Nothing extra to operate.
01
Fleet overview
See every paired AgentDock node, its connection state, version and capabilities from a single console.
Shared Recall
Centralize searchable Markdown memory, experience cards and private notes across your devices.
project.mdrunbooks/cards/
Reusable Workflows
Publish, version, match and reuse proven workflows instead of rebuilding the same operational steps.
Live Runtime
Inspect node-local Tasks, Skills, Plugins, MCP servers and diagnostics without duplicating runtime state.
One MCP endpoint
Give AI clients one MCP address for NexusDock tools and capabilities routed to the right AgentDock node.
https://nexus.example.com/mcp
03 / Deploy
From zero to your own Nexus.
From zero to your own Nexus.
Three steps.
NexusDock ships as a multi-architecture container for Linux AMD64 and ARM64.
Start NexusDock
Run the official container with persistent volumes for Nexus state and Recall.
Pair your devices
Generate a short-lived pairing code, then connect each AgentDock node.
Connect your AI client
Point ChatGPT, Claude, Codex or another MCP client at your single NexusDock endpoint.
services:
nexusdock:
image: agentdockio/nexusdock:latest
restart: unless-stopped
ports:
- "127.0.0.1:18777:18777"
volumes:
- nexus-data:/var/lib/nexus
- recall:/recall
volumes:
nexus-data:
recall:$
docker compose run --rm nexusdock admin init admin$
docker compose up -d
NEXUSDOCK / OPEN SOURCE
Your agents already work everywhere.
Give them one home.
Self-host NexusDock, keep control of your infrastructure, and connect every AgentDock through one shared layer.