
Chartsy
app.chartsyPublished by chartsy.appOfficial publisherv1.0.0Updated Oct 31, 2026
Read-only revenue analytics from Stripe, Paddle, Polar, Lemon Squeezy, Creem and Freemius.
Overview
Read-only revenue analytics MCP server that lets an assistant query live MRR, churn, refunds, customers and site traffic from connected payment providers.
- What you can do
- Get whole-business or daily snapshots and briefings on what changed and why
- Query revenue: MRR overall, by plan and by country, revenue breakdown, refunds and goal progress
- Inspect customers and churn: churn rate, new subscribers, at-risk and top customers, concentration
- Review site traffic: tracked sites, traffic volume, traffic sources and monthly event usage
- Attribute marketing to revenue by source and list connected accounts
- When to use it
- Useful when you want an assistant to answer questions about a SaaS business's revenue, churn, refunds or acquisition performance from live data, for example a weekly business review or deciding which channels to invest in.
- Requirements
- A remote streamable HTTP endpoint with OAuth sign-in; no local install. A Chartsy account on any plan, including the free trial, with a payment provider connected and synced. Unattended agents need a personal token generated in Chartsy, sent as an Authorization Bearer header, since OAuth requires a browser approval.
Installation
In SourceWeft
- Open Chartsy in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.chartsy%2Fchartsy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"chartsy": {
"type": "http",
"url": "https://mcp.chartsy.app/mcp"
}
}
}README
Chartsy for AI agents
Ask your AI agent about your SaaS business: MRR, churn, revenue, refunds, at-risk customers, goals, site traffic and signups. The numbers are live from Chartsy, which reads Stripe, Paddle, Polar, Lemon Squeezy, Creem, Freemius or a custom source.
This repo bundles what every agent install points at:
- The hosted Chartsy MCP server:
https://mcp.chartsy.app/mcp. It uses streamable HTTP and OAuth sign-in, and it's read-only. Nothing to install or run locally. - The
chartsyskill (skills/chartsy/SKILL.md). It teaches the agent which tool answers which question, how to keep tool calls to a minimum, and how to read the numbers correctly. - The
chartsy-growth-loopskill (skills/chartsy-growth-loop/SKILL.md). It guides your agent through a weekly loop: find which channels, campaigns and posts brought paying customers who stayed, recommend where to focus, and write next week's posts with UTM-tagged links. If you also connect a publishing tool's MCP (e.g. Postiz or Publer) to the same agent, the skill tells it to save the posts there as drafts for your review. Chartsy itself is read-only and never posts anything.
Usage: every tool call counts as one ChartsyAI question against your plan's monthly allowance, the same budget as questions asked inside Chartsy. The skill steers agents to one-call answers (
get_business_snapshot,get_daily_snapshot) wherever possible.
You need: a Chartsy account (any plan, including the free trial) with a payment provider connected and synced.
Install
Claude (claude.ai, desktop, mobile)
Settings → Connectors → Add custom connector, then paste https://mcp.chartsy.app/mcp
and sign in to Chartsy.
Claude Code
Plugin (MCP server and skill):
Or just the server:
Then run /mcp to sign in.
Cursor
Add to Cursor.
Or go to Settings → MCP → Add server, choose type HTTP, and use URL
https://mcp.chartsy.app/mcp.
ChatGPT
Settings → Connectors (Developer mode) → add https://mcp.chartsy.app/mcp and sign
in to Chartsy.
Gemini CLI
Then start gemini in a folder you trust (Gemini turns off MCP servers in untrusted
folders), run /mcp auth chartsy to sign in, and check /mcp shows it connected. The
extension brings the server and the skill. npx skills add alone installs only the skill.
Codex, OpenClaw and other skill-aware agents
The skill needs the MCP server connected in the same agent. Add
https://mcp.chartsy.app/mcp in that agent's MCP settings.
Any other MCP client
Use mcp.json, or point the client at https://mcp.chartsy.app/mcp
(streamable HTTP, OAuth sign-in).
Clients that only run local (stdio) servers
Older clients can't connect to a hosted server directly. Bridge to it with
mcp-remote, which handles the OAuth
sign-in in your browser:
Agents that run without a browser (servers, cron jobs, CI)
OAuth needs someone to click Approve in a browser. For an agent running unattended, such as OpenClaw on a VPS, a scheduled job or a CI pipeline, use a personal token instead:
- In Chartsy, go to Settings → AI & Integrations → Generate token. It's shown once, so copy it then.
- Store it as a secret (e.g.
CHARTSY_MCP_TOKEN). Never commit it. - Send it on every request:
For example with Claude Code:
Or through
mcp-remote:npx -y mcp-remote https://mcp.chartsy.app/mcp --header "Authorization: Bearer ${CHARTSY_MCP_TOKEN}"
Tokens last a year and can be revoked on the same tab. An unattended agent uses up ChartsyAI
questions like any other client, one per tool call, so schedule it sensibly. A daily
get_daily_snapshot is one question a day.
Things to ask
- "Give me a full business review. Where's the risk?"
- "What happened in my business yesterday?"
- "How has MRR moved by plan over the last 6 months?"
- "Which customers are at risk of churning?"
- "Which traffic source converts best to signups?"
- "Plan next week's X posts based on which channels brought paying customers last month."
- "What did we refund in Q1, and which plan has the worst refund ratio?"
Tools
All 21 tools are read-only and scoped to the accounts and sites your login owns.
Privacy
Customers are identified by payment-processor ID only. Names and emails never leave Chartsy. Access is checked on every call, so revoking a token or ending a subscription takes effect immediately. Policy: https://chartsy.app/privacy-policy
Repo layout
Keep version in step across .claude-plugin/, .cursor-plugin/ and
gemini-extension.json when you release.
Support: [email protected]
License
Copyright © 2026 Chartsy. All rights reserved. See LICENSE. You may install these files to connect your own agent to Chartsy; no other rights are granted.
Source: README.md at commit da9fcdb
Tools
0Version history
1- v1.0.0LatestOct 17, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.