Ask Claude about your MRR: connecting Chartsy to Claude in 5 minutes
You know the feeling. You're in the middle of writing something - a board update, an investor email, a plan for next quarter - and you need a number. So you open the dashboard, find the right chart, change the date range, squint at it, go back to what you were writing, and realise you now need a second number.
Chartsy's Claude connector removes that round trip. You ask Claude in plain language, and it reads your live Chartsy data to answer:
You: What happened in my business yesterday?
Claude: Revenue was $759 - about 19x your 7-day average of $38, driven by four Scale renewals landing on the same day. One subscription was cancelled (5.3% of the customers who were active that morning). No refunds. 312 visits, up 11% on the week.
Setup takes about five minutes, and it's read-only - Claude can look at your numbers, but nothing it does can change your Chartsy account, your Stripe or Paddle data, or your customers.
What you need first
- A Chartsy account. Any plan, including the free trial.
- A connected payment provider. The connector reads your live Stripe or Paddle data, so one needs to be connected and synced first. The sample account Chartsy seeds at signup doesn't count - it's the same demo data for everyone, and answering questions about it wouldn't tell you anything.
That's it. There's no API key to manage, no client ID or secret to copy between tabs.
Step 1: Connect
Pick whichever of these matches how you use Claude.
From Claude on the web or desktop
- Open Settings → Connectors → Add custom connector.
- Paste the server URL:
https://mcp.chartsy.app/mcp- Claude sends you to Chartsy to sign in. Approve the request.
- You're back in Claude, connected.
If you're already signed in to Chartsy in that browser, the approval is one click.
From Claude Code
One command, then authenticate:
claude mcp add --transport http -s user chartsy https://mcp.chartsy.app/mcpType /mcp in Claude Code to sign in and confirm the connection is live.
From another MCP client
Some clients can't run an OAuth flow. For those, generate a personal token instead:
- In Chartsy, go to Settings → Claude & MCP.
- Click Generate token. It's shown once - copy it before you leave the page.
- Chartsy prints the exact command to run, in this shape:
claude mcp add --transport http -s user chartsy https://mcp.chartsy.app/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Tokens last a year. That same tab lists every token you've issued, when it was created and when it expires, and lets you revoke any of them instantly.
Step 2: Ask something
Start broad. The connector is built so that "how is the business doing?" is a cheap question - Chartsy answers it with one call that returns the whole picture, rather than Claude making twenty small requests and stitching them together.
Good first questions:
- "What happened in my business yesterday?"
- "Give me a full business review - where's the risk?"
- "What's my MRR right now, and how has it moved by plan over the last 6 months?"
- "Which customers are at risk of churning, and how much MRR do my top 10 represent?"
- "Which traffic source converted best last month?"
- "What did we refund in Q1, and which plan is worst for refund ratio?"
Two of those deserve a closer look, because they're the ones people keep coming back to.
"What happened yesterday?"
This is a daily standup for your business. You get the day's revenue and how it split by plan, new subscribers, cancellations and churn rate, refunds, and site visits with the sources behind them.
The part that makes it useful is the context: every figure comes with the previous day's number and the trailing 7-day average. A day is never reported as a bare number you then have to interpret. Chartsy also flags the things worth knowing without being asked - revenue or traffic far off the baseline, cancellations, refunds larger than the day's takings, or simply "nothing happened yesterday", which for a business that bills weekly is the correct and reassuring answer.
It works for any day, not just yesterday
Ask it about whichever day you mean - "was Monday unusual?" works.
"Where's the risk?"
The business-review question returns MRR by plan and country, churn and new subscribers month by month, top customers, revenue concentration, refunds, goals, at-risk customers and traffic - over one shared window, so nothing is comparing different periods by accident.
On top of the raw numbers, Chartsy derives warnings: revenue concentrated in too few customers, months that churned above 20%, plans refunding an unusual share of revenue, paused subscriptions old enough that they're not really at risk any more, just stale.
What Claude can actually see
Every tool is read-only and scoped to what your own login owns.
Revenue - current MRR; MRR by plan and by country; revenue over any date range grouped by plan, country or payment method; refund totals and refund ratio by plan; progress against your goals.
Customers and churn - churn rate by day, week, month, quarter or year; new subscribers per period; customers with repeated failed payments; paused subscriptions; how much of your MRR sits with your largest customers.
Site traffic - visits, unique visitors and signups per day or month; traffic by source, medium, campaign, country, referrer or landing page, with signup rates. This half needs Chartsy's tracking script on your site; add it from the Domains tab in settings. Everything else works as soon as you connect.
Everything at once - the full business review, or a single day, in one call.
Want the exact list?
That's the summary. Every tool, what each one returns, and the limits that apply to all of them are set out in the Chartsy MCP reference.
If you have more than one account
Most people never think about this. With one connected payment provider, every question reads it automatically. With several, just name the one you mean - "what's MRR for the EU account?" is enough.
What Claude can't see
Worth being precise about, because you're pointing an AI client at your revenue data.
Customer names and email addresses never leave Chartsy. Questions that return per-customer rows identify people by payment-processor ID only. If you want to know who cus_QXm2... is, you look it up in Chartsy. This is deliberate and it isn't configurable.
Only your own data. Every query is filtered to the accounts and tracked sites your login owns. Connecting grants no access to anyone else's Chartsy data, and a token can't be pointed at an account you don't own.
Read-only, end to end. There is no tool that writes, updates or deletes anything.
Access is checked on every call, not just when you connect. Revoking a token, an ended trial or a lapsed subscription takes effect immediately.
Two practical notes
Tool calls draw from the same monthly ChartsyAI question allowance as questions asked inside Chartsy, so a long conversation with many calls uses more of it. And to disconnect, either revoke the token under Settings → Claude & MCP, or remove the connector in Claude.
Troubleshooting
"This Chartsy login has no connected payment provider yet."
Connect Stripe or Paddle and let the first sync finish. The demo account seeded at signup doesn't count.
"This Chartsy login has N accounts, so account_id is required."
Tell Claude which account you mean by name - it'll pass the right one.
"You've used all N ChartsyAI questions included in your plan this month."
Your monthly allowance is spent. It resets on the 1st, or you can upgrade.
Claude says the connector needs re-authorising.
Sign in again from Claude's connector settings. If you're using a generated token, check the Claude & MCP tab to see whether it expired or was revoked, and generate a new one.
The numbers don't match my dashboard.
They're the same queries behind both. Nine times out of ten it's a different account or date range - ask Claude to say which account and period it read, and the mismatch usually explains itself.
Anything else: support@chartsy.app.
Try it
If you already use Chartsy, connecting takes one paste of a URL:
https://mcp.chartsy.app/mcpThen ask it what happened yesterday.
