Skip to main content
The Streamable HTTP endpoint is /api/mcp/ on the selected deployment. MCP shares domain services with REST and the Console. It is not a generic HTTP proxy. Use this after connecting Overmind. Supply or select the named resource in your conversation; the agent reads the contract rather than guessing IDs.

Discovery and scope

Use the connected tools/list, prompts/list and resources for complete argument schemas. Tool availability depends on permissions and the deployed version; a static tool count is not a capability guarantee.

Authentication

API-key connections use X-Api-Key or a supported bearer header. Account keys reach authorized projects; project keys retain narrower scope. OAuth is supported for MCP account connections and requires the deployment’s login and consent flow. MCP OAuth tokens do not authenticate ordinary CLI file transfers. Read permission exposes inspection operations; writes require the operation’s permission scope. Expiry, account state and membership continue to apply.

Tool families

This index identifies the entry points; it does not replace their schemas. Preparation tools can create records or run preprocessing. An inspection-style name is not a guarantee of zero provider cost; read the tool’s impact and result contract before executing it.

Resources

Follow returned resource links for packages, revisions, bindings and data-first workflows. Their identifiers and pagination belong to the connected contract.

Jobs, pagination and retries

Background operations return durable identities. get_job(kind=..., id=...) reads the receipt; inspect_operation pages stored events without waking a worker. Use returned polling guidance while active and next actions after completion. Requests that accept a stable key recover the same work when the key and payload match. Changed payloads conflict. Do not assume every mutation is idempotent: run_evaluation, for example, creates new runs. Pagination can be limited by both item count and response bytes. Follow returned cursors, offsets, collections descriptors and evidence_resource links for complete retained evidence. Tool errors include a structured code, message, retryability and field details where applicable. Authentication and authorization failures remain distinct from workflow failures.

Prompts and local handoffs

Prompts include author-dataset-transformation, develop-model-from-data, investigate-capability, instrument-repository, prepare-evaluation, evaluate-change, finetune-capability, optimize-capability, compare-models, ship-model, upload-dataset-file, export-dataset, connect-traces and download-checkpoint. The CLI transfers bytes and runs local repository work. Provider secrets enter protected local configuration or the appropriate Console flow, not MCP tool arguments. See Connect your coding agent.