https://linen.dev logo
Powered by
Windows Desktop Agent using OAuth
# 🖥│support-forum
w
I can't get either Claude Desktop or Codex Desktop to establish a Composio MCP Server connection using OAuth. It seems to fail with the post authentication callback. - Claude Cowork asks me to paste in the localhost callback URL, but then complains that the flow says "no OAuth flow in progress" - Codex Desktop launches the OAuth url, I click on Allow Access, but then nothing really happens and I don't have access to Composio tools I can get Codex Desktop on a Mac to work fine. And Claude.ai (Web) connects to Composio fine. Alas, I need Claude Desktop because Cowork offers special functionality. This is super frustrating. What am I doing wrong?
codex mcp login
on Windows will launch the OAuth challenge in the browser. It seems to be working, but 
/mcp
shows no tools:
Copy code
• composio
    • Auth: OAuth
    • Tools: (none)
    • Resources: (none)
    • Resource templates: (none)
If I quit and restart codex cli, I get:
Copy code
âš  MCP client for `composio` failed to start: MCP startup failed: handshaking with MCP server failed: Send message error
  Transport
  [rmcp::transport::worker::WorkerTransport<rmcp::transport::streamable_http_client::StreamableHttpClientWorker<rmcp::tr
  ansport::auth::AuthClient<codex_rmcp_client::http_client_adapter::StreamableHttpClientAdapter>>>] error: Auth error:
  OAuth authorization required, when send initialize request

âš  MCP startup incomplete (failed: composio)
From codex cli, I can shell out to trigger an mcp login, like 
! codex mcp login composio
-- and it seems to be successful:
Copy code
• You ran codex mcp login composio
  â”” Authorize `composio` by opening this URL in your browser:
    https://login.composio.dev/oauth2/authorize?response_type=code&client_id=client_01KV2GWVVAH1PM8GHKHVDGG7JS&state=XQDjZpv1AW0NSliuQWY0aQ&code_challenge=WSkajGE44_d8LqWrRKPKf7S9pwbIJJc0rVEXdHv9hTg&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A55290%2Fcallback%2FO6YtLG_KIoXe&scope=openid+profile+email+offline_access&resource=https%3A%2F%2Fconnect.composio.dev%2Fmcp

    Successfully logged in to MCP server 'composio'.
EXCEPT that I still don't see any Tools. (Same 
/mcp
state as before.)
I discovered that the OAuth callback wasn't working because of AppContainer Isolation. Specifically, Codex needs an exemption. Read the details here: https://github.com/openai/codex/issues/26693#issuecomment-4702682117
b
Hi there, Nice debugging on the AppContainer/callback piece. The reason login looks successful but tools stay "(none)" (and a restart throws "OAuth authorization required") is that the browser OAuth callback on Windows desktop clients (Codex Desktop and Claude Cowork) doesn't reliably hand the token back to the client, so the MCP session never actually authenticates. This is a known rough edge on Windows desktop MCP clients, and I don't have a timeline to share yet. The reliable workaround is to skip OAuth and authenticate the same endpoint with an API key header instead: • In the Composio For You dashboard, open Connect > Clients and switch from the OAuth tab to the API Key tab to copy your consumer key. • Point the client at 
https://connect.composio.dev/mcp
with the header 
x-consumer-api-key: <your key>
(no browser callback involved). For Codex, that's the same server entry with this header added. If a specific client won't accept the header, reply with your config and I'll help adapt it. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.
2 Views
PreviousNext
Powered by