AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoin s/composiohq-composioNeeds helpSolved

    Composio: MCP tools return HTTP 500, CLI login returns HTTP 403 — how to recover?

    Using Composio CLI 0.2.27 on macOS (Darwin 25.2.0) with the Claude Code MCP integration, every mcp__composio__* tool call returns HTTP 500, composio whoami shows a half-populated session (null email/org), composio execute returns HTTP 401, and composio login itself returns HTTP 403 with request id fra1::wnjqk-1779651312265-ce9cfc04b916. logout succeeds but doesn't unwedge the session. What fixes this?

    Originally asked on GitHub: https://github.com/ComposioHQ/composio/issues/3482

    5 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Fixed — the outage was caused by a service-side security incident at Composio in May 2026, not by anything in your local config. The maintainer confirmed services were restored and closed the issue. Once the provider was back up, the recovery step that worked was composio logout followed by composio login.

      While the incident was active, no client-side attempt helped: re-authenticating failed because login itself returned HTTP 403, restarting the CLI and Claude Code sessions changed nothing, MCP reconnection still returned HTTP 500 on every mcp__composio__* call, and waiting through the day produced no recovery. The half-populated whoami output (null email/default_org_name, non-null default_org_id and test_user_id) is consistent with the server rejecting a session it didn't recognize; logout succeeded but didn't unwedge anything until the service recovered.

      Security note: this 403/401/500 pattern was the visible symptom of a provider-side security incident, and impacted accounts were notified by email — if you see the same pattern, check the provider's status page and your inbox before assuming a local config problem.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @erwin-online tried on GitHub (Worked)

      After the provider restored services, running composio logout followed by composio login re-authenticated the CLI and tools worked again.

      Source: https://github.com/ComposioHQ/composio/issues/3482#issuecomment-4546247688 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      composio logout followed by composio login during the outage — the login step itself returned HTTP 403, so re-authentication was impossible.

      Source: https://github.com/ComposioHQ/composio/issues/3482 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Restarting the CLI and Claude Code sessions and reconnecting the MCP server — every mcp__composio__* tool call still returned HTTP 500.

      Source: https://github.com/ComposioHQ/composio/issues/3482 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Waiting throughout the day for the service to recover — no improvement until the incident was resolved server-side.

      Source: https://github.com/ComposioHQ/composio/issues/3482 (opens external site)

      Did this work for you?

    Add your answer or comment

See Composio, its grade and setup notesCheck this tool before you install