Build with real revenue numbers in Kimi Code

  • MRR, churn, signups and paying channels in any session
  • Check pricing, onboarding and plan changes against real data
  • Read-only, no customer names or emails
Edit mcp.json Start free trial

Chartsy is a hosted, read-only MCP server that gives Kimi Code, Moonshot AI's terminal coding agent, your MRR, churn, refunds and site traffic from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Freemius, plus which channels bring paying customers. One entry in mcp.json, then a browser sign-in. Last updated October 2026.

Kimi Code · ~/my-saasSample data

We're about to drop the Starter plan. How many customers and how much MRR is still on it?

get_mrr_by_plan1 ChartsyAI question

Starter is small, but not empty.

  • 37 paying customers and $666 MRR, 4% of the total.
  • Down from 52 customers six months ago, so it's shrinking on its own.
  • RiskRemoving it without a migration path puts that $666 at risk.
Sample figures for a made-up business.
Setup

How to add Chartsy to Kimi Code in 3 steps

One JSON entry and a browser sign-in. The server is hosted, so there's nothing to install or run.

  1. 1ConnectUnder a minute

    Add Chartsy to mcp.json

    1. Open ~/.kimi-code/mcp.json, or create it
    2. Add the chartsy entry below
    3. Prefer not to edit JSON? Run /mcp-config in Kimi Code and add it there
    ~/.kimi-code/mcp.json
    {
  "mcpServers": {
    "chartsy": {
      "url": "https://mcp.chartsy.app/mcp"
    }
  }
}

    A url with no transport means streamable HTTP, which is what Chartsy speaks. Use .kimi-code/mcp.json in a repo instead to scope it to one project.

  2. 2Sign inAbout a minute

    Sign in with your Chartsy login

    1. Start a new Kimi Code session, so it picks up the server
    2. Run the login command; a browser opens, approve access with your Chartsy login
    3. Run /mcp and check that chartsy is connected
    Kimi Code
    /mcp-config login chartsy
/mcp

    Kimi Code stores the sign-in in its own credentials folder, readable only by your user. No API key in your repo.

  3. 3AskRight away

    Ask before you change the code

    Kimi Code · ~/my-saasSample data

    Before I change the trial length: how many trial signups became paying last month?

    get_site_trafficget_new_subscribers2 ChartsyAI questions

    Roughly one in nine.

    • 412 signups and 46 new subscribers last month.
    • About the same as the month before, so the current trial isn't broken.
    Also try (click to copy)

Using another coding agent? See Claude Code, Codex or Cursor. Full server reference: Chartsy MCP server.

Which setup?

mcp.json, /mcp-config or a token: which should you use?

All three reach the same server and the same numbers. Only how you add it and how Kimi Code signs in change.

SurfaceHow you add itSign-inBest for
mcp.jsonThis page
~/.kimi-code/mcp.json, or .kimi-code/mcp.json in a repo/mcp-config login chartsyEvery session on your machine, or one project
/mcp-config
Interactive, inside Kimi CodeThe same browser sign-inAdding it without editing JSON by hand
Personal token
bearerTokenEnvVar: "CHARTSY_MCP_TOKEN"A token from Chartsy; lasts a yearHeadless runs with kimi -p, scripts and CI
What you can ask

What can you ask Kimi Code about your SaaS?

Questions that change what you build next. Kimi Code picks the tools, so the calls can vary.

Kimi Code · ~/my-saasSample data

We're about to drop the Starter plan. How many customers and how much MRR is still on it?

get_mrr_by_plan~1 question

Starter is small, but not empty.

  • 37 paying customers and $666 MRR, 4% of the total.
  • RiskRemoving it without a migration path puts that MRR at risk.

Sample figures for a made-up business.

More in the MCP prompt library.

New: revenue by channel

Which channels bring paying customers?

Signups only tell you half the story. Kimi Code can now follow each channel into your billing data, so you see which ones bring customers who pay and stay.

  • Paying customers, MRR today, churn and retention for each source, medium, UTM campaign or individual post
  • Signup-to-paid rate, the early signal for a channel that's only weeks old
  • First touch (where they found you) or last touch (what made them sign up)
  • Decide where next month's marketing time and budget go, from revenue rather than clicks

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.

Kimi Code · ~/my-saasSample data

Which channels brought paying customers last quarter, and what are they worth now?

get_revenue_by_source1 ChartsyAI question

Search brings the most money; the newsletter converts best.

  • Google: 14 paying customers, $1,260 MRR today, 11% of signups paid.
  • Newsletter: 6 paying, $690 MRR, 16% of signups paid.
  • RiskReddit: 3 paying customers, too few to call yet.
Sample figures for a made-up business.
Growth loop skill

Turn what worked into next week's posts

The Chartsy growth-loop skill teaches Kimi Code 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.

  1. Install both Chartsy skills for Kimi Code with the command here
  2. Start a new session so Kimi Code loads them
  3. Ask: "Plan next week's posts based on what brought paying customers."

Installs to ~/.agents/skills/, which Kimi Code reads in every project. The skills need the Chartsy server connected too.

View the skill
Terminal
npx skills add sprifti/chartsy-agent -a kimi-code-cli -g
Ask Kimi Code
> 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
What Chartsy gives Kimi Code

19 read-only tools Kimi Code can use

They show up in Kimi Code as mcp__chartsy__<tool>. Approve them as they come, or allow mcp__chartsy__* with a permission rule.

Revenue 6

  • Current MRRget_mrr
  • MRR by plan, over timeget_mrr_by_plan
  • MRR by countryget_mrr_by_country
  • Revenue by plan, country or payment methodget_revenue_breakdown
  • Refunds and refund ratio by planget_refund_summary
  • Progress on your goalsget_goal_progress

Customers & churn 5

  • Churn rate by periodget_churn_rate
  • New subscribers per periodget_new_subscribers
  • At-risk customerslist_at_risk_customers
  • Top customers by lifetime revenuelist_top_customers
  • MRR concentrationget_customer_concentration

Site traffic 4

  • The sites you tracklist_tracked_sites
  • Visits, visitors and signupsget_site_traffic
  • Traffic by source, campaign or pageget_traffic_sources
  • Tracked events vs your planget_monthly_events_usage

Marketing & attribution 1

  • Paying customers and MRR by channel, campaign or postget_revenue_by_source

Everything at once 3

  • Full business reviewget_business_snapshot
  • Yesterday vs the 7-day averageget_daily_snapshot
  • Accounts your login can readlist_accounts
Privacy & limits

What Kimi Code can and can't see

Numbers and customer IDs reach your session. Names, emails and write access never do.

  • Read-only

    Kimi Code can read your numbers. It can't change Chartsy, your payment provider's data, or your customers.

  • IDs, not names

    Customers are payment-processor IDs; names and emails stay in Chartsy. Kimi Code sees only the accounts and sites your login owns, checked on every call.

  • One question per tool call

    Each call uses one ChartsyAI question from your monthly allowance, failed calls included. Broad questions usually take one call.

Troubleshooting

What to do if Kimi Code can't use Chartsy

Most problems are an old session, a missing sign-in or an untrusted folder.

chartsy doesn't show up in /mcp

Kimi Code only registers a server in sessions started after you add it. Start a new session. If it still isn't there, check that ~/.kimi-code/mcp.json is valid JSON with chartsy under mcpServers.

Kimi Code says chartsy needs authorization

Run /mcp-config login chartsy and approve access with your Chartsy login. If you revoked access in Chartsy, the next sign-in creates a fresh one.

A project-level chartsy server stays disabled

Servers in a repo's .kimi-code/mcp.json only run in a folder you trust. Accept the trust prompt, or put Chartsy in ~/.kimi-code/mcp.json. Headless kimi -p runs can't show the prompt; set KIMI_CODE_TRUST_WORKSPACE=1 for that process.

I use the old Kimi CLI and the paths don't match

Kimi CLI (kimi-cli, with ~/.kimi/mcp.json and kimi mcp auth) is archived. Install the current Kimi Code CLI from code.kimi.com and run kimi migrate to bring your config across.

Kimi Code says "no connected payment provider yet"

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.

Answers stopped working this month

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.

FAQ

Chartsy for Kimi Code: frequently asked questions

Short answers for developers adding Chartsy to Kimi Code.

How do I connect Chartsy to Kimi Code?

Add a chartsy entry with url https://mcp.chartsy.app/mcp under mcpServers in ~/.kimi-code/mcp.json, or run /mcp-config in Kimi Code. Then start a new session, run /mcp-config login chartsy and approve access with your Chartsy login.

Does it work in headless kimi -p runs and CI?

Yes, with a personal token instead of a sign-in. Generate one in Chartsy → Settings → Claude & MCP, store it as the CHARTSY_MCP_TOKEN environment variable, and set "bearerTokenEnvVar": "CHARTSY_MCP_TOKEN" on the chartsy entry. Never commit the token.

Is Chartsy for Kimi Code free?

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.

Which payment providers does it work with?

Kimi Code reads whatever you have connected to Chartsy: Stripe, Paddle, Polar, Lemon Squeezy, Creem, Freemius or a custom source through the Chartsy API.

Can Kimi Code change my data?

No. All 19 Chartsy tools are read-only. Kimi Code can't change Chartsy, your payment provider's data, or your customers.

How many ChartsyAI questions does Kimi Code use?

One per tool call, failed calls included. A focused question like "how much MRR is on Starter?" is usually one call; a broad one like "give me a business review" is one get_business_snapshot call.

Will customer names or emails end up in my session?

No. Customers appear as payment-processor IDs, such as a Stripe or Paddle customer ID. Names and emails stay in Chartsy.

How do I disconnect Chartsy from Kimi Code?

Remove the chartsy entry from mcp.json, or delete it in /mcp-config. To cut access everywhere, revoke it in Chartsy under Settings → Claude & MCP. Access is checked on every call, so it stops immediately.

Can Kimi Code tell me which marketing channels bring paying customers?

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.

Other agents

Use Chartsy in other AI agents

Same server, same numbers. Or see all AI agents and the MCP server reference.

Change the code with the numbers in view

Connect your payment provider to Chartsy, add one entry to mcp.json, and ask before you ship.

Edit mcp.json Start free trial

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 Albania

The 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.