Subscription Platform
Recharge MCP connector
The Recharge connector brings subscription charges, customer addresses, bundle selections, and accounts into Claude, ChatGPT, Cursor, and any MCP client, so your team can check, skip, and discount subscription orders from a chat window.
-
How it connects. Connects with an API key. 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 Recharge to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Recharge once
-
Open Connections, choose Add connection, and pick Recharge.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Recharge API key. One person generates a token in Recharge and pastes it once. Everyone else works through Share with, and never sees it.
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.
Connect Recharge to 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.
Connect Recharge to 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.
Connect Recharge to 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 Recharge 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 Recharge through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Skip a charge for a customer on request
When a subscriber writes in asking to pause next month's box, find their upcoming Recharge charge and skip it without opening the Recharge admin.
-
Support
Fix a shipping address before the next charge
Look up the address on a subscriber's Recharge account, update it, and merge duplicate addresses so the next shipment goes to the right place.
-
Retention
Apply a discount to keep a subscriber
When someone is about to cancel, apply a discount code to their next Recharge charge and confirm the new total in the same conversation.
-
Operations
Swap products in a bundle subscription
Review a subscriber's bundle selections in Recharge and update the items before the next charge is processed.
-
Finance
Review upcoming and failed charges
List Recharge charges by status or date, pull up a single charge to check line items and totals, and remove a discount that was applied in error.
-
Operations
Run bulk changes as a batch
Create an async batch in Recharge for a large set of updates, start it, and check the list of tasks to see what has finished.
Try asking
- “Show subscriptions at risk of cancelation this week.”
- “Summarize address changes across all customer accounts.”
- “List charges that failed processing in the last batch.”
AI tools
Recharge tools for your AI agents
111 tools are ready to call through Elaichi's MCP endpoint the moment you connect Recharge, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Recharge gets you
6 screens from the product, each doing one job for your Recharge account.
The agent
Ask Recharge questions, get live answers.
Ask about subscriptions, addresses and charges in plain language and get answers from live records.
- subscriptions
- addresses
- charges
- customers
Ask Elaichi to work across your apps.
Show subscriptions at risk of cancelation this week.
Summarize address changes across all customer accounts.
List charges that failed processing in the last batch.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Recharge endpoint, any MCP client.
Connect Claude, ChatGPT or Cursor to Recharge through one governed org endpoint, no SDK or shared key.
Copy the endpoint
Tool catalog
111 Recharge tools, zero custom code.
Browse every Recharge tool, resource and method available without writing a single line of custom code.
- List all Recharge accounts
- Get single Recharge account by ID
- Create a Recharge async batch
- List all Recharge async batches
Toolboxes
Every team gets its own Recharge toolbox.
Give each team a Recharge toolbox scoped to the work they actually do.
- Support
- Billing
- Retention
- Fulfillment
Shared connections
Delegated Recharge access, no shared credentials.
See who connected each Recharge account and how many teams and members share it.
- North America
- EMEA
- APAC
- Wholesale
Audit log
Every Recharge action, logged and attributed.
Answer who did what in Recharge with a complete, append-only audit log.
- When
- Who
- What happened
- Type
Launching 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
Recharge digests run themselves, you approve.
A schedule fetches Recharge records, drafts a digest, and posts it back once a person approves.
Recharge digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch subscriptions
Recharge
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
Recharge
Queued
Collections and dashboards
Recharge health, computed on a schedule.
Track subscriptions and charges with a 14 day chart and team breakdown, no model required.
Recharge health
Refreshed 4 minutes ago · every 15 minutes · from the subscriptions collection
Subscriptions
1,284 ↓ 12%
Addresses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Subscriptions created
Last 14 days
By team
Share of activity
North America 34%
EMEA 27%
APAC 21%
Wholesale 18%
FAQ
Frequently asked questions
How do I connect Recharge to Claude?
Connect Recharge in Elaichi first: open the Recharge connector, paste an API key from your Recharge admin, and save. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, so the whole setup takes a few minutes.
Does Recharge work with ChatGPT and Cursor as well as Claude?
Yes. Once Recharge is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Recharge once and every client picks it up.
What can an AI agent actually do with my Recharge data?
With Recharge connected, an agent can look up a subscriber's account, list their upcoming or past charges, skip a charge, apply or remove a discount on a charge, and update or merge shipping addresses. It can also review and change bundle selections and create batches for large sets of updates. Short, concrete asks such as "skip the next charge for this customer" work better than long instructions.
Does connecting Recharge give the AI access to my whole store?
No. Access to Recharge follows the API key and the person who signed in, so the agent sees only what that Recharge account can see. Elaichi can narrow that further by removing actions for a team, and it never widens what Recharge itself allows.
Can I stop an agent from deleting or changing things in Recharge?
Yes. Restrictions in Elaichi work per action, so you can allow reading Recharge charges and accounts while blocking address deletion or discount changes. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to a Recharge connection when someone leaves?
Offboarding a person in Elaichi ends their access to Recharge at once, across every client they used. A shared Recharge connection keeps working for everyone else on the team. If you disconnect Recharge in Elaichi, it is removed from Claude, ChatGPT, Cursor, and every other client in one step.
Put Recharge in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.