@devries-cameron20 / composio Mirror · read-only / commits / f571fca6c
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 11:00 UTC

docs: remove unnecessary custom MCP setup instructions

Mukund committed Sep 30, 2026 at 09:25 UTC f571fca6cd800998c56c3f90bfdb4a5d0f128480
1 file changed +7 -46
docs/content/docs/extending-sessions/custom-mcp.mdx
+7 -46
@@ -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 and add its `CUSTOM_*` toolkit slug to a session. Tool Router can then help the user connect if authentication is required.
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.
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,9 +19,9 @@ 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 through a session if the server uses an API key or DCR OAuth. No-auth servers skip this step.
22 +3. **Connect** an account 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.
24 +5. **Use** the toolkit in a session.
25
26 <Callout type="warn" title="API-only while Custom MCP is experimental">
27 Use the lifecycle endpoints below to register, sync, and delete Custom MCP toolkits. You can also use the experimental SDK methods described below. These contracts may change while Custom MCP is experimental. The API reference has the full request and response schemas for [upsert](/reference/api-reference/toolkits/postCustomToolkitsUpsert), [sync](/reference/api-reference/toolkits/postCustomToolkitsSync), and [delete](/reference/api-reference/toolkits/deleteCustomToolkitsBySlug). Dashboard management is coming soon for customers who prefer a UI.
@@ -162,47 +162,11 @@ Choose the mode that matches your server, then complete any required connection:
162 | Authentication | Use it when | After registration |
163 | --- | --- | --- |
164 | No auth | The server accepts requests without credentials. | No connection is required. Initial sync runs automatically. |
165 -| API key | Each connected account supplies an API key. | Use Tool Router to collect the key and create a connection. Initial sync then starts in the background. |
166 -| DCR OAuth | The server supports OAuth Dynamic Client Registration. | Use Tool Router to start authorization. Initial sync starts when the connection becomes active. |
165 +| API key | Each connected account supplies an API key. | Create an active connection. Initial sync then starts in the background. |
166 +| DCR OAuth | The server supports OAuth Dynamic Client Registration. | Authorize a connection. Initial sync starts when it becomes active. |
167
168 For DCR OAuth, the server must support the standard authorization-code flow. Other OAuth grant types aren't supported.
169
170 -### Let Tool Router manage authentication
171 -
172 -Add the registered `CUSTOM_*` toolkit to a session. When your agent needs a connection, `COMPOSIO_MANAGE_CONNECTIONS` can create an auth config automatically and return a link for the user to connect. No-auth servers need neither an auth config nor a connection.
173 -
174 -Tool Router reuses eligible connections for the session’s `user_id`. You don't need to create an auth config yourself or pass a connected account ID for this flow.
175 -
176 -### Create an auth config yourself (optional)
177 -
178 -For a setup flow you manage directly through the API, you can create the auth config yourself. Set `is_enabled_for_tool_router` to `true` so Tool Router can use it and match its connected accounts by `user_id`:
179 -
180 -```bash
181 -curl --request POST \
182 - --url https://backend.composio.dev/api/v3.1/auth_configs \
183 - --header "x-api-key: $COMPOSIO_API_KEY" \
184 - --header "Content-Type: application/json" \
185 - --data '{
186 - "toolkit": { "slug": "CUSTOM_ACME" },
187 - "auth_config": {
188 - "type": "use_custom_auth",
189 - "authScheme": "API_KEY",
190 - "credentials": {},
191 - "is_enabled_for_tool_router": true
192 - }
193 - }'
194 -```
195 -
196 -Tool Router enables this flag on auth configs it creates automatically. If you created a config yourself without the flag, enable it to make its connections available for automatic matching:
197 -
198 -```bash
199 -curl --request PATCH \
200 - --url https://backend.composio.dev/api/v3.1/auth_configs/ac_xxxxxxxx \
201 - --header "x-api-key: $COMPOSIO_API_KEY" \
202 - --header "Content-Type: application/json" \
203 - --data '{ "type": "custom", "is_enabled_for_tool_router": true }'
204 -```
205 -
170 ## Sync and resync tools
171
172 Call `POST /api/v3.1/custom/toolkits/sync` to fetch the server's current tools:
@@ -271,7 +235,7 @@ Deletion removes the custom toolkit and its tools. It also revokes and removes t
235
236 ## Use Custom MCP in a session
237
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.
238 +Once the toolkit is synced, add its `CUSTOM_*` slug to a session.
239
240 ### Use a no-auth server
241
@@ -311,9 +275,7 @@ With the default search-first session, your agent can discover the custom tools
275
276 ### Use an authenticated server
277
314 -Create the session with the toolkit slug as in the example above. Tool Router can [create the auth config and start a connection](#let-tool-router-manage-authentication) when needed, then use the connected account for the session’s `user_id`.
315 -
316 -If you need a specific account, you can pin it explicitly:
278 +Use the same session configuration shown above. To select a specific connected account, pass its ID:
279
280 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
281 <Tab value="Python">
@@ -406,7 +368,6 @@ See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning) for more example
368 </Accordion>
369 <Accordion title="Sessions and tool APIs">
370
409 -- **Manually created auth configs:** set `is_enabled_for_tool_router: true` to make their connections available for automatic matching. Tool Router sets this flag on configs it creates automatically.
371 - **Prefer the v3.1 tools API:** The v3 tools API pins a default version that doesn't contain custom tools. If you must use v3, explicitly select `latest` as described above.
372
373 </Accordion>