How to Connect Polar to VS Code

Query your Polar data directly from VS Code 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 VS Code using the config on this page. VS Code 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 VS Code about your Polar data.

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

What you can ask VS Code
  • 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 VS Code's settings file (shown below). Swap in your API key from Settings → API Keys.

3

Ask VS Code about your data

Restart VS Code 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 VS Code

What VS Code does with your Polar data

Database access in Copilot Chat

Once configured, GitHub Copilot Chat can call Sequel tools to answer questions about your data. Ask about your schema, query examples, or check metrics — right in the Chat panel.

Team-wide setup with one commit

Commit .vscode/mcp.json to your repo and every developer on the team gets Sequel MCP configured automatically. Each team member provides their own API key.

Schema-aware code generation

Copilot can pull your actual database schema through Sequel and use it to generate more accurate SQL queries, migration files, and ORM models — based on what's really in your database.

Configuration

Add Sequel to VS Code

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

.vscode/mcp.json

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

Install

Install Polar MCP in VS Code

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 VS Code

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

Frequently asked questions

How do I connect Polar to VS Code?

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

What Polar data can VS Code access?

VS Code 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 VS Code's servers?

Query results are returned to VS Code 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. VS Code will be able to query all of them.

Does this work with GitHub Copilot in VS Code?

Yes. VS Code's MCP support is available in GitHub Copilot Chat (VS Code 1.99+). Create .vscode/mcp.json in your project root with the config above, and Sequel tools will appear in Copilot Chat.

Do I need the GitHub Copilot subscription?

VS Code MCP requires GitHub Copilot Chat (Individual, Business, or Enterprise plan). The MCP configuration itself is free; you only need a Sequel API key and a Copilot subscription.

Can I configure this globally instead of per-project?

Yes. Add the server configuration to your VS Code user settings.json under the `mcp.servers` key for global access across all projects.

Is the .vscode/mcp.json file safe to commit?

The config file is safe to commit — but never commit your actual API key in it. Use an environment variable reference or instruct team members to replace the placeholder with their own key.

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 VS Code today

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