Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "guide" |
| 3 | title: "Hermes MCP" |
| 4 | description: "Public support knowledge for Hermes MCP." |
| 5 | category: "getting-started" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "mcp" |
| 10 | - "mcp-hermes" |
| 11 | --- |
| 12 | # Hermes MCP |
| 13 | |
| 14 | Use this for Hermes / Nous Hermes Agent customers reporting Composio MCP connection failures. |
| 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 |
| 23 | https://backend.composio.dev/api/v3.1/mcp/servers |
| 24 | https://backend.composio.dev/api/v3.1/mcp/<mcp_server_id> |
| 25 | ``` |
| 26 | |
| 27 | 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`. |
| 28 | |
| 29 | 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. |
| 30 | |
| 31 | ## Auth configs are project-scoped |
| 32 | |
| 33 | 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. |
| 34 | |
| 35 | 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. |