@devries-cameron20 / composio Mirror · read-only / commits / cc46750e1
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, 09:45 UTC

docs: warn where backend.composio.dev MCP URLs first appear (#4828)

Follow-up to #4827. Agents such as Muse keep picking up `backend.composio.dev` URLs from the docs when connecting an MCP client to Composio Connect. Adds a warning right before the first `backend.composio.dev` MCP URL on each page that has one, pointing existing clients to `https://connect.composio.dev/mcp`: - Single Toolkit MCP: in "Use with AI providers", before the first server URL (replaces the top-of-page note from #4827) - Migrating MCP servers to sessions: before the old-URL example - Hermes MCP KB guide: before the production API paths (source, article and generated page) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

akram-composio committed Oct 13, 2026 at 05:33 UTC cc46750e1696364b78849d5a061f667b5bee3b23
5 files changed +14 -4
docs/content/docs/migration-guide/mcp-servers-to-sessions.mdx
+4
@@ -124,6 +124,10 @@ re-auth.
124 Swap the generated server URL for `session.mcp.url` wherever your agent connects. Nothing else about
125 the client changes.
126
127 +<Callout type="warn">
128 +For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
129 +</Callout>
130 +
131 ```python
132 # Before: https://backend.composio.dev/v3/mcp/<SERVER_ID>?user_id=<USER_ID>
133 # After: session.mcp.url
docs/content/docs/single-toolkit-mcp.mdx
+4 -4
@@ -9,10 +9,6 @@ deprecated: true
9 For most use cases, use a regular [session](/docs/configuring-sessions) instead. Sessions provide dynamic tool access and a much better MCP experience with context management handled by us.
10 </Callout>
11
12 -<Callout type="info" title="Connecting an existing MCP client?">
13 -The `backend.composio.dev` URLs on this page are for MCP servers you create with the SDK. To connect an existing client such as Claude, ChatGPT, Cursor or Muse, use [Composio Connect](/docs/composio-connect) at `https://connect.composio.dev/mcp`.
14 -</Callout>
15 -
12 ## Install the SDK
13
14 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -133,6 +129,10 @@ console.log("MCP Server URL:", instance.url);
129 Pass an `x-api-key` header when connecting to Composio MCP. This is required when `require_mcp_api_key` is enabled (default for newly created organizations).
130 </Callout>
131
132 + <Callout type="warn">
133 + For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
134 + </Callout>
135 +
136 <Tabs items={['OpenAI (Python)', 'Anthropic (Python)', 'Mastra (TypeScript)']}>
137 <Tab value="OpenAI (Python)">
138 ```python
docs/content/kb/guide/mcp-mcp-hermes.mdx
+2
@@ -13,6 +13,8 @@ Use these checks to troubleshoot Composio MCP connection failures in Hermes / No
13
14 ## Production MCP API paths and direct transport tests
15
16 +**Warning:** For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
17 +
18 Use HTTPS and the full production API path:
19
20 ```text
docs/kb/articles/mcp-mcp-hermes.md
+2
@@ -2,6 +2,8 @@ Use these checks to troubleshoot Composio MCP connection failures in Hermes / No
2
3 ## Production MCP API paths and direct transport tests
4
5 +**Warning:** For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
6 +
7 Use HTTPS and the full production API path:
8
9 ```text
docs/kb/source/mcp/mcp-hermes/public.md
+2
@@ -15,6 +15,8 @@ Use this for Hermes / Nous Hermes Agent customers reporting Composio MCP connect
15
16 ## Production MCP API paths and direct transport tests
17
18 +**Warning:** For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
19 +
20 Use HTTPS and the full production API path:
21
22 ```text