Mission Control MCP

A self-hosted control plane for running several agents: task dispatch, run review, spend tracking, connected via MCP, CLI or REST

  • 6,486 ★ on the repository
  • Last commit
  • MIT
MCP serverOfficial

Broad access

Why this level

  • Stores API keys and credentials for controlling several agents
  • Lets callers register agents and dispatch tasks to them programmatically
  • The README explicitly warns to keep the instance on a trusted network without a TLS reverse proxy
All reasons and checks

builderz-labs/mission-control

Install

Manual install

git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
bash install.sh --local

Local install from source, needs Node.js 22+ and pnpm.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Stores API keys and credentials for controlling several agents
  • Lets callers register agents and dispatch tasks to them programmatically
  • The README explicitly warns to keep the instance on a trusted network without a TLS reverse proxy

This is third-party code. Review the repository files before installing.

What it does

Mission Control is a separate self-hosted app with a web dashboard and a SQLite database that sits above agent runtimes like OpenClaw, Claude Code or Codex without replacing their reasoning loop. It registers agents, assigns and dispatches tasks, tracks runs through a quality review gate, keeps memory and a skills registry, and tallies spend and token use. An agent connects over the REST API with an API key, through the built-in CLI, or through an MCP server added to Claude Code with one command. It fits when several agents or runtimes work in parallel and it is hard to tell who owns what and what already passed review.

Who it is for. For anyone running several agents or runtimes in parallel who wants one dashboard for tasks, review and spend.

Good fit when

  • Several agents work in parallel and it is unclear who owns what and what already passed review
  • You want unified spend and token tracking across all agents and runtimes
  • You need to dispatch tasks to an agent programmatically over REST, CLI or MCP and watch the queue

Not a fit when

  • A single agent on a single machine already stays understandable from its native CLI
  • You need a managed multi-tenant SaaS rather than a self-hosted control plane
  • The project is still alpha and you cannot tolerate schema or API changes between releases

Example request

Register me as agent scout in Mission Control and show me my task queue

MCP

Transport
stdio
Authentication
API key

Environment variables

MC_URL required
Address of the deployed Mission Control instance.
MC_API_KEY required, secret
API key from Settings after the first setup.

Limitations

The project is alpha, schema and API can change between releases. It runs as a separate Next.js service with SQLite, needs a first admin account and an API key to store. Live session messaging needs a connected runtime gateway, some features are unavailable without one.

How to disable. Stop the Mission Control container or process and remove the MCP connection with claude mcp remove mission-control.

FAQ

Does Mission Control replace the agent's reasoning loop?

No, the README states the control plane sits above runtimes and does not replace their reasoning and tool loop, it gives operators one place to see and govern the work.

Is a runtime gateway required?

Not for tasks, spend tracking or skills, but live session messaging needs a connected gateway for that specific runtime.

Discussion

No questions or reviews yet.

A self-hosted task board for people and agents: agents claim cards over MCP, and the receipt log cannot be rewritten.

MCP serverExtended access115Repository stars

A CLI that keeps Claude Code agents running around the clock in PTY sessions, steered from Telegram, a dashboard and cron.

CLIBroad access107Repository stars

CLI dispatcher for agents: tasks run in the background and the agent sleeps on a question until you reply from a messenger.

CLIBroad access4.6KRepository stars
Official

apra-fleet runs a fleet of AI agents across machines and models through MCP and drives multi-hour workflows

MCP serverBroad access106Repository stars

Agents for recurring work in Markdown files: schedules, approval of important actions, run history in a dashboard and a Mac app

CLIExtended access208Repository stars

Orchestrator for Claude Code, Codex and Gemini CLI: YAML workflows that loop until your own quality gates pass

CLIBroad access334Repository stars

README in short

The README frames Mission Control as a self-hosted control plane for operators, sitting above OpenClaw, Claude Code, Codex and other runtimes. It lists its scope: tasks with a quality review gate, agent registration and presence, an activity stream, memory and a skills registry, roles and audit, plus Web UI, CLI, MCP server and REST API interfaces. It explicitly states when the tool is the wrong fit: a single agent on one machine, a need for managed SaaS, or an inability to tolerate alpha status. Install is via docker compose or a source build with Node.js and pnpm, MIT licensed.

README badge

Report a problem