Skip to content

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.

1

In Elaichi

Connect Recharge once

  1. Open Connections, choose Add connection, and pick Recharge.

  2. Optionally set Share with to give a team access, then press Connect.

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

recharge
Recharge
Billsby
Fanvue
Metronome
Ordway
Paddle
2

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.

Recharge MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Recharge MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 111 Recharge tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Recharge, by what to check
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 $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.

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Recharge accounts List List all accounts associated to the Recharge store. Returns each account record with: id, user_id, created_at, invited_at, and is_owner.
Get single Recharge account by ID Get Get a single account associated to the Recharge store by id. Returns: id, user_id, created_at, invited_at, is_owner. Required: id.
Create a Recharge async batch Create Create a new async batch in Recharge to run bulk operations (e.g. discount_create, discount_update, discount_delete). Returns the created batch with id, batch_type, status, total_task_count, and created_at. Requires batch_type. Batches only process resources from the API version they are created in, and tasks are not attempted until the batch is submitted via process.
List all Recharge async batches List List async batches in Recharge, newest first by default. Returns each batch's id, batch_type, status, total_task_count, success_task_count, fail_task_count, and created_at/updated_at timestamps. Use sort_by to order by id or created_at.
Get single Recharge async batch by ID Get Get an async batch by id in Recharge to evaluate batch progress while it processes. Returns: id, batch_type, closed_at, created_at, deleted_at, fail_task_count, status, submitted_at, success_task_count, total_task_count, updated_at, version. Required: id.

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
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Recharge · customer subscriptions and addresses

Recharge starter 18 Mar 4, 2026

Billing toolbox

Recharge · charges and payment methods

— 9 Mar 2, 2026

Retention toolbox

Recharge · cancelations and skips

— 24 Feb 27, 2026

Fulfillment toolbox

Recharge · shipments and order batches

Recharge starter 6 Feb 19, 2026

Marketing toolbox

Recharge · discounts and customer segments

— 31 Jan 30, 2026

Operations toolbox

Recharge · async batches and account settings

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
RE

Recharge (North America)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RE

Recharge (EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RE

Recharge (APAC)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RE

Recharge (Wholesale)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
RE

Recharge (DTC Brand A)

Connected by Ryan Hayes

Personal • Active Not shared
RE

Recharge (DTC Brand B)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Recharge Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Recharge Subscriptions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Recharge Subscriptions List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch subscriptions

    Recharge

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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 my team share one Recharge connection?

Yes. One person connects Recharge in Elaichi and shares the connection with a team, and nobody else ever handles the Recharge API key. Each person still signs in to Elaichi as themselves, so the audit log names who skipped a charge or changed an address.

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.