Hi, is the MCP still not accepting the newly generated keys? I have regenerated twice and both times it hasn't worked.

Hi @Just-a-random-guy , sorry for the trouble here. Could you share a bit more context on how you're using the MCP server? Specifically: 1. The MCP server URL you're hitting 2. The client you're connecting from (Claude Desktop, Cursor, Claude Code, n8n etc) 3. Where exactly the new key is failing (auth header, OAuth flow, etc) That'll help me figure out what's going on.

MCP Server URL: https://connect.composio.dev/mcp Client: OpenClaw Where it fails: Authorization header — Bearer token rejected immediately on connect

Same issue for both

Now I can regenerate but it still doesn't work

Theyre really dropping the ball

Hey https://connect.composio.dev/mcp -> Means you are using Composio for you?

I'm in the same boat, trying to connect to the composio for you mcp server with a hermes agent on a virtual machine. trying to authenticate with a token returns a 401 error and my agent says we need to use an OAuth url to authenticate but that won't work for my set up

hey guys sorry for the issue, we currently disable the x-consumer-api-key. it should work via oauth

just wanted to +1 this error. cant connect with my remote hermes agent because of the 401 error while trying to oauth

hey folks, quick update - we tested the consumer MCP key flow with Hermes, including VM/headless + Docker, and it's working now. For remote/headless Hermes, use

https://connect.composio.dev/mcp

with

headers.x-consumer-api-key: <your ck_... consumer key>

. Don't use

ak_

,

x-api-key

, or a custom

/mcp/<name>

URL. Can you retry with that? If it still 401s, send the Hermes version + masked config/error.