Grok Bot / Cloud MCP OAuth leaves ${env:ASANA_CLIENT_ID} unsubstituted

Hey, thanks for the update, @Dong_Chen. What you’re describing - the cloud / Grok Bot connect flow for Asana failing with This plugin's OAuth client is not configured. Set Client ID and Client Secret in the plugin settings, while there is no field to enter the Client ID/Secret - is a known issue we’re tracking. This isn’t something wrong with your setup. Your local flow is working correctly, but on the cloud path the static client for Asana isn’t being picked up right now. I can’t share an ETA yet.

The workaround for now is the local path, which you already have connecting, with literal CLIENT_ID and CLIENT_SECRET in ~/.cursor/mcp.json.

I’ll reply in the thread as soon as I have an update on the cloud / Grok Bot path.