Recharge MCP Server

by usefulapi Your server? Claim it

answering

Recharge is answering right now. Last checked 15 min ago. It exposes 15 tools. Last commit 1 Sep 2026.

Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.

Uptime history 47 days of history · worst day 15%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

180 ms

Response time

average over 24h

Stars

last commit 1 Sep 2026

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Page executes code built at runtime portal/index.html:231

        results.innerHTML = order.map(function (g) {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add recharge --transport http https://recharge.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "recharge": {
      "url": "https://recharge.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.recharge]
url = "https://recharge.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "recharge": {
      "url": "https://recharge.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "recharge": {
      "url": "https://recharge.usefulapi.io/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recharge

recharge_activate_subscription

REACTIVATES a cancelled subscription — resumes future charges. This MODIFIES live data. Recharge REST: POST /subscriptions/{id}/activate (no body). Returns { subscription }.

recharge_cancel_subscription

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 }.

recharge_get_charge

Get a single charge by id, including line items, totals, status, scheduled date, and customer/address. Recharge REST: GET /charges/{id}.

recharge_get_customer

Get a single customer by id, including contact details, Shopify customer id, and subscription/charge counts. Recharge REST: GET /customers/{id}.

recharge_get_order

Get a single order by id, including line items, totals, status, and the charge/subscription it came from. Recharge REST: GET /orders/{id}.

recharge_get_store

Get the Recharge store/shop info — name, domain, currency, timezone, and account settings. Recharge REST: GET /store.

recharge_get_subscription

Get a single subscription by id, including product, quantity, price, charge interval, and next charge date. Recharge REST: GET /subscriptions/{id}.

recharge_list_addresses

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.

recharge_list_charges

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.

recharge_list_customers

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.

recharge_list_onetimes

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.

recharge_list_orders

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.

recharge_list_products

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.

recharge_list_subscriptions

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.

recharge_skip_charge

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 }.

Endpoints

URL	Transport	State	Latency	Checked
https://recharge.usefulapi.io/mcp	streamable-http	answering	243 ms	15 min ago

Alternatives to Recharge

same job, measured the same way

MCP Stripe

by infoinlet-marketplace

Read-only Stripe for AI agents — customers, charges, subscriptions, invoices, balance.

26 installs/wk local only

Orb

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Foxyio

by usefulapi

Read Foxy transactions, subscriptions, customers, carts and coupons; update customers and subs.

14 tools answering

Cakto

by mcp-dir

Read your Cakto sales: orders, revenue analytics, subscriptions, churn, customers and products.

27 tools answering

Chargebee

by usefulapi

Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons.

13 tools answering

Stripe MCP Server

by friendlygeorge

MCP server for Stripe API — customers, charges, payments, subscriptions, products, and invoices

36 installs/wk local only

Lago

by usefulapi

Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.

24 tools answering

ZeroSettle

by zerosettle

Read-only revenue, subscriptions, customers, and experiments tools for ZeroSettle accounts.

answering

Recharge — questions

Answers built from our own checks of this server.

What can Recharge do?

It exposes 15 tools, read directly from the server on our last check. Among them: recharge_activate_subscription, recharge_cancel_subscription, recharge_get_charge, recharge_get_customer, recharge_get_order, recharge_get_store and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Recharge working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 180 ms. The bar chart above shows every period we have measured.

How do I connect Recharge?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Recharge need an API key?

No. Recharge completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Recharge?

It answers our handshake in 180 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Recharge open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.