# Common Issues

## Connection issues

<details>

<summary>"Needs authentication" never resolves after signing in</summary>

This usually means the OAuth handshake between Cursor and Coupler.io didn't complete. Try removing the Coupler.io MCP entry from Cursor, reloading the app, and re-adding Coupler.io MCP from the MCP directory. Make sure you're signing in with the correct Coupler.io account and that pop-ups or redirects are not being blocked by your browser.

</details>

<details>

<summary>MCP connector shows as installed but Cursor has no access to data</summary>

The MCP connector being installed does not automatically load data — you still need to create and successfully run a data flow in Coupler.io with Cursor selected as the destination. Check that your data flow has completed at least one successful run before querying in Cursor.

</details>

## Data issues

<details>

<summary>Cursor's AI gives incomplete or inaccurate answers about my data</summary>

The quality of answers depends on the structure of the data coming from Coupler.io. Make sure column names are descriptive (e.g., `revenue_usd` rather than `col_3`) and that your data flow applies any necessary transformations — like aggregations or joins — before it reaches Cursor. Cleaner, well-labeled data produces better conversational results.

Also, make sure you are using the right prompt. Vague and abstract prompts result in poor answers.

</details>

<details>

<summary>Data in Cursor appears outdated</summary>

Cursor shows the data from the most recent successful run of your data flow. If the data looks stale, go back to Coupler.io and trigger a manual run to refresh it. Once you've confirmed the data flow works correctly, you can set up a schedule so Cursor always has current data.

Make sure to start a new chat to fetch fresh data or ask Cursor to get it directly if you want to continue the ongoing conversation.

</details>

## Permission errors

<details>

<summary>"Access denied" when Cursor tries to call the Coupler.io MCP</summary>

This error typically appears when the authentication token has expired or been revoked. Re-authenticate by clicking **Needs authentication** on the Coupler.io MCP entry in Cursor. If the issue persists, remove and re-add the integration from the Cursor MCP directory.

{% hint style="danger" %}
Do not share your Coupler.io credentials with Cursor's AI chat directly — authentication should only happen through the official MCP connector flow.
{% endhint %}

</details>