How to Connect Polar to Codex

How do I connect Polar to Codex?

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

What Polar data can Codex access?

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

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

How do I configure Sequel for Codex CLI?

Add the Sequel MCP server to ~/.codex/config.yaml as shown above. Create the file if it doesn't exist. Replace `sql_your_api_key` with a real key from Settings → API Keys, then restart Codex.

Does Codex CLI support HTTP MCP servers?

Yes. Codex CLI supports MCP over HTTP (Streamable HTTP transport). The `type: http` field in the config tells Codex to use this transport when connecting to Sequel.

Can I limit which databases Codex can access?

Sequel MCP is scoped to your organization's connected data sources. You can create separate API keys for different environments and revoke them at any time from Settings → API Keys.

Is this the same as the original OpenAI Codex model?

No — Codex CLI is OpenAI's agentic terminal coding tool, separate from the original Codex language model. It uses the latest OpenAI models (GPT-4o and o-series) with MCP tool support.

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.