We are facing trouble connecting with Axiom MCP. Which is our primary source or the place where we post all our logs there are repeated connection/disconnection issues.
NA
This is related to Claude agents or some sort of automation that we have on top of any message that comes on Slack or to alerting channels of Slack.
Hey, thanks for the report. This is a known rough edge with cloud agents and remote MCPs like Axiom, and there’s a reliable workaround.
What’s happening: Axiom only requires auth when a tool is actually called, so on cursor.com/agents the server shows green right after the connection check, before there’s a valid token. Because of that, the OAuth step doesn’t always pop up cleanly, and reconnect can fail instead of reopening OAuth. Green status here means Cursor can reach the server, not that there’s a valid token.
For headless cloud agents, I’d recommend not relying on interactive OAuth and switching to header-based auth instead. It’s more stable. Create an Axiom token and set headers on the MCP entry instead of OAuth:
Authorization: Bearer <your-token>
x-axiom-org-id: <your-org-id>
If you can only set one header, Axiom also accepts the org via a URL param: https://mcp.axiom.co/mcp?org-id=<your-org-id>.
Setup details are in the Axiom docs: Axiom MCP Server | Axiom Docs. Cursor cloud agents support custom headers on HTTP MCP servers, so the token gets sent directly and the OAuth handshake is skipped.