MODEL CONTEXT PROTOCOL

Two integration paths.
Different runtime contracts.

MESA v0.9.3 supports direct V4 stdio with mesa mcp-config, plus a separately managed HTTP gateway and local bridge.

DIRECT V4 · LOCAL

Direct stdio server

mesa_mcp.server runs a V4 JSON-RPC stdio stream against the HTTP API. Run mesa start, then mesa mcp-config to generate the private client configuration. Tool approvals come from the MCP client and access comes from the API key’s grants.

stdioHTTP APIproject scope

CURRENT V4 PATH

Gateway + local bridge

A separately supervised HTTP gateway owns credentials, policy, approvals, operation state, and connections. Codex can connect directly to its /mcp endpoint; Antigravity uses a binding-scoped stdio bridge.

V4approvalsbinding-scoped

V4 BRIDGE TOOLS

Operations expose
their real state.

Writes return durable operation IDs. Default policy may return PENDING_APPROVAL rather than holding stdio open.

mesa_healthBridge, gateway, MESA, and spool health
mesa_recallScoped V4 search or token-bounded context
mesa_rememberDurable write operation
mesa_improveRevision operation with idempotency key
mesa_forgetPurge operation; never queued offline
mesa_get_operation_statusApproval and mutation progress

BOUNDARY NOTES

  • stdout is reserved for MCP JSON-RPC; logs go to stderr
  • bridges do not import or access storage backends
  • credentials live outside project configuration
  • missing client/workspace bindings fail closed
  • the exact supported host depends on the selected integration path