@devries-cameron20 / composio-1 / commits / d396e9288
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: clarify session setup before the first connection

Mukund committed Sep 29, 2026 at 17:43 UTC d396e92885683bfbb5e15c9f5f094ba0fba870d5
1 file changed +3 -3
docs/content/docs/extending-sessions/custom-mcp.mdx
+3 -3
@@ -5,7 +5,7 @@ keywords: [custom mcp, bring your own mcp, remote mcp, custom toolkits, experime
5 experimental: true
6 ---
7
8 -Custom MCP lets you use tools from your remote MCP server in the same session as Composio's built-in toolkits. Register the server, connect it if authentication is required, then add its synced `CUSTOM_*` toolkit slug to a session.
8 +Custom MCP lets you use tools from your remote MCP server in the same session as Composio's built-in toolkits. Register the server and add its `CUSTOM_*` toolkit slug to a session. Tool Router can then help the user connect if authentication is required.
9
10 <Callout type="warn">
11 Custom MCP is experimental. Its setup flow, authentication options, and API contracts may change while we work with early customers.
@@ -19,7 +19,7 @@ A Custom MCP moves through this lifecycle:
19
20 1. **Deploy** your MCP server at a public HTTPS URL.
21 2. **Register** its URL and authentication scheme. Composio creates a project-scoped `CUSTOM_*` toolkit.
22 -3. **Connect** an account if the server uses an API key or DCR OAuth. No-auth servers skip this step.
22 +3. **Connect** an account through a session if the server uses an API key or DCR OAuth. No-auth servers skip this step.
23 4. **Sync** its tools. The first sync starts automatically; later tool changes require a manual sync.
24 5. **Use** the toolkit in a session. Tool Router matches connected accounts to the session’s `user_id`; selecting an account explicitly is optional.
25
@@ -271,7 +271,7 @@ Deletion removes the custom toolkit and its tools. It also revokes and removes t
271
272 ## Use Custom MCP in a session
273
274 -Once the toolkit is synced, add its `CUSTOM_*` slug to a session.
274 +Add the registered toolkit’s `CUSTOM_*` slug to a session. For authenticated servers, connect an account before executing tools; the first active connection starts the initial sync.
275
276 ### Use a no-auth server
277