# Asana connector

**URL:** <https://forum.cursor.com/t/asana-connector/173426>\
**Category:** Bug Reports\
**Tags:** mcp, grok-bot\
**Created:** [September 30, 2026, 4:39pm UTC](https://forum.cursor.com/t/asana-connector/173426 "2026-09-30T16:39:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Carroll](https://avatars.discourse-cdn.com/v4/letter/k/9fc348/32.png) [@Kevin\_Carroll](https://forum.cursor.com/u/Kevin_Carroll)\
**Post date:** [September 30, 2026, 4:39pm UTC](https://forum.cursor.com/t/asana-connector/173426/1 "2026-09-30T16:39:35Z")

</div>

### Where does the bug appear (feature/product)?

Grok Bot

### Describe the Bug

Asana connector sign-in fails with invalid\_request: The redirect\_uri parameter does not match a valid url for the application, since about 10:25 AM ET on 9/30. It affects my three Asana accounts, and the connector has now disappeared from the list.

### Steps to Reproduce

Steps to reproduce:

In Grok Bot, the Asana connector (Asana MCP) has been working normally for weeks, with three accounts: default, “cos” and “rls”.  
At about 10:25 AM ET on 9/30/2026, all three accounts suddenly switched to needing authentication.  
Start the Asana sign-in from Grok Bot for any account.  
Asana’s OAuth page returns “invalid\_request: The redirect\_uri parameter does not match a valid url for the application” and never shows the approve screen.  
It happens every time. I tried three times, including one forced re-auth, and got the same error each time.  
By about 11:10 AM ET the Asana connector had disappeared from the agent’s connector list completely. Gmail, Calendar, Drive, Slack and others still work.

### Expected Behavior

Expected: the Asana sign-in completes and the connector reconnects.  
Actual: the redirect\_uri mismatch error, and now the connector is missing.

### Operating System

Windows 10/11

### Version Information

0.63.0

grokbot://app/v1/settings?id=update-channel

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [September 30, 2026, 7:52pm UTC](https://forum.cursor.com/t/asana-connector/173426/6 "2026-09-30T19:52:35Z")

</div>

Hey @Kevin_Carroll, thanks for the report.

Around 10 AM ET, Asana stopped accepting the saved sign-in for your Asana connector, which is why all three accounts switched to needing authentication together. The connector itself is still saved on your account. It just drops out of the agent’s connector list until it is signed in again.

The redirect\_uri error comes from Asana. It means the Asana app your connector is configured with (the one whose Client ID was entered when the connector was set up) doesn’t list the callback address Grok Bot uses for sign-in. Could you try this:

1. Open the Asana developer console at [Log in - Asana](https://app.asana.com/0/my-apps) and select that app.
2. Open its OAuth settings and find Redirect URLs.
3. Add [Cursor Agent - Turn your ideas into code](https://www.cursor.com/agents/mcp/oauth/callback) and save. Leave any existing URLs in place.
4. In Grok Bot, start the Asana sign-in again for the default account.
5. Once that works, repeat the sign-in for “cos” and “rls”.

If Asana still shows the redirect\_uri error after step 4, reply with a screenshot of the app’s Redirect URLs list and the time you tried, and we’ll dig in further.