claude mcp login wrike fails at token exchange with "client_id must be supplied" despite pre-configured client ID being resolved
Status Open
Maintainer reply None cached
Activity 1 comment · opened Jul 21, 2026
Descriptionclaude mcp login wrike completes the OAuth authorize/redirect/callback steps successfully (auth code is returned from Wrike), but the final token-exchange call fails with client_id must be supplied, even though the debug log shows the client ID was already resolved three times earlier in the same flow via "Using pre-configured client ID."
Reproduced ~10 times in a row today, consistently failing at the same step.
Steps to reproduce
claude --debug-file <path> mcp login wrike- Complete the browser OAuth prompt (authorize access)
- CLI receives redirect/callback successfully
- Token exchange fails
Relevant debug log excerpt
[DEBUG] MCP server "wrike": Initial auth result: REDIRECT
[DEBUG] MCP server "wrike": MCP OAuth server cleaned up
[DEBUG] MCP server "wrike": Completing auth flow with authorization code
[DEBUG] MCP server "wrike": Returning cached discovery state (authServer: https://login.wrike.com/oauth2)
[DEBUG] MCP server "wrike": Using pre-configured client ID
[DEBUG] MCP server "wrike": Returning code verifier
[DEBUG] MCP server "wrike": Using pre-configured client ID
[DEBUG] MCP server "wrike": Using pre-configured client ID
[DEBUG] MCP server "wrike": Error during auth completion: OYt: client_id must be supplied
Expected behavior
Token exchange should include the client_id that was already resolved earlier in the same auth flow, and login should succeed.
Environment
claude mcp login wrike, MCP server URLhttps://mcp.wrike.com/v2- OAuth server:
https://login.wrike.com/oauth2 - Redirect port 8080 (from config)
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗