MCP server

openloop mcp runs a Model Context Protocol server over stdio (newline-delimited JSON-RPC 2.0, protocol 2025-06-18). Any MCP client, an editor agent, a chat assistant, another orchestrator, can inspect and steer the fleet with it.

Register it

In an MCP client config (Claude Code, Cursor, etc.) add a stdio server:

{
  "mcpServers": {
    "openloop": {
      "command": "openloop",
      "args": ["mcp"]
    }
  }
}

Tools

Tool	Effect
openloop_list_projects	Registered projects and their queue counts
openloop_list_tasks	Tasks for a project, filterable
openloop_add_task	Create a task (title, kind, risk, scope)
openloop_task_show	Full task detail
openloop_promotion_queue	Pending promotions
openloop_digest	Fleet confidence digest
openloop_budget_status	Daily spend vs. ceiling
openloop_pause / openloop_resume	Hold or restart scheduling

What it’s for

The MCP surface is deliberately narrow and safe:

• Queuing work: “add a task to api to rate-limit login attempts” from wherever you’re already talking to an agent.
• Reviewing: pull the promotion queue and digest into a conversation before deciding.
• Coordinating: an editor agent can pause the loop while it works in a repo, then resume, no competing writes.

Mutations are limited to adding tasks and pausing/resuming; promotions are still applied by humans (or by the daemon); the MCP server cannot merge anything.