Chartsy is a hosted, read-only MCP server that gives Paperclip agents your MRR, churn, refunds, site traffic and revenue by channel from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius. Add it once as a Paperclip connector, or to the runtime your agents use, such as Claude Code or Codex. Last updated October 2026.
Every Monday, report MRR, churn and the channels that brought paying customers.
Weekly report filed for the CEO agent.
Paperclip agents work unattended, so they use a personal token rather than a sign-in that someone has to click.
https://mcp.chartsy.app/mcp
Rather connect the runtime your agents use? Add Chartsy there with a token instead: Claude Code, Codex, OpenClaw or Hermes Agent.
Put the report on a routine so it runs on schedule, or assign it as a one-off issue.
Every Monday, report MRR, churn and the channels that brought paying customers.
Weekly report filed.
How the weekly report works with other agents: the daily business brief.
Both give your agents the same numbers. Pick the one you'll manage more easily.
| Surface | Set up in | Who can use it | Best for |
|---|---|---|---|
Paperclip connectorThis page | Connectors → Connect your own MCP server | The agents you pick, with per-action controls | Most teams: one place to grant and revoke |
The runtime | Claude Code, Codex, OpenClaw or Hermes MCP config, with a token | Every agent on that runtime | Agents that already share one runtime config |
Growth loop skill | Skills → import from GitHub | Agents you assign it to | A marketing agent that plans next week's posts |
Give them goals, not just questions. Each agent picks its own tools, so the calls can vary.
Every Monday, report MRR, churn and the channels that brought paying customers.
Weekly report filed for the CEO agent.
Two calls a week: about 9 ChartsyAI questions a month.
Which channels brought paying customers last month, and which brought none?
Recommend moving spend from paid social to search content.
Sample figures for a made-up business.
Flag me if churn rises above its 3-month average.
Checked: no flag this week.
Sample figures for a made-up business.
Which customers are at risk this quarter?
5 customers with 2 or more failed payments.
Chartsy shares IDs, never names or emails.
Are we on track for this quarter's MRR goal?
Behind, but close.
Sample figures for a made-up business.
More in the MCP prompt library.
Signups only tell you half the story. Paperclip 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 Chartsy growth-loop skill teaches Paperclip a weekly routine: check which channels and posts brought paying customers, recommend where to focus, and draft next week's posts with tracked links for you to review. Connect Postiz or Publer too and the drafts are saved there, never published. Chartsy stays read-only.
sprifti/chartsy-agent from GitHubSkills live at the company level in Paperclip, so any agent in the company can be assigned it.
View the skillsprifti/chartsy-agent
> Plan next week's posts based on what brought paying customers. get_revenue_by_source · by=campaign Comparison posts brought 5 of 9 new paying customers. Three drafts below, each with a UTM link so next week is measurable. # Sample answer for a made-up business
The same numbers as your Chartsy dashboard. Set any action to Ask first or Off in the connector if an agent doesn't need it.
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 agents. Names, emails and write access never do.
Paperclip 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. Paperclip 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 token or which agents the connector is shared with.
The token isn't reaching Chartsy in the right form. Chartsy expects the header Authorization: Bearer <your-token>. If the API key field doesn't add "Bearer", set a custom header with that exact value. If the token was revoked or expired, generate a new one.
The connector is only available to the agents you picked. Open the Chartsy connector and add that agent, and check the actions it needs aren't set to Off.
Agents that run unattended can't click a sign-in page. Use a personal token instead, as in step 1.
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. Several agents on frequent heartbeats add up fast. When the allowance is used up, calls stop until it resets on the 1st, or until you upgrade your Chartsy plan.
Short answers for people running an agent company on Paperclip.
Generate a personal token in Chartsy → Settings → Claude & MCP. In Paperclip, open Connectors → Connect your own MCP server, paste https://mcp.chartsy.app/mcp, paste the token when asked for an API key, and choose which agents may use it.
Either. Paperclip's custom connector shares Chartsy with the agents you pick. Or you can add Chartsy to the runtime your agents run on, such as Claude Code, Codex, OpenClaw or Hermes, with a token in that runtime's MCP config.
Paperclip agents wake on heartbeats and routines with nobody watching, so a sign-in page can't be clicked. A personal token lasts a year and you can revoke it any time.
One per tool call, failed calls included. A weekly report is usually two calls, about 9 questions a month. Agents with frequent heartbeats use more, so give Chartsy only to the agents that need it.
Connecting costs nothing extra. It works on any Chartsy plan, including the free trial, and each tool call uses one ChartsyAI question from your plan's monthly allowance.
Paperclip agents 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. Your agents can't change Chartsy, your payment provider's data, or your customers.
Remove the Chartsy connector in Paperclip, or take an agent off it. To cut access everywhere at once, revoke the token in Chartsy under Settings → Claude & MCP.
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 connector to Paperclip, and give an agent its first weekly report.
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.