Production MCP API paths and direct transport tests
Warning: For consumer connections, usehttps://connect.composio.dev/mcp, not this URL.
Use HTTPS and the full production API path:
x-api-key. Avoid an HTTP URL, staging hosts, or a trailing slash on /servers, which can produce redirects. For a no-auth server, still pass auth_config_ids: [] explicitly with no_auth_apps.
When testing the returned MCP transport directly, include the Project API key, either user_id or connected_account_id, and Accept: application/json, text/event-stream. A redirect from the returned URL to the current Streamable HTTP endpoint is expected when the client follows it.
Auth configs are project-scoped
A hosted For You/consumer MCP session cannot reuse a custom auth config created in a separate Platform developer project. The session resolves configs only in its own project. For a customer-created Platform Tool Router session, bind a same-project config with its realac_* ID. A display name is not the auth-config ID, and cross-project binding is unsupported.