How to Connect Dodo Payments to Claude Code Using Sequel

Dodo Payments is a merchant of record for digital products: it sells one-time products and subscriptions, collects tax, and pays you out. Claude Code is Anthropic's AI coding CLI that runs in your terminal. Sequel's MCP server connects the two, so you can answer revenue questions from the same place you ship the product.

This guide covers the full setup in three steps.

What You'll Accomplish

By the end of this guide, you'll be able to run Claude Code and ask questions like:

• "What was our revenue last month, by currency, and how much of it was refunded?"
• "Which subscriptions are on hold because a renewal failed, and what was the error code?"
• "How much has Dodo paid out this year, and what did the fees come to?"

Claude Code calls Sequel's MCP server, which queries the Dodo Payments API and returns the results inline.

Prerequisites

• A Sequel account: Sign up free at sequel.sh
• A Dodo Payments business in live or test mode
• Permission to create an API key under Developer in the Dodo dashboard
• Claude Code installed: run npm install -g @anthropic-ai/claude-code if you haven't already

Step 1: Connect Dodo Payments to Sequel

Sign in to sequel.sh and click Data Sources in the left sidebar.

Click New Connection, then select Dodo Payments from the connector list.

Now create the key in Dodo. Go to Developer → API Keys → Add API Key, give it a name, and leave Enable write access unchecked. Copy the key; Dodo shows it once.

Back in Sequel, fill in two fields:

• API key: the key you just copied
• Environment: live for real data, test if the key came from test mode

Click Connect. Sequel verifies the key against Dodo and names the connection after your brand.

Tip: keep write access off. The connector has no write tools, so a read-only key means an agent cannot refund, cancel, or create anything even by accident.

Step 2: Add Sequel to Claude Code

In your terminal:

claude mcp add sequel \
  --transport http \
  https://api.sequel.sh/mcp

Claude Code opens a browser so you can authorize Sequel. Once approved, the server persists across sessions. Add --scope user to install it globally rather than per project.

Verify it registered:

claude mcp list

sequel should appear in the list of configured MCP servers.

Step 3: Query Your Dodo Payments Data

Start a Claude Code session and try these:

What was our revenue last month by currency, and how much of it was refunded?

Which subscriptions are on hold or set to cancel at the next billing date, and who are the customers?

List payouts this year with the fee, refunds and chargebacks netted from each.

Claude Code calls the Sequel MCP server, which hits the relevant Dodo endpoint and returns the results in your terminal. Amounts come back in the currency's smallest unit, and the agent divides before reporting.

What You Can Do Now

• Revenue checks without a dashboard: ask "What did we bill this week compared to last week?" mid-session.
• Involuntary churn: ask "Which failed payments this month were card declines rather than customers leaving?" The error code on each payment answers it.
• Refund and dispute rates: ask "Which products have the highest refund rate relative to successful payments?"
• Reconciliation: ask "Walk me through the balance ledger for the last payout: payments, fees, refunds and adjustments."
• Cross-source analysis: with Search Console and GA4 also connected, ask "Which organic landing pages brought in the customers who paid in Dodo last quarter?"

That last question spans billing and search data, which is exactly the shape Dodo cannot answer alone. Sequel's revenue playbooks already know how to run it. For more on why cross-source questions justify this setup, see the connector is the easy part and MCP for databases.