Connect Recharge to Claude Code

Let Claude manage subscriptions and billing in Recharge. From the terminal, inside the sessions where you already work.

How do you connect Recharge to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Recharge, you add a Recharge MCP server: a small hosted service that exposes Recharge's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Recharge account. No API keys pasted into config files.

claude mcp add --transport http recharge https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Recharge once connected?

Full read-write Recharge access lets Claude act on subscriptions where they live: pause or reactivate a plan, swap the product on a subscription, change quantity or next charge date, apply a retention discount, and update a customer's payment or address. The cancellation triage that meant clicking through the merchant portal happens in one approved step.

Pause, skip, or reactivate a subscription for a specific customer
Swap the product or variant on an active subscription
Change the quantity or shift the next charge date
Apply a retention discount code to a subscription
Update a subscriber's shipping address or billing details
Cancel a subscription with a reason once you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Recharge access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Recharge API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Recharge changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Recharge connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Recharge connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Recharge account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Recharge's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Recharge?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Recharge account it signs in with. Revoking access is one click in Recharge.

More on the Recharge connector

Recharge connector for claude.ai Wix + Claude Code Ecwid + Claude Code Etsy + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us