Connect Recurly to Claude Code

Have Claude create subscriptions and issue credits in Recurly. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Recurly to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Recurly, you add a Recurly MCP server: a small hosted service that exposes Recurly'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 Recurly account. No API keys pasted into config files.

claude mcp add --transport http recurly 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 Recurly once connected?

Full read-write Recurly access lets Claude create and change subscriptions, apply coupons, issue credits or refunds, update billing details, and trigger invoices once you approve. The account research and billing changes that used to mean clicking through the dashboard happen where the subscription data already lives.

Create a new subscription on a chosen plan for an existing account
Upgrade, downgrade, or pause a subscription and preview the proration
Apply a coupon or one-time credit to an account
Issue a refund or adjustment against an invoice after you approve it
Update an account's billing information and contact details
Find accounts with past-due invoices and propose dunning actions

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 Recurly 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 Recurly API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Recurly 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 Recurly 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 Recurly 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 Recurly 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 Recurly'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 Recurly?

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 Recurly account it signs in with. Revoking access is one click in Recurly.

More on the Recurly connector

Recurly connector for claude.ai Sage Intacct + Claude Code Wave + Claude Code Zoho Books + 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