Recharge MCP. Manage every billing detail without leaving your agent.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Recharge MCP Server manages subscription commerce directly from any AI agent. This server exposes 11 tools for handling recurring billing, customer records, and order fulfillment via Recharge.
You can list active subscriptions, get detailed customer profiles, track specific orders, or update subscription parameters—all without navigating the dashboard.
It makes managing your entire subscription lifecycle conversational.
What your AI agents can do
Cancel subscription
Stops a specific subscription immediately using its ID.
Get customer
Retrieves all profile and billing details for one customer ID.
Get order
Pulls full information about a single, completed subscription order.
Retrieves a list of all existing Recharge subscriptions, including status and basic details.
Fetches detailed information for a specific subscriber using their unique ID.
Retrieves full details about a single, processed subscription order.
Lists all historical and recent charges associated with your store's recurring revenue.
Retrieves a catalog of every subscription product offered through Recharge.
Updates key parameters on an active subscription, such as its quantity or renewal date.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 CompatibleWaiting for input…
Recharge MCP Server: 11 Tools for Commerce Ops
These tools allow your AI client to interact directly with the Recharge API. Manage everything from listing customers and products to updating subscriptions and reviewing billing charges.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Recharge on Vinkius019dd148cancel subscription
Stops a specific subscription immediately using its ID.
019dd148get customer
Retrieves all profile and billing details for one customer ID.
019dd148get order
Pulls full information about a single, completed subscription order.
019dd148get subscription details
Fetches all specific metadata and parameters for one active subscription ID.
019dd148list billing charges
Outputs a list of recent processed charges and billing history records.
019dd148list customers
Provides a paginated list containing IDs for all Recharge customers.
019dd148list products
Returns the catalog of every subscription product available in your store.
019dd148list shipping addresses
Lists and retrieves all stored physical shipping addresses for customers.
019dd148list subscription orders
Retrieves a list of processed subscription orders, allowing bulk review.
019dd148list subscriptions
Gives an overview and status of all subscriptions currently managed by Recharge.
019dd148update subscription
Makes direct changes to a subscription, such as changing its plan or quantity.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Recharge, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Recharge. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Reviewing customer accounts used to mean jumping through a dozen tabs.
Today, tracking down basic subscription info is painful. You open the main dashboard, navigate to 'Customers,' find the user's ID in one tab; then you have to click into their profile on another tab just to see if they are paid up or what address they used for shipping. It’s a lot of clicking and copy-pasting IDs across different views.
With this MCP server, that process is gone. Your agent handles the jumps. You ask it to 'Check Jane Doe's status,' and in one go, you get structured data covering her profile (`get_customer`), her current plan details (`get_subscription_details`), and a list of recent orders—all without leaving the chat window.
Recharge MCP Server: Complete Billing & Order Ops
The biggest time sinks disappear. You no longer need to manually generate reports on charges or run separate queries for order history. The agent pulls all that data together. If you suspect a billing issue, you don't check one place; you compare the output of `list_billing_charges` directly against what was captured by `get_order`. It’s immediate reconciliation.
What's different now is speed and accuracy. You stop spending time gathering data from siloed dashboards. You get a single, definitive source of truth for your customer lifecycle, built into your workflow.
What you can do with this MCP connector
Recharge MCP Server lets your agent talk directly to your billing backend. You connect any AI client—Claude, Cursor, whatever—and you can manage recurring commerce stuff in natural conversation. This server exposes eleven specific tools that let your agent handle everything from listing active subscriptions to updating customer data and reviewing full financial history without ever touching the main Recharge dashboard.
It makes managing your whole subscription life cycle a conversational thing.
Managing Subscriptions
You've got list_subscriptions when you need an overview of every existing Recharge subscription; it gives you the status and basic details for all of them at once. If you know a specific subscription ID, you can pull deep metadata and parameters using get_subscription_details, which shows exactly what that plan is doing right now.
You'll use update_subscription when you need to change key parameters on an active account—say, bumping up the quantity or tweaking the renewal date. Need to shut something down? Just give your agent cancel_subscription with the specific ID, and it stops the subscription immediately.
Customer Data Access
You can start by pulling a paginated list of all customer IDs using list_customers. Once you have those IDs, you fetch detailed information for any single subscriber—their full profile and billing records—with get_customer. You also get access to physical location data; list_shipping_addresses gathers every stored shipping address across your user base.
If you need to look at historical order fulfillment, list_subscription_orders pulls a list of processed orders for bulk review, and you can dive into the specifics of one completed transaction using get_order. Furthermore, your agent can get a complete catalog of every single subscription product available in the store by running list_products.
Billing and Financial History
When it comes to money, you've got deep visibility. You pull all recent processed charges and see the full billing history records using list_billing_charges. If a customer needs help with their account status, your agent can first list every single subscription using list_subscriptions for an immediate overview, then drill down into specific transaction details by pulling either a whole order record via get_order or checking the deep parameters of one active subscription using get_subscription_details.
You don't have to leave the chat window to manage this; your AI client handles the tool calls directly.
This setup lets you skip the dashboard entirely. You pull customer IDs with list_customers, get their full details with get_customer and review all addresses using list_shipping_addresses. If a plan needs adjusting, you use update_subscription; if it's done, you call cancel_subscription. For billing reviews, you run list_billing_charges to see the history, or get the full details of a past order with get_order.
019dd148-e16e-7123-9a8d-74bb122ef7c0 How Recharge MCP Works
- 1 Subscribe to the Recharge server and provide your API Access Token from your store settings.
- 2 Your AI client calls a specific tool (e.g.,
list_subscriptions) using the required parameters. - 3 The agent executes the function against the Recharge platform, returning structured data that you can use immediately.
The bottom line is you don't talk to the dashboard; your agent talks directly to your billing database via predictable API calls.
Who Is Recharge MCP For?
This is for FinOps Engineers, E-commerce Operations Managers, and Billing Analysts. You're the person who wakes up at 2 AM staring at a dashboard full of red flags—a forgotten renewal, an incorrect charge, or a customer asking 'Why was I charged twice?' This tool lets you run complex queries and make fixes without ever logging into the web UI.
Needs to check if a bulk list of customers are properly subscribed or needs to correct an incorrect subscription quantity for several accounts quickly.
Must reconcile charges and identify the source of revenue loss by comparing data from list_billing_charges against specific customer profiles.
Has to look up an order's history or check a user's payment method status without giving out internal credentials over the phone.
What Changes When You Connect
- Real-time status checks: Use
list_subscriptionsto instantly see if a user's plan is active, cancelled, or suspended. You don't have to manually check the customer portal for basic status updates. - Deep financial dives:
list_billing_chargesgives you access to historical transaction data, letting your agent calculate revenue loss or verify a specific payment date without generating a manual report. - Customer record lookup: The
get_customertool pulls the entire profile—including shipping addresses (list_shipping_addresses) and billing info—into one structured response for easy review. - Subscription adjustments on the fly: Never manually change a plan again. Use
update_subscriptionto modify quantities or reschedule charges directly through your conversation with the agent. - Full order transparency: You can track down specific transactions using
get_order. This means you know exactly when an item shipped and what was charged for it, solving fulfillment questions instantly.
Real-World Use Cases
Investigating a double charge
A customer contacts support claiming they were double-charged. Instead of asking the user to email screenshots, your agent runs get_order and compares it against list_billing_charges. The output immediately shows two separate charges on different dates, clarifying that one was for a premium add-on billed separately.
Bulk status audit
The ops team needs to verify which high-value customers are currently subscribed. They ask the agent to run list_subscriptions, filtering only by 'Premium' plans and checking if they have paid in the last 30 days using the output of get_subscription_details.
Mid-cycle plan upgrade
A user calls to upgrade their service immediately. The agent first uses get_customer to verify the account is in good standing, then runs update_subscription to change the product and quantity, ensuring the charge date is correct.
Identifying lapsed accounts
The marketing team wants a list of customers who haven't placed an order or checked their details in 60 days. The agent runs list_customers and then cross-references the resulting IDs against recent data from list_subscription_orders to find stale records.
The Tradeoffs
Assuming one tool covers everything
The user just asks, 'Can you fix my bill?' This vague request forces the agent to guess, potentially running get_customer when what's actually needed is a specific historical check via list_billing_charges.
→
Don't ask for generic fixes. Instead, tell your agent exactly what data point you need: 'Check my billing history for any charges over $100 last month using list_billing_charges.' Specific tools yield specific results.
Trying to update without checking existence
The user attempts to run update_subscription(id='fake-uuid'). Since the ID is bad, the API call fails silently or returns a generic error that doesn't tell you why it failed.
→
Always verify data first. Before updating anything with update_subscription, use get_subscription_details to confirm the subscription exists and check its current state.
Over-relying on product names
A user says, 'Update my coffee box.' This is too vague. The agent doesn't know if they mean the active plan or a retired one.
→
Use specific identifiers. Always reference the subscription ID (found via list_subscriptions) and then use that ID with update_subscription to ensure you are modifying the right thing.
When It Fits, When It Doesn't
You need this server if your job involves interpreting or changing structured billing data (charges, customer profiles, plan statuses). Use it when manual dashboard navigation is too slow or error-prone. For example, if a user calls about a charge discrepancy, you use list_billing_charges and then cross-reference the result with get_customer. Don't use this server if you just need to know general marketing stats (like total users who signed up) that don't involve billing status. For those, you might look at an analytics API instead of a transaction management tool.
Crucially: If you only have product names and no IDs, start by calling list_products or list_subscriptions. Never assume the data structure until you run one of the initial listing tools.
Common Questions About Recharge MCP
How do I check all my active subscriptions using list_subscriptions? +
You simply ask the agent to run list_subscriptions. It returns a structured list showing every subscription ID, status (active/cancelled), and basic plan metadata.
Can I use get_customer to find billing addresses? +
Yes. The get_customer tool retrieves the complete customer profile, which includes all stored billing information and a list of associated shipping addresses (list_shipping_addresses).
What if I need to change a plan? Do I use update_subscription? +
Yes. You must use update_subscription. Remember, you'll need the specific subscription ID first; never guess it.
Can list_billing_charges show me charges from last year? +
The tool lists processed and recent charges. While it provides historical data, always check its documentation for date range limitations to ensure you pull the full history needed.
When I use `list_customers`, what credentials does my AI client need to authenticate? +
You must provide a valid Recharge API Access Token. This token acts as your primary authentication key, granting the agent read/write access to all customer data. The server validates this token first; if it's missing or expired, no tools will execute.
Does `list_products` return every product available in my store, or only those currently subscribed to? +
list_products returns the full catalog of subscription products. This lets your agent see all options—whether they are active, paused, or archived. It gives you a complete list for cross-referencing data.
If I run `get_order` and provide an Order ID that doesn't exist, what error does the server return? +
The system returns a standard 'Not Found' (404) error. Your agent handles this by reporting back to you that the specific order ID was invalid. You can then prompt it to search using different criteria.
Is there a rate limit if I call `list_subscriptions` repeatedly in one session? +
Yes, like any external API, there are usage limits. For large datasets, the server employs pagination; you'll need to handle the 'next page' tokens returned by the tool to ensure you retrieve every single subscription record.
Can I list all my active subscriptions using my AI agent? +
Yes! Use the list_subscriptions tool to retrieve a comprehensive list of all active and cancelled subscriptions in your account.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.