How many tools does the Chartsy MCP server expose?

Eighteen, grouped into revenue, customers and churn, site traffic, and whole-business tools. Two of them are snapshots - one covering the whole business over a shared time window, one covering a single day - so broad questions resolve in a single call rather than a dozen.

Can I scope an MCP question to one account or site?

Yes. With a single connected payment provider every tool reads it automatically. With several, name the account you mean and Claude passes the right one. Site-traffic tools can be scoped to one tracked site the same way.

How long does a Chartsy MCP token last?

An OAuth access token lasts one hour and its refresh token up to 90 days, replaced each time it is used. A personal access token generated under Settings, Claude and MCP lasts one year. Access is re-checked on every call, so revoking one takes effect immediately.

Does Chartsy MCP work with BigCommerce?

No. Chartsy MCP reads live Stripe or Paddle data, so it requires a connected payment provider. There are no order, product or store tools, and a BigCommerce-only account has nothing for it to read. BigCommerce merchants should use ChartsyAI inside Chartsy instead.

Chartsy MCP reference

Q: Do MCP tool calls use up my ChartsyAI questions?

Yes. Each tool call draws from the same monthly question budget as questions asked inside Chartsy, so a long conversation with lots of tool calls uses more of it. Your allowance is set by your plan and shown in Chartsy, and it resets on the 1st.

Chartsy's MCP server lets Claude read your live revenue and site-traffic data, so you can ask about MRR, churn, refunds or traffic sources in the same conversation where you're doing the rest of your work - no exporting, no dashboard hopping.

It is read-only. Claude can look at your numbers; nothing it does can change your Chartsy account, your Stripe or Paddle data, or your customers.

Looking for setup steps?

This page is the reference: every tool, and the limits that apply to all of them. The connection walkthrough - prerequisites, the three ways to connect, a first question to try, and troubleshooting - lives in Connect Chartsy to Claude in 5 minutes.

Server URL: https://mcp.chartsy.app/mcp
Transport: streamable HTTP
Authentication: OAuth (sign in with your Chartsy login) - or a personal token you generate in Chartsy
Support: support@chartsy.app
Privacy policy: chartsy.app/privacy-policy

Connection details

The facts a client needs. For the step-by-step version of each route, see the connection walkthrough.

Requires a Chartsy account on any plan, including the trial, with a connected and synced Stripe or Paddle account. The sample account seeded at signup does not count.
OAuth - the default. Add the server URL as a custom connector and sign in with your Chartsy login. Access tokens last one hour; refresh tokens up to 90 days, replaced on each use.
Personal access token - for clients that cannot run an OAuth flow. Generated under Settings → Claude & MCP, shown once, valid for one year, revocable at any time.

The tools Claude gets

Every tool is read-only and scoped to the accounts your own login owns.

Revenue

Tool	What it returns
`get_mrr`	Current monthly recurring revenue
`get_mrr_by_plan`	MRR and paying customers per plan, per month (up to 36 months)
`get_mrr_by_country`	Current MRR and paying customers per country
`get_revenue_breakdown`	Revenue over a date range, grouped by plan, country or payment method
`get_refund_summary`	Refund totals and refund ratio by plan
`get_goal_progress`	Progress against your revenue and growth goals

Customers and churn

Tool	What it returns
`get_churn_rate`	Churn rate per day, week, month, quarter or year
`get_new_subscribers`	New subscribers per period
`list_at_risk_customers`	Customers with repeated failed payments, and paused subscriptions
`list_top_customers`	Top customers by lifetime revenue
`get_customer_concentration`	Share of MRR coming from your top K customers

Site traffic

Tool	What it returns
`list_tracked_sites`	The sites you track with Chartsy
`get_site_traffic`	Visits, unique visitors and signups per period
`get_traffic_sources`	Traffic by source, medium, campaign, country, referrer or landing page, with signup rates
`get_monthly_events_usage`	This month's tracked events against your plan limit

Everything at once

Tool	What it returns
`get_business_snapshot`	The whole review in one call - MRR, plans, countries, churn, new subscribers, top customers, concentration, refunds, goals, at-risk customers, traffic and sources - plus derived warnings about concentration, churn spikes and refund ratios
`get_daily_snapshot`	A single day in one call - that day's revenue and revenue by plan, new subscribers, cancellations, refunds, visits and traffic sources, each against the previous day and the trailing 7-day average, plus warnings about moves far off that baseline. Defaults to yesterday
`list_accounts`	The Chartsy accounts this login can read

If you have more than one account

Most people don't need to think about this: with one connected payment provider, every tool reads it automatically. If you have several, Claude calls list_accounts and passes the account you name - "what's MRR for the EU account?" is enough.

Data, privacy and limits

Customer identities never leave Chartsy. Tools that return per-customer rows identify customers by payment-processor ID only. No names, no email addresses - look the ID up in Chartsy to see who it is.

Claude only ever sees your own data. Every query is filtered to the accounts and tracked sites your login owns. Connecting doesn't grant access to anyone else's Chartsy data, and a token can't be pointed at an account you don't own.

It's read-only, end to end. There is no tool that writes, updates or deletes anything.

Tool calls count toward your ChartsyAI allowance

Each call draws from the same monthly question budget as questions asked inside Chartsy, so a long conversation with lots of tool calls uses up more of it. Your allowance is set by your plan and shown in Chartsy.

Access is checked on every call, not just when you connect - so revoking a token, an ended trial or a lapsed subscription takes effect immediately.

To disconnect: revoke the token under Settings → Claude & MCP, or remove the connector in Claude.

If something is not working

Every error the server returns - no connected payment provider, an account that needs naming, a spent ChartsyAI allowance, a connector that needs re-authorising, or numbers that disagree with your dashboard - is covered in the walkthrough's troubleshooting section. Anything else: support@chartsy.app.