ChartMogul MCP connector
Connect ChartMogul to Elaichi and Claude, ChatGPT, Cursor or the Elaichi Agent can answer questions about your MRR, churn, retention, customers, invoices and pipeline, each person inside their own ChartMogul access, with every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect ChartMogul to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ChartMogul once
-
Open Connections, choose Add connection, and pick ChartMogul.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in ChartMogul. ChartMogul's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
ChartMogul MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ChartMogul MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
ChartMogul MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect ChartMogul to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with ChartMogul through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Pull month-end MRR without opening a dashboard
Ask for last month's MRR, new business, expansion and contraction and get the figures straight from ChartMogul. Paste them into the board deck and move on.
-
Revenue operations
Explain a churn spike before the meeting
Ask which customers churned this quarter, what plans they were on and what they were paying. Walk into the review with names, not a guess.
-
Sales
Check a prospect's history before the call
Look up whether an account already exists in ChartMogul, what it paid before and where it sits in the pipeline, all in one question.
-
Customer success
Spot accounts worth a renewal conversation
Ask for customers whose subscription value dropped in the last 90 days or whose invoices are overdue, then plan the outreach.
-
Leadership
Get a retention answer in plain language
Ask how net revenue retention compares to the same quarter last year and get the number with the cohort behind it.
-
Marketing
See which plans actually grow revenue
Ask which plans added the most MRR this month and which lose customers fastest, then point campaigns at the ones that stick.
Try asking
- “What was our MRR last month and how did it change?”
- “Which customers churned this quarter and what plans were they on?”
- “Show me overdue invoices for enterprise customers.”
Native MCP
Why connect ChartMogul's MCP server through Elaichi
ChartMogul builds and runs this MCP server. Elaichi sits in front of it, so ChartMogul's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to ChartMogul's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT and Cursor reach ChartMogul's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds ChartMogul's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own ChartMogul sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches ChartMogul's server. By default, a tool ChartMogul does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to ChartMogul
ChartMogul builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the ChartMogul team.
Compare
Elaichi vs Zapier MCP vs Composio for ChartMogul
All three can connect ChartMogul to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ChartMogul tools | Allow or restrict single ChartMogul tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ChartMogul call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting ChartMogul gets you
5 screens from the product, each doing one job for your ChartMogul account.
The agent
Ask about MRR and get a live answer.
Type a question in plain language and get numbers from your ChartMogul account.
- customers
- invoices
- subscriptions
- metrics
Ask Elaichi to work across your apps.
What was our MRR last month and how did it change?
Which customers churned this quarter and what plans were they on?
Show me overdue invoices for enterprise customers.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach ChartMogul through one governed endpoint, with no SDK to install.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own ChartMogul toolbox.
Finance sees invoices and MRR, sales sees pipeline, each scoped to the team that needs it.
- Finance
- Revenue operations
- Sales
- Customer success
ElaichiToolboxesShared connections
Share ChartMogul access without sharing a credential.
One person connects, the team works through it, and nobody else ever sees a key.
- Finance
- RevOps
- Sales
- Customer success
ElaichiConnectionsAudit log
Know who pulled which ChartMogul number, and when.
Every call lands in an append-only log with who, what, type and resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules start the churn digest, people approve it.
Churned customers are fetched, grouped, drafted into a digest, approved, then sent, all from one trigger.
ChartMogul digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
ChartMogul
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
ChartMogul
Queued
Collections and dashboards
ChartMogul health, computed on a schedule, no prompt.
Four metrics, 14 days of customers created and a team breakdown, computed without a model.
ChartMogul health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Invoices
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Finance 34%
RevOps 27%
Sales 21%
Customer success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect ChartMogul to Claude?
Two steps. In Elaichi, choose ChartMogul, sign in to your ChartMogul account and approve access, which takes about a minute and needs no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once and ChartMogul is ready.
Does ChartMogul work with ChatGPT and Cursor as well as Claude?
Yes. Once ChartMogul is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect ChartMogul once and every client picks it up.
What can an AI agent actually do with my ChartMogul data?
It can read your subscription metrics such as MRR, churn and retention, and look up customers, invoices and sales pipeline records in ChartMogul. Ask for last month's MRR, the customers who churned this quarter, or overdue invoices for a segment and it answers from live ChartMogul numbers. Short, concrete asks work better than long sentences.
Does connecting ChartMogul give the AI access to everything in my account?
No. Every call runs as the person who signed in to ChartMogul, so the agent sees exactly the metrics, customers and invoices that person can already see, and nothing more. Elaichi can narrow that access further for a team or a person, but it can never widen it beyond what ChartMogul grants.
Can I stop an agent from changing things in ChartMogul?
Yes. Restrictions in Elaichi work per action, so you decide which ChartMogul capabilities a team can use. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however clever, can reach it.
What happens to a ChartMogul connection when someone leaves?
Offboarding that person in Elaichi ends their ChartMogul access at once across Claude, ChatGPT, Cursor and every other client. A shared ChartMogul connection keeps working for everyone else on the team. If you ever want ChartMogul gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the ChartMogul MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ChartMogul is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for ChartMogul?
Yes. Both let Claude, ChatGPT or Cursor use ChartMogul. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ChartMogul call.
How is Elaichi different from Composio for ChartMogul?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ChartMogul: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ChartMogul in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.