Recharge MCP by usefulapi
Server Details
Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.
- Status
- Healthy
- Uptime
- 81.0% over 55 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action (e.g., activate vs cancel subscription, list vs get for each entity). No two tools have overlapping purposes.
All tools follow a consistent pattern: recharge_<verb>_<resource> (e.g., recharge_get_subscription, recharge_list_charges). Verbs are uniform (get, list, activate, cancel, skip).
15 tools cover essential read and mutation operations for subscriptions and charges, plus read-only for other entities. This is well-scoped without being excessive or insufficient.
The server lacks create, update, and delete operations for most resources (customers, addresses, orders, products, subscriptions). Only subscription activation/cancel and charge skip are mutations. This is a significant gap for a subscription management API.
Available Tools
15 toolsrecharge_activate_subscriptionActivate subscriptionDestructiveInspect
REACTIVATES a cancelled subscription — resumes future charges. This MODIFIES live data. Recharge REST: POST /subscriptions/{id}/activate (no body). Returns { subscription }.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id to reactivate. |
recharge_cancel_customer_subscriptionCancel subscriptionDestructiveInspect
CANCELS an active subscription — stops all future charges. This MODIFIES live data. A cancellation_reason is required. Recharge REST: POST /subscriptions/{id}/cancel with JSON body { cancellation_reason, cancellation_reason_comments? }. Returns { subscription }.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id to cancel. | |
| cancellation_reason | Yes | Reason for cancelling (required by Recharge). | |
| cancellation_reason_comments | No | Optional free-text detail about the cancellation. |
recharge_get_chargeGet chargeRead-onlyInspect
Get a single charge by id, including line items, totals, status, scheduled date, and customer/address. Recharge REST: GET /charges/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Charge id. |
recharge_get_customerGet customerRead-onlyInspect
Get a single customer by id, including contact details, Shopify customer id, and subscription/charge counts. Recharge REST: GET /customers/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Customer id. |
recharge_get_orderGet orderRead-onlyInspect
Get a single order by id, including line items, totals, status, and the charge/subscription it came from. Recharge REST: GET /orders/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Order id. |
recharge_get_storeGet storeRead-onlyInspect
Get the Recharge store/shop info — name, domain, currency, timezone, and account settings. Recharge REST: GET /store.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
recharge_get_subscriptionGet subscriptionRead-onlyInspect
Get a single subscription by id, including product, quantity, price, charge interval, and next charge date. Recharge REST: GET /subscriptions/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id. |
recharge_list_addressesList addressesRead-onlyInspect
List customer addresses with optional filters (customer, ids, created/updated date ranges). Returns { addresses }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /addresses.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of address ids to fetch. | |
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| customer_id | No | Filter by customer id. | |
| created_at_max | No | Filter to addresses created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to addresses created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to addresses updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to addresses updated on/after this date (ISO 8601). |
recharge_list_chargesList chargesRead-onlyInspect
List charges with optional filters (customer, address, status, ids, purchase item, scheduled/created/updated date ranges) and sorting. Returns { charges }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /charges.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of charge ids to fetch. | |
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| status | No | Filter by charge status: success | queued | error | refunded | partially_refunded | skipped | pending_manual_payment | pending. | |
| sort_by | No | Sort order: id-asc | id-desc | updated_at-asc | updated_at-desc | scheduled_at-asc | scheduled_at-desc. | |
| address_id | No | Filter by address id. | |
| customer_id | No | Filter by customer id. | |
| scheduled_at | No | Filter to charges scheduled on this date (ISO 8601). | |
| created_at_max | No | Filter to charges created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to charges created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to charges updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to charges updated on/after this date (ISO 8601). | |
| purchase_item_id | No | Filter to charges containing this purchase item (subscription/onetime line item) id. | |
| scheduled_at_max | No | Filter to charges scheduled on/before this date (ISO 8601). | |
| scheduled_at_min | No | Filter to charges scheduled on/after this date (ISO 8601). |
recharge_list_customersList customersRead-onlyInspect
List customers with optional filters (email, ids, created/updated date ranges) and sorting. Returns { customers }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /customers.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of customer ids to fetch. | |
| No | Filter by customer email. | ||
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| sort_by | No | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. | |
| created_at_max | No | Filter to customers created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to customers created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to customers updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to customers updated on/after this date (ISO 8601). |
recharge_list_onetimesList one-timesRead-onlyInspect
List one-time (non-recurring) line items with optional filters (customer, address, created/updated date ranges). Returns { onetimes }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /onetimes.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| address_id | No | Filter by address id. | |
| customer_id | No | Filter by customer id. | |
| created_at_max | No | Filter to one-times created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to one-times created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to one-times updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to one-times updated on/after this date (ISO 8601). |
recharge_list_ordersList ordersRead-onlyInspect
List orders with optional filters (customer, address, subscription, status, ids, created/updated/scheduled date ranges) and sorting. Returns { orders }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /orders.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of order ids to fetch. | |
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| status | No | Filter by order status, e.g. success | queued | error | refunded | skipped | cancelled. | |
| sort_by | No | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. | |
| address_id | No | Filter by address id. | |
| customer_id | No | Filter by customer id. | |
| created_at_max | No | Filter to orders created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to orders created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to orders updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to orders updated on/after this date (ISO 8601). | |
| subscription_id | No | Filter by subscription id. | |
| scheduled_at_max | No | Filter to orders scheduled on/before this date (ISO 8601). | |
| scheduled_at_min | No | Filter to orders scheduled on/after this date (ISO 8601). |
recharge_list_productsList productsRead-onlyInspect
List Recharge products (subscription rules / discounts per product) with optional id filter. Returns { products }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /products.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of product ids to fetch. | |
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
recharge_list_subscriptionsList subscriptionsRead-onlyInspect
List subscriptions with optional filters (customer, address, status, ids, created/updated date ranges) and sorting. Returns { subscriptions }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /subscriptions.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Comma-separated list of subscription ids to fetch. | |
| limit | No | Max results per page (1-250, default 50). | |
| cursor | No | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. | |
| status | No | Filter by subscription status, e.g. active | cancelled | expired. | |
| sort_by | No | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. | |
| address_id | No | Filter by address id. | |
| customer_id | No | Filter by customer id. | |
| created_at_max | No | Filter to subscriptions created on/before this date (ISO 8601). | |
| created_at_min | No | Filter to subscriptions created on/after this date (ISO 8601). | |
| updated_at_max | No | Filter to subscriptions updated on/before this date (ISO 8601). | |
| updated_at_min | No | Filter to subscriptions updated on/after this date (ISO 8601). |
recharge_skip_chargeSkip chargeDestructiveInspect
SKIPS a scheduled charge — prevents it from processing on its scheduled date. This MODIFIES live billing data. Some stores require the specific line items to skip via purchase_item_ids. Recharge REST: POST /charges/{id}/skip with JSON body { purchase_item_ids? }. Returns { charge }.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Charge id to skip. | |
| purchase_item_ids | No | The subscription/onetime line item ids to skip (some stores require this). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Added
recharge_cancel_customer_subscription - Removed
recharge_cancel_subscription
15 tool updates
- Changed
recharge_activate_subscription1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_cancel_subscription1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_get_charge1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_get_customer1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_get_order1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_get_store1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_get_subscription1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_addresses1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_charges1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_customers1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_onetimes1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_orders1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_products1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_list_subscriptions1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
recharge_skip_charge1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
15 tool updates
- First observed
recharge_activate_subscription - First observed
recharge_cancel_subscription - First observed
recharge_get_charge - First observed
recharge_get_customer - First observed
recharge_get_order - First observed
recharge_get_store - First observed
recharge_get_subscription - First observed
recharge_list_addresses - First observed
recharge_list_charges - First observed
recharge_list_customers - First observed
recharge_list_onetimes - First observed
recharge_list_orders - First observed
recharge_list_products - First observed
recharge_list_subscriptions - First observed
recharge_skip_charge
Related MCP Connectors
Read payment settings, orders and receipts, create payment links and API keys.
Products, customers, orders, subscriptions, benefits, revenue metrics and refunds.
Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons.
Create and manage checkout pages, event ticketing, forms, customers, payments and subscriptions.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying Chargebee subscriptions and customer data through natural language, supporting subscription details, customer lists, and customer profiles.19 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables reading customer, subscription, transaction, and adjustment data from the Paddle Billing API to inspect billing and recurring-revenue state.57 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to customer and recurring-billing state from Recurly, including accounts, subscriptions, invoices, and payment outcomes.54 npmMIT

ChartMogul MCP Serverofficial
AlicenseAqualityFmaintenanceEnables interaction with the ChartMogul API to manage subscription data, customer relationships, and sales CRM activities. It allows users to retrieve key business metrics like MRR and churn while performing data operations on plans, invoices, and contacts.558MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.