Recurly MCP servers compared: documentation, raw API, and operations

There are a few ways to connect Recurly to Claude or ChatGPT today. They solve different problems. Here is an honest comparison to help you pick.

By Thomas Fitzgerald, Marketing · 2026-10-18

MCP (the Model Context Protocol) lets AI assistants like Claude and ChatGPT use outside tools. If your subscriptions run on Recurly, there are now several MCP servers you could connect. They are not interchangeable, because they answer different questions.

This is our honest read as of October 2026. We make one of them, so weigh that accordingly, and check each provider's own documentation for the current details.

1. Recurly's own: documentation and code

Recurly publishes Recurly Compass MCP, a public server for documentation and code. According to Recurly's documentation, it has a knowledge agent that answers questions about Recurly's docs and a coding agent that gives code examples and API parameter references.

Good for: developers building on Recurly, and anyone asking "how does Recurly do X?"

Not for: questions about your own customers and billing data. It doesn't read your account.

2. General-purpose API connectors

Integration platforms offer Recurly connectors that expose Recurly's API actions to an AI, usually authenticated with your Recurly API key. Some are hosted, some are open source.

Good for: developers and technical users who want the AI to call specific API endpoints, and teams already using that platform for other connectors.

Things to weigh: an API action is not a question. "Decline rate by affiliate this week" means pulling transactions and accounts, joining them and counting, and with raw actions the AI does that page by page, within your context window. Changes go straight to the API, so any limits, approvals and audit trail are yours to build. And a Recurly API key typically sits in the connector's configuration.

3. Operations: Retrixus

Retrixus is built for subscription teams rather than developers: operations, support, finance and fraud.

What's different:

• Questions, answered. Retrixus pulls and joins the records itself and returns the answer, across every Recurly site you run at once, including this morning.
• Honest limits. If a question needs more records than it can read, it says how far it got rather than returning a partial count.
• Changes inside your rules. Refunds and cancels are checked against limits you set, previewed, sent for approval when they're over a limit, and recorded in an audit log that can't be edited.
• Bulk fixes. Plan a change for a whole group of accounts, see every account first, then run it safely in the background.
• Watches. Alerts by email or Slack when signups, declines, fraud blocks or failed renewals look unusual.
• Zendesk alongside, and an Agent Console for phone agents.
• No API key in chat. People sign in with Google or an emailed link; your Recurly key stays in a secret store.
• Easy on your account. It uses at most half of your site's Recurly API limit.

Not for: documentation lookups (use Recurly's own), or arbitrary API calls Retrixus doesn't expose.

Which to choose

• Building an integration? Recurly Compass, plus the API.
• Want an AI to call specific Recurly endpoints and you're comfortable managing keys and guardrails? A general-purpose connector.
• Want your whole team asking questions about customers and billing, with changes made safely? Retrixus.

Plenty of teams will use more than one. Retrixus is free to try on one Recurly site.