Recharge MCP connector
The Recharge connector brings subscription charges, customer addresses, bundle selections, and accounts into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so your team can check, skip, and discount subscription orders from a chat window.
- Connects with an API key
- Free 14-day trial
- No credit card
Show subscriptions at risk of cancelation this week.
Working in Recharge with Elaichi
-
List all Recharge accounts
-
Get single Recharge account by ID
-
List all Recharge async batches
How to connect Recharge to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Recharge 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.
Recharge MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Recharge 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. The plugin directory lives at chatgpt.com/plugins.
Recharge 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.
Recharge MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Recharge through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Recharge is logged.
-
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.”
What connecting Recharge gets you
6 screens from Elaichi, each doing one job for your Recharge account.
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, Cursor or Microsoft Copilot
The agent
Ask Recharge questions, get live answers.
Ask about subscriptions, addresses and charges in plain language and get answers from live records.
Copy the endpoint
AI apps
One Recharge endpoint, any MCP client.
Connect Claude, ChatGPT, Cursor or Microsoft Copilot to Recharge through one governed org endpoint, no SDK or shared key.
Tool catalog
111 Recharge tools, zero custom code.
Browse every Recharge tool, resource and method available without writing a single line of custom code.
Toolboxes
Every team gets its own Recharge toolbox.
Give each team a Recharge toolbox scoped to the work they actually do.
Shared connections
Delegated Recharge access, no shared credentials.
See who connected each Recharge account and how many teams and members share it.
Audit log
Every Recharge action, logged and attributed.
Answer who did what in Recharge with a complete, append-only audit log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Recharge digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Recharge
Queued
Automations
Recharge digests run themselves, you approve.
A schedule fetches Recharge records, drafts a digest, and posts it back once a person approves.
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%
Collections and dashboards
Recharge health, computed on a schedule.
Track subscriptions and charges with a 14 day chart and team breakdown, no model required.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Recharge
All three can connect Recharge 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 Recharge tools | Allow or restrict single Recharge 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 Recharge 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 role, 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 restricting address deletion or discount changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client in one step.
Does the Recharge MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Recharge 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, Microsoft Copilot, 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 Recharge?
Yes. Both let Claude, ChatGPT or Cursor use Recharge. 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 Recharge call.
How is Elaichi different from Composio for Recharge?
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 Recharge: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Recharge in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot