Mission Control
Let your agent read and update Mission Control projects, tasks, subtasks, templates, and status over streamable HTTP instead of context-switching to the web app.
Overview
Mission Control is an MCP server for the Build phase that reads and writes Mission Control projects, tasks, subtasks, templates, and status updates over authenticated HTTP.
What is this MCP server?
- Remote streamable-http MCP at mission-control-six-kohl.vercel.app/api/mcp
- Read and write projects, tasks, subtasks, and templates
- Push status updates from the agent into Mission Control state
- Bearer Authorization header with per-user MCP token from Settings → API keys
- Hosted web UI at mission-control-six-kohl.vercel.app (server v0.1.0)
- Server version 0.1.0
- Remote transport: streamable-http at /api/mcp on Vercel host
- Repository: github.com/dinof777/mission-control
What problem does it solve?
Builders lose flow when the agent cannot see or update the same task board they use to track what to ship next.
Who is it for?
Solo builders already on Mission Control who want agents to create tasks, update status, and apply templates via streamable-http MCP.
Skip if: Teams on Jira/Linear only, or anyone who cannot use a hosted remote MCP endpoint with a Bearer token.
What do I get? / Deliverables
After you generate an MCP token and configure the remote server, your agent can sync project and task state with Mission Control in both directions.
- Agent-readable project and task state from Mission Control
- Created or updated tasks, subtasks, and templates via MCP tools
- Status updates reflected in the hosted Mission Control workspace
Recommended MCP Servers
Journey fit
Mission Control is a project and task system; the canonical shelf is Build because planning and execution artifacts live there before launch-focused distribution work. PM subphase matches read/write access to projects, tasks, subtasks, templates, and status updates—the core primitives of solo product management.
How it compares
Remote PM state MCP for one hosted app, not a generic local file-based planning skill.
Common Questions / FAQ
Who is Mission Control MCP for?
Indie developers and small teams who manage work in Mission Control and want Claude Code, Cursor, or similar agents to read and write that workspace.
When should I use Mission Control MCP?
Use it during Build PM when you want the agent to update tasks, subtasks, templates, or status while implementing features or clearing a sprint list.
How do I add Mission Control to my agent?
Add the remote URL https://mission-control-six-kohl.vercel.app/api/mcp with Authorization Bearer and your MCP token from Settings → API keys → Generate MCP token, then restart the MCP client.