MC
Mid Conversation
MCP tool reference
Mission Control MCP
MCP tools, contracts, and client integration at a glance
Mission Control runs one shared MCP contract layer for ticket operations. Codex and VS Copilot use the same tool set and schema so ticket automation stays consistent across clients.
7
Production MCP tools
3
Client contexts supported
1
Shared contract surface
Current Tool Matrix
Canonical server path: tools/mcp/mission_control_server.py and tool specs in tools/mcp/mission_control_tools.py.
| Tool | Primary purpose | Key output focus |
|---|---|---|
| ticket_create | Create SQL tickets with directives, tags, and project association. | Canonical ticket id, directive set, and intake metadata. |
| ticket_get | Fetch merged ticket state (markdown + DB), directives, files, and bootstrap context. | Ticket detail payload, source-of-truth marker, worker bootstrap. |
| ticket_validate_handoff | Validate required sections and directive hygiene before handoff/closure. | Pass/fail summary, missing sections, recommendations. |
| ticket_sync | Run canonical markdown-to-DB sync through the ticket sync pipeline. | Sync success, command metadata, guardrail status. |
| ticket_regen_brief | Regenerate AI brief/development story snapshots from current ticket state. | Refresh status, snapshot source, updated metadata. |
| ticket_repo_state | Capture branch/head/dirty state for commit-discipline checks and audit context. | Dirty count, samples, upstream/ahead/behind status. |
| echo_guidance_get | Return effective Echo Guidance so clients align with operator preference settings. | Effective guidance object + personality projection data. |
Client Integration (Codex + VS Copilot)
Both clients use the same tool contracts and route tool calls through the Mission Control MCP runtime.
| Client | Transport/runtime | Telemetry actor/client labels | Status |
|---|---|---|---|
| Codex Desktop | MCP stdio JSON-RPC against mission_control_server.py --serve-stdio. |
actor=Codex, client=codex-desktop, source_label=codex-desktop. |
Supported |
| Visual Studio + GitHub Copilot | Same MCP stdio contract and tool schemas. | actor=GitHub Copilot, client=vscode-copilot, source_label=vscode-copilot. |
Supported |
| CLI / automation checks | Direct tool calls via --call mode for audits and scripted validation. |
Configurable via --actor-context, --client, and --source-label. |
Supported |
Actor parity validator:
tools/mcp/verify_actor_parity.py checks that Codex and VS Copilot invocations both appear in MCP telemetry buckets.
Quick Verification Commands
Run these from the workspace root when validating MCP behavior locally.
python3 tools/mcp/mission_control_server.py --pretty
python3 tools/mcp/mission_control_server.py --call ticket_repo_state --arguments "{}"
python3 tools/mcp/verify_actor_parity.py --api-base http://127.0.0.1:5001
Step 1: Schema sanity
Use
--pretty to inspect exported tool schemas and confirm the expected tool inventory.
Step 2: Runtime call
Call
ticket_repo_state to validate server invocation path and response serialization.
Step 3: Actor parity
Run parity checks to ensure Codex and VS Copilot telemetry attribution stays aligned.