wehub-resource-sync
21 lines
3.7 KiB
Plaintext
21 lines
3.7 KiB
Plaintext
---
|
|
title: MCP
|
|
description: "MCP server management"
|
|
---
|
|
|
|
{/* Auto-generated from OpenAPI spec. Edit the overview at api-overviews/mcp.mdx, not this file. */}
|
|
|
|
<Callout type="warning">
|
|
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](/docs/sessions-via-mcp) and [migrating MCP servers to sessions](/docs/migration-guide/mcp-servers-to-sessions).
|
|
</Callout>
|
|
|
|
The MCP API is the standalone, hosted [Model Context Protocol](https://modelcontextprotocol.io) 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](/docs/configuring-sessions).
|
|
|
|
## Endpoints
|
|
|
|
<ApiEndpointsTable endpoints={[{"method":"GET","pathV31":"/api/v3.1/mcp/servers","pathV3":"/api/v3/mcp/servers","summary":"List MCP servers with optional filters and pagination","href":"/reference/api-reference/mcp/getMcpServers"},{"method":"POST","pathV31":"/api/v3.1/mcp/servers","pathV3":"/api/v3/mcp/servers","summary":"Create a new MCP server","href":"/reference/api-reference/mcp/postMcpServers"},{"method":"POST","pathV31":"/api/v3.1/mcp/servers/custom","pathV3":"/api/v3/mcp/servers/custom","summary":"Create a new custom MCP server with multiple apps","href":"/reference/api-reference/mcp/postMcpServersCustom"},{"method":"POST","pathV31":"/api/v3.1/mcp/servers/generate","pathV3":"/api/v3/mcp/servers/generate","summary":"Generate MCP URL with custom parameters","href":"/reference/api-reference/mcp/postMcpServersGenerate"},{"method":"GET","pathV31":"/api/v3.1/mcp/{id}","pathV3":"/api/v3/mcp/{id}","summary":"Get MCP server details by ID","href":"/reference/api-reference/mcp/getMcpById"},{"method":"PATCH","pathV31":"/api/v3.1/mcp/{id}","pathV3":"/api/v3/mcp/{id}","summary":"Update MCP server configuration","href":"/reference/api-reference/mcp/patchMcpById"},{"method":"DELETE","pathV31":"/api/v3.1/mcp/{id}","pathV3":"/api/v3/mcp/{id}","summary":"Delete an MCP server","href":"/reference/api-reference/mcp/deleteMcpById"},{"method":"GET","pathV31":"/api/v3.1/mcp/app/{appKey}","pathV3":"/api/v3/mcp/app/{appKey}","summary":"List MCP servers for a specific app","href":"/reference/api-reference/mcp/getMcpAppByAppKey"},{"method":"GET","pathV31":"/api/v3.1/mcp/servers/{serverId}/instances","pathV3":"/api/v3/mcp/servers/{serverId}/instances","summary":"List all instances for an MCP server","href":"/reference/api-reference/mcp/getMcpServersByServerIdInstances"},{"method":"POST","pathV31":"/api/v3.1/mcp/servers/{serverId}/instances","pathV3":"/api/v3/mcp/servers/{serverId}/instances","summary":"Create a new MCP server instance","href":"/reference/api-reference/mcp/postMcpServersByServerIdInstances"},{"method":"DELETE","pathV31":"/api/v3.1/mcp/servers/{serverId}/instances/{instanceId}","pathV3":"/api/v3/mcp/servers/{serverId}/instances/{instanceId}","summary":"Delete an MCP server instance and associated connected accounts","href":"/reference/api-reference/mcp/deleteMcpServersByServerIdInstancesByInstanceId"}]} />
|