Skip to main content
The mcp command group resolves a project’s Model Context Protocol (MCP) endpoint so an external agent can connect to it without a hand-pasted URL. Every Machina project exposes an MCP server at its Client-API base (the api claim in the project token) plus a fixed path. mcp url derives that endpoint for you.
Wiring an external agent? Use connect. mcp url returns just the raw endpoint (URL, transport, auth header). To get a ready-to-register connection with the auth token paired in (and optionally a durable minted key), use machina connect instead.

​
url — resolve the MCP endpoint

The endpoint is: --probe confirms a reachable SSE endpoint (not full MCP protocol conformance) — use it to catch an org-client-deployed project whose MCP host differs from its api host, rather than handing out an unverified URL.
  • connect — resolve the endpoint and pair the auth token for an external agent (e.g. sportsclaw), with --mint for a durable dedicated key.