BriefCase
02/13/2026, 9:33 PM@composio/mcp@latest alone (gets "Unknown argument" error)
- Config with mcp-remote (gets OAuth 501 error)
- Config with mcp-remote --http (gets "Invalid URL" error)
Already authorized 6 apps in Composio dashboard. Need working config format for Claude Desktop regular chat app.Uday
02/14/2026, 5:00 AMBriefCase
02/14/2026, 9:34 PM{
"command": "npx",
"args": [
"-y",
"mcp-remote",
"URL"
]
}Errors:
1. HTTP 501 - OAuth metadata endpoint doesn't exist
2. HTTP 403 - OAuth registration forbidden
The issue:
Setup command still generates mcp-remote wrapper which requires OAuth 2.1.
Your endpoint doesn't implement OAuth metadata at:
https://mcp.composio.dev/.well-known/oauth-authorization-server
Question:
Does Composio MCP have a STDIO-based server (not HTTP remote) for Claude Desktop?
The --client claude flag didn't change the config format - still uses mcp-remote which requires OAuth that your endpoint doesn't support.
My setup:
- macOS Claude Desktop (regular chat app)
- Customer ID: 129a0ab9-7381-469e-8036-5a6763920338
- Want: Google Drive, Docs, Sheets access via Composio
Need: Either OAuth support on your endpoint OR stdio-based MCP server that doesn't require OAuth.BriefCase
02/14/2026, 9:34 PMBriefCase
02/14/2026, 9:34 PMUday
02/15/2026, 5:06 PMx-api-key? I can share a sample config:
{
"mcpServers": {
"mcp-config-xxxxx": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"--header",
"x-api-key: ak_xxxx",
"https://backend.composio.dev/v3/mcp/<server-id>/mcp?user_id=pg-test-xxxx"
],
"env": {
"npm_config_yes": "true"
}
}
}
}Uday
02/15/2026, 5:08 PM