Chartsy is a hosted, read-only MCP server that gives OpenAI Codex your MRR, churn, refunds and site traffic from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius. One command adds it; the same config works in the Codex CLI, the IDE extension and the ChatGPT desktop app. Last updated October 2026.
Before I ship this pricing change, show MRR by plan.
Current MRR by plan:
One command and a sign-in. Nothing to install or run: the server is hosted.
codex mcp login chartsy)/mcp to check chartsy is connectedcodex mcp add chartsy --url https://mcp.chartsy.app/mcp
Prefer config files? Add [mcp_servers.chartsy] with url = "https://mcp.chartsy.app/mcp" to ~/.codex/config.toml.
Codex uses the Chartsy tools when your question needs real numbers.
Which countries should I localize for first?
Germany first, then Brazil.
Add the Chartsy skill too, so Codex uses fewer calls: see the Chartsy skill below.
Yes. They share one config, so you set it up once.
| Surface | How you connect | Sign-in | Best for |
|---|---|---|---|
Codex CLIThis page | codex mcp add chartsy --url https://mcp.chartsy.app/mcp | Chartsy login in the browser, once | Checking numbers and writing scripts from the terminal |
IDE extension & app | Nothing extra: reads the same ~/.codex/config.toml | Same sign-in as the CLI | Data-aware changes while you edit code |
codex exec & CI | bearer_token_env_var = "CHARTSY_MCP_TOKEN" | Personal token from Chartsy → Settings → Claude & MCP | Scheduled reports and pipelines with no browser |
Engineering questions that are better with real numbers. Codex picks the tools, so the calls can vary.
Before I ship this pricing change, show MRR by plan.
Current MRR by plan:
Sample figures for a made-up business.
Write a script that posts yesterday's numbers to Slack every weekday morning.
Codex writes a cron job that:
codex exec with CHARTSY_MCP_TOKEN setUnattended runs need a personal token. One snapshot a weekday is about 22 questions a month.
Which countries should I localize for first?
Germany first, then Brazil.
Sample figures for a made-up business.
Did the new onboarding flow lift signups? It shipped two weeks ago.
Signups per visit, week by week:
Two weeks is an early read. Codex will say so.
Which plan's refunds went up after the billing refactor?
You get:
Codex picks the tools; the count can vary.
My MRR calculation says $18,900. Check it against Chartsy.
Chartsy says $18,400.
Sample figures for a made-up business.
More in the MCP prompt library.
The Chartsy skill teaches Codex which tool answers which question. Codex picks it up from ~/.agents/skills.
# Install the Chartsy skill for every project npx skills add sprifti/chartsy-agent -g # The skill needs the MCP server from step 1. # Restart Codex if it doesn't show up in /skills.
Signups only tell you half the story. Codex 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 Codex 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.
npx skills add sprifti/chartsy-agent -g
> 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. Type /mcp in Codex to see them.
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 Codex. Names, emails and write access never do.
Codex 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. Codex 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.
Start with /mcp: it shows whether chartsy is connected.
Run codex mcp login chartsy and sign in to Chartsy in the browser. If you use a token instead, check CHARTSY_MCP_TOKEN is set where Codex runs and hasn't expired or been revoked.
Unattended runs can't open a browser. Generate a personal token in Chartsy under Settings → Claude & MCP, store it as the CHARTSY_MCP_TOKEN secret, and set bearer_token_env_var = "CHARTSY_MCP_TOKEN" for the chartsy server in config.toml.
Restart Codex after installing it, and check it's in ~/.agents/skills (or .agents/skills in your repo). Type /skills to list what Codex sees.
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 your monthly allowance is used up, calls stop until it resets on the 1st, or until you upgrade your Chartsy plan.
Short answers for developers using OpenAI Codex.
Run codex mcp add chartsy --url https://mcp.chartsy.app/mcp, sign in to Chartsy in the browser and approve. If the browser doesn't open, run codex mcp login chartsy. The same config works in the Codex CLI, IDE extension and ChatGPT desktop app.
For sign-in: [mcp_servers.chartsy] url = "https://mcp.chartsy.app/mcp". For a personal token: [mcp_servers.chartsy] url = "https://mcp.chartsy.app/mcp" bearer_token_env_var = "CHARTSY_MCP_TOKEN", with the token in the CHARTSY_MCP_TOKEN environment variable.
No. Codex is OpenAI's coding agent and connects to Chartsy with one command on any setup. ChatGPT is set up separately, as a custom MCP server on a Plus, Pro, Business, Enterprise or Edu plan. Chartsy + ChatGPT.
Yes, with a personal token instead of the browser sign-in: generate it in Chartsy under Settings → Claude & MCP, store it as CHARTSY_MCP_TOKEN, set bearer_token_env_var in config.toml, and run codex exec. Each run uses one ChartsyAI question per tool call.
One per tool call, failed calls included. Most questions take one or two calls. The Chartsy skill keeps broad questions to a single snapshot call.
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.
Codex 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. Codex can't change Chartsy, your payment provider's data, or your customers, whatever its approval mode.
Run codex mcp remove chartsy, and npx skills remove chartsy if you installed the skill. To cut access everywhere, revoke it 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, run one command, and ask Codex.
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.