Orbitali Docs

MCP Integrations

Discover connected MCP servers and assign their tools to Orbitali agents.

MCP integrations are connected in the Orbitali dashboard. The public API can inspect those connections and select which advertised tools an agent may use. Authentication credentials and OAuth tokens remain server-side and are never returned by these endpoints.

All endpoints use API key authentication:

Authorization: Bearer $ORBITALI_API_KEY

Endpoints

MethodPathDescription
GET/public/v1/mcp/serversList the organization's connected MCP servers
GET/public/v1/agents/{agent_id}/mcp-toolsList an agent's selected connected MCP tools
PUT/public/v1/agents/{agent_id}/mcp-toolsReplace an agent's connected MCP tool selections

Discover integrations

curl https://api.orbitali.ai/public/v1/mcp/servers \
  -H "Authorization: Bearer $ORBITALI_API_KEY"

Each result includes the integration name, status, authentication type, and cached MCP tool definitions. Only integrations with status: "active" can be assigned. Secret headers, OAuth tokens, and client credentials are omitted.

Assign tools to an agent

First discover the server ID and exact tool names, then replace the agent's complete MCP tool selection:

curl https://api.orbitali.ai/public/v1/agents/$AGENT_ID/mcp-tools \
  -X PUT \
  -H "Authorization: Bearer $ORBITALI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "mcpServerId": "40000000-0000-4000-8000-000000000001",
      "toolName": "find_available_times",
      "enabled": true
    },
    {
      "mcpServerId": "40000000-0000-4000-8000-000000000001",
      "toolName": "book_appointment",
      "enabled": true
    }
  ]'

PUT replaces all current MCP tool selections. Send [] to clear them. A server from another organization, an inactive connection, or a tool name not advertised by the integration is rejected.

On this page