API Reference

MCP

This API is deprecated. Use a session's MCP endpoint instead. Create a session with composio.create(userId, { mcp: true }), then read the hosted URL off session.mcp.url. See Using sessions via MCP and migrating MCP servers to sessions.

The MCP API is the standalone, hosted Model Context Protocol server-management surface. It let you stand up and manage a separate server config per toolkit, then mint a per-user MCP URL that any MCP-compatible client could connect to.

These endpoints create, list, update, and delete MCP servers, including custom servers spanning multiple apps, generate per-user MCP URLs, and manage per-user server instances and their connected accounts.

Sessions replace this. A single composio.create(...) gives you the same MCP URL pattern, keyed by user_id, while handling tool discovery, authentication, context, and versioning for you. Your existing tools, auth configs (ac_…), and connected accounts carry over with no re-authentication. To pin a session to a fixed tool list the way a server did, use the direct-tools preset described in Configuring sessions.

Endpoints

EndpointQuick Link
GET /api/v3.1/mcp/serversList MCP servers with optional filters and pagination
POST /api/v3.1/mcp/serversCreate a new MCP server
POST /api/v3.1/mcp/servers/customCreate a new custom MCP server with multiple apps
POST /api/v3.1/mcp/servers/generateGenerate MCP URL with custom parameters
GET /api/v3.1/mcp/{id}Get MCP server details by ID
PATCH /api/v3.1/mcp/{id}Update MCP server configuration
DELETE /api/v3.1/mcp/{id}Delete an MCP server
GET /api/v3.1/mcp/app/{appKey}List MCP servers for a specific app
GET /api/v3.1/mcp/servers/{serverId}/instancesList all instances for an MCP server
POST /api/v3.1/mcp/servers/{serverId}/instancesCreate a new MCP server instance
DELETE /api/v3.1/mcp/servers/{serverId}/instances/{instanceId}Delete an MCP server instance and associated connected accounts

On this page