> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/ai/cursor.md).

# Cursor

Cursor is an AI-powered code editor that lets you interact with data through natural language. By connecting Coupler.io to Cursor, you can load data from any source directly into your AI workspace and ask questions about it — no SQL, no formulas, just conversation.

The integration uses the **Model Context Protocol (MCP)**, which lets Cursor communicate with Coupler.io as a remote data provider. Your data flows become queryable datasets that Cursor's AI can reason over.

## Why use Cursor as a destination?

* **Conversational analytics** — Ask questions like "what's my top-performing campaign this month?" instead of writing queries
* **Any source, one workspace** — Marketing reports, financial metrics, operational data, or any other Coupler.io source all land in the same AI-ready environment
* **No code required** — Analysts and non-technical users can explore complex datasets without leaving Cursor
* **Live data, real insights** — Schedule your data flow to refresh automatically, so Cursor always has up-to-date data to work with

## Prerequisites

* A Cursor account
* The Cursor desktop application installed on your machine

## Quick start

{% hint style="success" %}
Install the Coupler.io MCP connector in Cursor before building your data flow — authentication happens on the Cursor side first, then you select Cursor as the destination in Coupler.io.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Install the Coupler.io MCP connector in Cursor and authenticate.** Visit the [Coupler.io entry in the Cursor MCP directory](https://l.rw.rw/couplerio-cursor-mcp) and click **Add to Cursor**. Once added, find the new integration inside Cursor and click **Needs authentication**. Sign in with your Coupler.io credentials and grant access.
{% endstep %}

{% step %}
**Create a data flow in Coupler.io.** In Coupler.io, create a new data flow and add your data source, such as Google Analytics, HubSpot, Airtable, or others.
{% endstep %}

{% step %}
**Select Cursor as the destination.** In the destination step of your data flow, choose **Cursor** from the list of available destinations.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute the data flow manually. Once it completes successfully, your data is available in Cursor's AI context.
{% endstep %}

{% step %}
**Explore your data in Cursor.** Open the AI Pane in Cursor from the side panel or command palette. Start asking questions about your dataset — for example, "summarize my sales data by region" or "which rows have missing values?"
{% endstep %}
{% endstepper %}

## Supported features

| Feature              | Supported |
| -------------------- | --------- |
| Replace mode         | Yes       |
| Append mode          | No        |
| Automatic scheduling | Yes       |
| Type enforcement     | No        |
| Templates            | No        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/destinations/categories/ai/cursor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.