Reported by @surreal pumice
Bug Report: Asana MCP OAuth completes, but Codex sends an invalid token and Asana tools never become available
`Steps to Reproduce`
- Remove existing Asana MCP config:
codex mcp remove asana - Add Asana MCP again:
codex mcp add asana --url https://mcp.asana.com/v2/mcp - Complete the OAuth flow in the browser from the URL printed by the command.
- The command reports:
Successfully logged in. - Also tested the strict auth-only flow:
codex mcp login asana - That command reports:
Successfully logged in to MCP server 'asana'. - After that, launch a fresh Codex session/subprocess and
`Expected Result`
- Asana MCP should expose usable Asana tools/resources in the fresh session.
- I should be able to list accessible Asana workspaces/teams or perform any basic Asana MCP read action.
`Actual Result`
-
Fresh session does not expose usable Asana MCP actions.
-
Asana MCP worker fails with this error:
Transport channel closed, when AuthRequired(AuthRequiredError { www_authenticate_header: "Bearer realm=\"Asana MCP\", resource_metadata=\"https://mcp.asana.com/.well-known/oauth-protected-resource/v2\", error=\"invalid_token\", error_description=\"Invalid token signature - token was not issued by Asana OAuth\"" }) -
The fresh session then reports that Asana MCP tools are unavailable.
`Environment`
- Codex desktop on macOS -
codex --versionreturnedcodex-cli 0.118.0-alpha.2- Asana MCP URL:https://mcp.asana.com/v2/mcp