Models and tools
MCP server
An MCP server integration connects a remote Model Context Protocol (MCP) server to Mobius so agents can call that server's tools.
Use MCP when you already operate a tool server and want agents to use it without turning each tool into a Mobius-managed action. MCP tools are discovered dynamically from the connected server.
Capability map
| Capability | Value |
|---|---|
| Provider ID | mcp |
| Auth kind | api_key |
| Connect flow | Endpoint URL with none, bearer, API key, custom header, or OAuth auth |
| Actions | Dynamic tools |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | Yes |
Connect an MCP server
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose MCP server, and provide the endpoint, auth mode, and optional action prefix. |
| CLI | The mobius CLI does not connect MCP servers yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/mcp/connect with the server endpoint, auth fields, and optional action_prefix. |
Choose a stable action prefix. Mobius rejects prefixes that collide with
reserved provider namespaces such as slack, github, or table.
Actions
MCP does not register static action names at boot. After connecting a server, list its live tools:
curl "$MOBIUS_API_URL/v1/projects/platform/integrations/<integration-id>/mcp/tools" \
-H "Authorization: Bearer $MOBIUS_API_KEY"The response returns the tool names agents can call, plus an ok verdict and a
message when the server is unreachable.
Events
MCP server integrations do not register source events.
Next
- Give agents access through toolkits and skills.
- Check provider readiness from integrations.
- Use custom code with workers when the tool should run in your process instead.