Chartsy is a hosted, read-only MCP server that gives a NanoClaw agent group your MRR, churn, refunds and site traffic from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius. The token sits in OneCLI's Agent Vault and is added to requests on the way out, so the agent never holds it. Last updated October 2026.
@Andy how did we do last week?
A good week, with one thing to watch.
NanoClaw agents run unattended in containers, so they use a personal token instead of a browser sign-in. The token goes into the vault; the group only gets the server URL.
mcp.chartsy.app that sends it as Authorization: Beareronecli secrets create \
--name Chartsy \
--type generic \
--value "<your-chartsy-token>" \
--host-pattern mcp.chartsy.app \
--header-name Authorization \
--value-format 'Bearer {value}'Don't put the token in --headers on the MCP server: anything there is visible to the group's container.
onecli agents secretsset-secrets replaces itonecli agents secrets --id <agent-id> onecli agents set-secrets --id <agent-id> \ --secret-ids <existing-ids>,<chartsy-secret-id>
The agent id is the OneCLI agent whose identifier matches the group. No restart needed: the vault applies secrets on the next request.
ncl groups list ncl groups config add-mcp-server --id <group-id> \ --name chartsy --url https://mcp.chartsy.app/mcp ncl groups restart --id <group-id>
@Andy what happened yesterday?
A quiet Sunday, nothing urgent.
Want a scheduled brief in your chat apps instead? See Chartsy + OpenClaw or Chartsy + Hermes Agent.
NanoClaw keeps credentials out of the container. Chartsy fits that model.
| Surface | How | Token visible to the agent? | Best for |
|---|---|---|---|
OneCLI vaultThis page | onecli secrets create for mcp.chartsy.app | No, added on the way out | Every NanoClaw group that should read your numbers |
--headers on the server | add-mcp-server --headers | Yes, it sits in the group config | Quick local tests only; avoid on a shared host |
Another agent | Sign-in instead of a token · OpenClaw, Claude | No token at all | When you'd rather not run your own containers |
Mention the agent in the group, or schedule a task. It picks the tools, so the calls can vary.
@Andy how did we do last week?
A good week, with one thing to watch.
Sample figures for a made-up business.
Which channels brought paying customers last month?
Two channels did the work.
Sample figures for a made-up business.
Which customers have failed payments this quarter?
3 customers with 2 or more failed payments.
Chartsy shares IDs, never names or emails.
Which plan grew the most this quarter?
Annual Pro grew fastest.
Sample figures for a made-up business.
Are refunds higher than usual this month?
Slightly.
Sample figures for a made-up business.
More in the MCP prompt library.
Signups only tell you half the story. NanoClaw 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, available to the one group you add Chartsy to.
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 the group. The token, names, emails and write access don't.
NanoClaw 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. NanoClaw 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 vault grant or a group that hasn't restarted.
The vault isn't adding the token. Check the secret's host pattern is mcp.chartsy.app, its header is Authorization with the value format "Bearer {value}", and that it's granted to the group's agent with onecli agents set-secrets. If the token was revoked or expired, generate a new one and update the secret.
onecli agents set-secrets replaces the agent's whole secret list. List the secrets you had, then set them again together with the Chartsy secret.
Server changes only apply when the group restarts. Run ncl groups restart --id <group-id>, and check you added the server to the group you're talking to.
Group agents run without a browser, so a sign-in can't finish. Use a personal token in the vault 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.
Short answers for people running their own NanoClaw.
Generate a personal token in Chartsy → Settings → Claude & MCP, store it in the OneCLI vault for mcp.chartsy.app as an Authorization: Bearer header, grant it to the group's agent, then run ncl groups config add-mcp-server --id <group-id> --name chartsy --url https://mcp.chartsy.app/mcp and restart the group.
The OneCLI gateway adds the token to requests as they leave, so the agent in the container never sees it. If the container is compromised, your Chartsy token isn't in it.
No. Only groups you add the server to, and whose agent holds the Chartsy secret, can read your numbers. Add it group by group.
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.
NanoClaw reads 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. NanoClaw can't change Chartsy, your payment provider's data, or your customers.
One per tool call, failed calls included. A broad question like "how did we do last week?" is usually one call. A scheduled daily check is about 30 questions a month.
Remove the chartsy server from the group's config and restart the group, and remove the secret from the vault. 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, store a token in the vault, and add the server to a group.
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.