Chartsy is a hosted, read-only MCP server that lets Zaps run Chartsy tools for your MRR, churn and refunds from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius, plus site traffic and revenue by marketing channel. You connect it through Zapier's MCP Client app, currently in beta, with a personal token. Last updated October 2026.
Run Tool: get_daily_snapshot
Posted to Slack by the next step:
Zaps run on their own, so Zapier connects with a personal token rather than a sign-in.
https://mcp.chartsy.app/mcp
With OAuth set to Yes, Zapier ignores the Bearer Token field, so leave it on No.
Need a model to write the summary? See Chartsy + n8n or Chartsy + Make, whose MCP steps can let AI pick the tools.
The MCP Client app gives you three ways to use the same connection. Every Chartsy tool is read-only, so both run steps work.
| Surface | What it does | ChartsyAI questions | Best for |
|---|---|---|---|
Run ToolThis page | An action that runs the Chartsy tool you pick | Exactly 1 per run | Scheduled reports and Slack posts |
Run Read-Only Tool | A search step for read-only tools | Exactly 1 per run | Looking up a number mid-Zap, e.g. current MRR |
New Tool Result | A trigger that fires when a tool returns a new result | Depends on how often Zapier checks | Use sparingly; a schedule is easier to budget |
Each card is one Run Tool step and what the next step does with it.
Run Tool: get_daily_snapshot
Posted to #numbers:
Weekdays only: about 22 ChartsyAI questions a month.
Run Tool: get_revenue_by_source for last week, by source
Rows added to Google Sheets:
One run a week: about 4 ChartsyAI questions a month.
Run Tool: get_mrr
Row added to the MRR sheet:
Daily: about 30 ChartsyAI questions a month.
Run Tool: list_at_risk_customers
2 tasks created in your CRM:
IDs only: names and emails stay in Chartsy.
Run Tool: get_goal_progress
Sent by Gmail every Friday:
Sample figures for a made-up business.
Tool arguments are listed in the MCP server reference.
One Run Tool step with get_revenue_by_source, a Formatter step for the dates, and a sheet. Over a month you can see which channels keep bringing customers who pay.
by to campaign or content to compare UTM campaigns or posts1. Schedule by Zapier Every week, Monday at 8:00 2. Formatter by Zapier: Date / Time Add/Subtract Time: -7 days To format: YYYY-MM-DD 3. MCP Client: Run Tool Tool: get_revenue_by_source start_date: (step 2 output) end_date: (yesterday, same way) by: source 4. Google Sheets: Create Spreadsheet Row Week · Source · Paying customers · MRR
Signups only tell you half the story. Zapier can now follow each channel into your billing data, so you see which ones bring customers who pay and stay.
Needs the Chartsy tracking script on your site and a connected payment provider. Groups under 5 paying customers are flagged as inconclusive, and retention needs about 90 days to mean much.
Which channels brought paying customers last quarter, and what are they worth now?
Search brings the most money; the newsletter converts best.
The same numbers as your Chartsy dashboard. Pick one per Run Tool step.
get_mrrget_mrr_by_planget_mrr_by_countryget_revenue_breakdownget_refund_summaryget_goal_progressget_churn_rateget_new_subscriberslist_at_risk_customerslist_top_customersget_customer_concentrationlist_tracked_sitesget_site_trafficget_traffic_sourcesget_monthly_events_usageget_revenue_by_sourceget_business_snapshotget_daily_snapshotlist_accountsNumbers and customer IDs reach your Zap. Names, emails and write access never do.
Zapier can read your numbers. It can't change Chartsy, your payment provider's data, or your customers.
Customers are payment-processor IDs; names and emails stay in Chartsy. Zapier sees only the accounts and sites your login owns, checked on every call.
Each call uses one ChartsyAI question from your monthly allowance, failed calls included. Broad questions usually take one call.
Most problems are the OAuth setting, the token or the transport.
Check the Server URL is exactly https://mcp.chartsy.app/mcp, Transport is Streamable HTTP and OAuth is No. If it still fails with a valid token, contact Zapier support: MCP Client is in beta, and some token connections fail on Zapier's side before reaching the server.
The Bearer Token is missing, wrong, revoked or expired, or OAuth is set to Yes, which makes Zapier ignore the token. Generate a new token in Chartsy → Settings → Claude & MCP and reconnect.
Dates must be YYYY-MM-DD. Use a Formatter by Zapier Date / Time step to produce them.
Connect Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius in Chartsy and let the first sync finish. The demo data added at signup doesn't count.
Each tool call uses one ChartsyAI question, failed calls included. When the monthly allowance is used up, calls stop until it resets on the 1st, or until you upgrade your Chartsy plan. Zaps that run every few minutes use it up fast.
Short answers for people building Zaps.
Generate a personal token in Chartsy → Settings → Claude & MCP. In Zapier, open Apps → + Add connection → MCP Client, enter https://mcp.chartsy.app/mcp as the Server URL, choose Streamable HTTP, set OAuth to No and paste the token into Bearer Token.
Not a dedicated one. Chartsy works through Zapier's own MCP Client app, which is in beta and can call any remote MCP server. You get every Chartsy tool as a Run Tool step.
No. Run Tool calls one Chartsy tool and hands its result to the next step, with no model involved. If you want a written summary, add an AI step after it, or use Make or n8n, whose MCP steps can let a model pick the tools.
One per Run Tool step that runs, failed calls included. A weekday Slack post is about 22 questions a month; a weekly sheet is about 4. Zaps that run every few minutes use the allowance fast, so schedule sensibly.
Connecting costs nothing extra on the Chartsy side. It works on any Chartsy plan, including the free trial, and each tool call uses one ChartsyAI question. Zapier's tasks are billed by Zapier.
Zaps read whatever you have connected to Chartsy: Stripe, Paddle, Polar, Lemon Squeezy, Creem, Freemius or a custom source through the Chartsy API.
No. All 19 Chartsy tools are read-only. A Zap can't change Chartsy, your payment provider's data, or your customers.
Remove the MCP Client connection under Apps in Zapier. To cut access everywhere, revoke the token in Chartsy under Settings → Claude & MCP; it stops working on the next call.
Yes. The get_revenue_by_source tool follows the people who signed up from each source, medium, UTM campaign or post into your billing data, and returns how many became paying customers, what they're worth in MRR today, how many churned and the retention rate. You can choose first touch (where they first found you) or last touch (what made them sign up). It needs the Chartsy tracking script on your site and a connected payment provider. Groups with fewer than 5 paying customers are flagged as too small to call.
Same server, same numbers. Or see all AI agents and the MCP server reference.
Connect your payment provider to Chartsy, add the MCP Client connection, and post yesterday's numbers tomorrow morning.
Product names are trademarks of their owners, used only to say what Chartsy works with. Chartsy isn't affiliated with or endorsed by them.
Ministry of Economy and Innovation
Startup AlbaniaThe Chartsy program is realized with the financial support of the Albanian Government through the Ministry of Economy and Innovation, under the Grant 2026 scheme, and is implemented by the Innovation4Albania Agency.