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, 06:00 UTC
| 1 | Use these checks to troubleshoot Composio MCP connection failures in Hermes / Nous Hermes Agent. |
| 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 |
| 10 | https://backend.composio.dev/api/v3.1/mcp/servers |
| 11 | https://backend.composio.dev/api/v3.1/mcp/<mcp_server_id> |
| 12 | ``` |
| 13 | |
| 14 | Pass the Project API key in `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`. |
| 15 | |
| 16 | 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. |
| 17 | |
| 18 | ## Auth configs are project-scoped |
| 19 | |
| 20 | 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. |
| 21 | |
| 22 | For a customer-created Platform Tool Router session, bind a same-project config with its real `ac_*` ID. A display name is not the auth-config ID, and cross-project binding is unsupported. |