How to Connect Polar to Cursor

Query your Polar data directly from Cursor using Sequel’s MCP server. Ask questions in plain English, with no SQL, no dashboards, and no context switching.

Short answer

Connect Polar to Sequel, then add Sequel's MCP server to Cursor using the config on this page. Cursor can then query your live Polar data in plain English, with no connector code and no CSV exports. Both steps take a few minutes.

Example prompts

Everything you can ask Cursor about your Polar data.

Ask in plain English — Sequel translates it into a Polar query, runs it, and Cursor hands back the answer. No SQL, no dashboards, no CSV exports.

What you can ask Cursor
  • What's our MRR trend over the last six months?
  • Which cancellation reason drove the most churn last quarter?
  • How much revenue did we make in March, net of refunds?
  • Which subscriptions are past due right now?
  • What's our checkout conversion rate by product?

How it works

Three steps to get started

1

Connect Polar to Sequel

In your Sequel dashboard, go to Connections and add Polar. Sequel handles authentication and schema discovery automatically.

2

Add Sequel to the agent

Copy the Sequel MCP configuration into Cursor's settings file (shown below). Swap in your API key from Settings → API Keys.

3

Ask Cursor about your data

Restart Cursor and start asking questions. "What's our MRR trend over the last six months?" — and get a real answer backed by live Polar data.

Why Cursor

What Cursor does with your Polar data

Schema exploration in your editor

Ask Cursor to describe your database schema, find the right table for a feature, or understand relationships between tables — all without switching to another tool or reading through migrations.

Query data while you code

Need to check actual data while implementing a feature? Ask Cursor to pull examples from your connected databases. No more copy-pasting connection strings into a separate SQL client.

Catch data issues before they ship

Run queries against your staging or production database from inside the editor. Validate assumptions about data shape, volume, or edge cases while the code is still in front of you.

Configuration

Add Sequel to Cursor

Place this in .cursor/mcp.json and replace sql_your_api_key with a key from Settings → API Keys.

.cursor/mcp.json

{
  "mcpServers": {
    "sequel": {
      "url": "https://api.sequel.sh/mcp",
      "headers": {
        "Authorization": "Bearer sql_your_api_key"
      }
    }
  }
}

Install

Install Polar MCP in Cursor

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. Every route signs in with your Sequel account over OAuth, so there is no API key to copy and nothing to keep in sync.

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Add Sequel to Cursor

One click: the button above opens Cursor with Sequel pre-filled, and Cursor signs you in with your Sequel account. There is no key to paste.

Frequently asked questions

How do I connect Polar to Cursor?

You need two things: (1) connect Polar to Sequel in your Sequel dashboard under Connections, and (2) add the Sequel MCP config to Cursor using the setup shown above. Once both are done, Cursor can query your Polar data directly.

What Polar data can Cursor access?

Cursor can access any data available through your Polar connection in Sequel. Use Sequel's search tool to discover available metrics and dimensions, then execute queries to pull the data you need.

Is my Polar data sent to Cursor's servers?

Query results are returned to Cursor as context within your conversation. Only the data you explicitly ask about is retrieved. Sequel never stores your query results permanently — they exist only for the duration of the tool call.

Do I need a Sequel account?

Yes. You need a Sequel account to connect Polar and generate an API key. Sign up free at sequel.sh — no credit card required. Then create a connection to Polar and generate an API key from Settings → API Keys.

Can I connect multiple Polar accounts?

Yes. Sequel supports multiple connections of the same type. If you have multiple Polar accounts or properties, add each as a separate connection in Sequel. Cursor will be able to query all of them.

Does this work with Cursor Agent and Cursor Chat?

Yes. Once the MCP config is in your .cursor/mcp.json, Sequel tools are available in both Cursor Chat and Cursor Agent. The agent can call multiple tools in sequence to answer complex questions.

Should I use a project-level or global MCP config?

Use a project-level .cursor/mcp.json for team repos so all collaborators share the same MCP setup. For personal access, add the config globally at ~/.cursor/mcp.json instead.

Can Cursor modify my database through Sequel?

Sequel's query tools are read-only by default. The workbench tool can run Python code, which could write to files, but it runs in an isolated sandbox without direct database write access.

How do I share the Sequel MCP config with my team?

Commit .cursor/mcp.json to your repo. Each team member needs their own Sequel API key — replace the value of the Authorization header with their personal key from Settings → API Keys.

How do I connect Polar to Sequel?

In Polar, go to Organization Settings → Developers → New Token and create an Organization Access Token with read-only scopes (metrics:read, orders:read, subscriptions:read, customers:read, products:read, payments:read, refunds:read, disputes:read, discounts:read, checkouts:read, events:read, meters:read, customer_meters:read, organizations:read). Paste the token into Sequel's Polar connector and click Test. Leave the environment field blank for production, or enter 'sandbox' to connect a Polar sandbox organization.

Can Sequel change anything in my Polar account?

No. The connector exposes read-only tools only — it cannot create, refund, cancel, or modify any order, subscription, customer, product, or discount. Granting only the :read scopes on your token enforces that at Polar's end too.

Does Sequel recalculate my revenue metrics?

No, and that's the point. Polar computes MRR, ARR, churn, LTV and 50-odd other metrics itself, and Sequel reads those figures directly. You get the same numbers as the Polar dashboard, already net of refunds and proration, rather than an approximation reconstructed from a list of orders.

Can I ask about payouts or my Polar balance?

Not currently. Polar's public API has no payouts or balance endpoints, so those figures aren't reachable by any integration, including Sequel. Revenue questions work fine — just note that revenue is not the same as what lands in your bank account, since it's before Polar's fees and payout timing.

Connect Polar to Cursor today

Sign up free, connect your data sources, and start querying in minutes.