Skip to main content
“MCP” shows up in two directions in Machina, and they’re easy to conflate because both ultimately talk to the same kind of endpoint. Keep them separate:

MCP Builder (outbound)

Compose a server that exposes your project’s workflows, agents, prompts, and connector operations as tools — for an external agent to call.

External MCP (inbound)

Connect your project to someone else’s MCP server, so its tools become available to the Studio Copilot.

​
The one thing both share: the connection endpoint

Every Machina project has an MCP endpoint at its Client-API base plus a fixed path: Whatever tools MCP Builder publishes (outbound) show up on this same endpoint. Resolve it with machina mcp url, or get it paired with an auth token ready to hand to an external agent with machina connect. See Connecting External Agents for ready-to-paste snippets (Claude Code, Cursor, Codex, Claude Desktop).

​
Quick decision guide

  • “I want an external agent (SportsClaw, Claude Code, Cursor…) to call things in my project” → MCP Builder to choose what’s exposed, then Connecting External Agents to wire the client.
  • “I want my project’s Copilot to use tools from someone else’s MCP server” → External MCP.