Recharge integration
Recharge subscription commerce through its REST API. Read and write recurring subscriptions and the records around them: customers, shipping addresses, upcoming and past charges, resulting orders, one time purchases, the product catalogue and the store settings. Every call in this integration pins the 2021-11 version, because an unpinned call inherits whatever version the store happens to default to, which changes both the paths and the way paging works.
Say what should happen.
The workflow builds itself.
Common Recharge use cases
- diagnosing why a payment failed
- finding failed charges to retry
- honouring a cancellation request
- reporting on active recurring revenue
- reading a customer before a support reply
- auditing add ons queued on upcoming charges
- migrating subscriptions from another platform
- applying a quantity change a customer asked for
- reading the next charge date before changing it
- delaying a shipment a customer asked to postpone
What you can do with Recharge
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Subscription, 7 operations
activate_subscriptionActivate subscriptionPOSTBrings a cancelled subscription back to active and returns it.cancel_subscriptionCancel subscriptionPOSTCancels a subscription and returns it in its cancelled state.create_subscriptionCreate subscriptionPOSTCreates a subscription and returns the stored record.get_subscriptionGet subscriptionGETReturns a single subscription under the subscription key.list_subscriptionsList subscriptionsGETReturns a page of subscriptions with the cursor of the next page beside them.set_next_charge_dateSet next charge datePOSTReschedules the next charge of a subscription.update_subscriptionUpdate subscriptionPUTApplies a partial update to a subscription and returns the stored record.
Customer, 3 operations
create_customerCreate customerPOSTCreates a customer and returns the stored record.get_customerGet customerGETReturns a single customer under the customer key.list_customersList customersGETReturns a page of customers with the cursor of the next page beside them.
Address, 2 operations
create_addressCreate addressPOSTCreates an address and returns the stored record.list_addressesList addressesGETReturns a page of addresses.
Charge, 2 operations
get_chargeGet chargeGETReturns a single charge under the charge key.list_chargesList chargesGETReturns a page of charges.
Onetime, 1 operation
list_onetimesList onetimesGETReturns a page of one time products.
Order, 1 operation
list_ordersList ordersGETReturns a page of orders.
Product, 1 operation
list_productsList productsGETReturns a page of products with their variants.
Store, 1 operation
get_storeGet storeGETReturns the store configuration under the store key.
Use Recharge from Claude Code, Cursor or Codex
Connect Recharge in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Recharge operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Recharge
- Create your workspace
Sign up free. Nothing to install.
- Connect Recharge once
Add your Recharge connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Recharge integration FAQ
What can you do with the Recharge integration?
LiveContext exposes 18 operations on Recharge, covering subscription, customer, address and charge. Common uses include diagnosing why a payment failed, finding failed charges to retry and honouring a cancellation request.
