Okto Nexus MCP
A local MCP server for coordinating teams of agents: identities, messages, handoffs and a live dashboard in one repo.
- 107 ★ on the repository
- Last commit
Extended access
Why this level
- By default the server listens on all network interfaces and agent access is governed by keys and policies.
- With permission, agents accept and run tasks from other agents.
Install
- Works in
Manual install
uv tool install "okto-nexus[serve]"Then okto-nexus serve. Connect an MCP client to http://127.0.0.1:8202/mcp with an agent key.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- By default the server listens on all network interfaces and agent access is governed by keys and policies.
- With permission, agents accept and run tasks from other agents.
This is third-party code. Review the repository files before installing.
What it does
Okto Nexus is an MCP server and operator dashboard for agents working in one repository. Agents get durable identities, presence, messages with inbox lanes, handoffs, artifacts, an event log and governance controls without a cloud broker. `okto-nexus serve` brings everything up on one port: `/mcp` for MCP over streamable HTTP authenticated as an agent, `/api/v1` for operator REST and SSE, and the root serves the bundled React dashboard. Messages are delivered through lanes with leases, redelivery and acknowledgements, and a task goes to exactly one worker with optional verification and dependencies. Routing works by name, capability, role, tag or broadcast. Records live in one SQLite database in WAL mode. Before starting, an agent calls `agent_whoami`, `workspace_resolve` and `session_open` and then works through its inbox.
Who it is for. People running several agents on one project who want shared message queues, task handoffs and permission control.
Good fit when
- Two agents share a repository and one must hand a task to the other with an acknowledgement.
- A message between agents must not be lost and needs redelivery and delivery confirmation.
- An operator needs a dashboard showing which agents are present and what sits in queues.
- Agent roles, permissions and communication scopes are set by explicit rules.
Not a fit when
- An agent works alone: coordination only complicates setup.
- You need a public multi-tenant broker: the server targets a local or controlled single-tenant setup.
- You need a store other than SQLite: there are no other adapters.
Example request
Sign in as an agent, resolve the project workspace, check the inbox and hand the testing task to the agent with the qa role.MCP
- Transport
- http
- Authentication
- API key
Environment variables
OKTO_NEXUS_HOST- Listen address, all interfaces by default.
OKTO_NEXUS_RUNTIME_HANDOFF_AUTO_CLAIM_ENABLED- Allows auto-claiming work from broadcasts, on by default at startup level.
Limitations
Python 3.11 or newer is required, and the full bundle with the dashboard and local embeddings installs as `okto-nexus[serve]`. By default the server listens on `0.0.0.0:8202`, all interfaces: pass `--host 127.0.0.1` for access from this machine only. The server does not terminate TLS, so remote access needs an authenticated proxy. Agent keys are stored as hashes and shown once, while session secrets sit in the database in plain text. Auto-claiming work from a broadcast is off by default and needs four conditions. Version 0.3.0 is in development and memory is experimental.
How to disable. Stop `okto-nexus serve`, remove the `okto-nexus` entry from the client config and the package with `uv tool uninstall okto-nexus`. Data lives in `~/.okto_nexus`.
FAQ
How do I start the server?
Run `uv tool install "okto-nexus[serve]"`, then `okto-nexus serve`. The dashboard opens at `http://127.0.0.1:8202/` and MCP is at `/mcp`.
How do I get an agent key?
In the dashboard open Agents, then New agent. Copy the `nxs_` key right away: the server stores only a hash and will not show it again.
What should an agent do on its first turn?
Call `agent_whoami`, then `workspace_resolve` with an absolute path and `session_open`. Then work through the inbox and anchor an event cursor.
How do I close network access?
Start with `--host 127.0.0.1`. For remote access put a TLS proxy with authentication in front of the server.
Where is data stored?
In `~/.okto_nexus/nexus.db`, a SQLite database in WAL mode. Do not commit the database and sidecar files.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for a shared agent room: decisions, tasks verified by another agent and a final report, joined by code.
PromptOps keeps Claude Code, Codex and Gemini CLI side by side by project and gives a lead agent MCP to launch helpers
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A mail server for agents sharing one repository: messages, threads, file reservations and a 16-screen TUI
A persistent memory MCP server for agents: observations, beliefs, goals and dream consolidation across 60 tools.
Shared company context for agents over MCP: an event graph with permissions, approvals and audit
README in short
The README covers installation, startup, connecting an MCP client, the agent pre-flight, the coordination model and configuration. Separate sections cover migrations, errors and security limits.