- No first-party Recharge MCP server or documentation exists as of the public record and source read on 2026-08-31.
- Recharge-Storefront-API-MCP's README claims 87 tools across 16 categories; src/tools/index.js:5-19 registers 77 across 15 modules.
- The README's entire 8-tool 'Authentication' category (README.md:805-816) has no source file, import, or registration anywhere in the repo.
- Auth uses a two-tier admin-token-to-customer-session-token model (src/recharge-client.js:785-811), scoped to one customer per session.
- The session cache discards the Recharge API's own token expiry, storing only token/email/createdAt/lastUsed and relying on a blanket 4-hour createdAt sweep (src/utils/session-cache.js:9-10, :52-57; sweep call at src/recharge-client.js:204-206).
- clearSessionsForDomain wipes the entire session cache instead of scoping to one store, since sessions aren't tagged with which store they belong to (src/utils/session-cache.js:160-172).
01 What Recharge-Storefront-API-MCP is and who ships it
No first-party Recharge MCP server exists — as of the public record and source read on 2026-08-31, getrecharge.com and developer.rechargepayments.com carry Recharge's REST API documentation and nothing about the Model Context Protocol. The only entry in this category is Recharge-Storefront-API-MCP, a community project from bearded-giant, and the pick here comes with a catch worth knowing before you install it: its README documents 87 tools across 16 categories, but the source registers exactly 77 tools across 15 imported modules, and the entire 8-tool "Authentication" category the README lists — login_shopify_app_proxy, send_passwordless_code, validate_passwordless_code, and five others — has no source file, no import and no registration anywhere in the repository.
Recharge-Storefront-API-MCP wraps Recharge's Storefront API — the customer-facing half of Recharge's subscription platform — in an MCP server for AI assistants and other MCP clients. It's unambiguously community-maintained, not first-party: the repository lives at github.com/bearded-giant/Recharge-Storefront-API-MCP, is licensed MIT, and as read on 2026-08-31 sits at 2 stars, 3 forks and 0 open issues, with a default-branch (main) last commit dated 2026-02-10 (commit 2eded80).
| Metric | Recharge-Storefront-API-MCP |
|---|---|
| Maintainer | bearded-giant (community) |
| First-party | No |
| Licence | MIT |
| Stars | 2 |
| Forks | 3 |
| Open issues | 0 |
| Last commit (default branch) | 2026-02-10 |
| README-claimed tool count | 87 tools / 16 categories |
| Source-registered tool count | 77 tools / 15 modules |
02 Tools it exposes: 77 registered across the Storefront API
The tool aggregator at src/tools/index.js:5-19 imports exactly 15 modules, and src/tools/index.js:21-36 spreads them into the exported tool list — a count of name: registrations across those 15 files totals 77, not the 87 the README's category table implies. The table below shows a representative selection from that 77-tool registration — not the full inventory — covering customer, subscription, address, payment, catalog and order operations:
| Tool | What it does | Read/Write |
|---|---|---|
| get_customer / get_customer_by_email | Look up a customer record | Read |
| update_customer | Edit a customer record | Write |
| create_customer_session_by_id | Mint a per-customer storefront session token | Write |
| get_delivery_schedule | Return upcoming delivery dates | Read |
| get_customer_portal_access / get_churn_landing_page_url / get_payment_recovery_url / get_gift_redemption_url | Return customer-portal / churn / payment-recovery / gift URLs | Read |
| send_customer_notification | Trigger a customer notification | Write |
| get_subscriptions / get_subscription | List or fetch subscriptions | Read |
| create_subscription / update_subscription | Create or edit a subscription | Write |
| skip_subscription | Skip a subscription charge | Write |
| cancel_subscription / activate_subscription | Cancel or reactivate a subscription | Write |
| set_subscription_next_charge | Reschedule the next charge date | Write |
| change_subscription_address | Reassign a subscription's shipping address | Write |
| skip_gift_subscription_charge | Skip a gift subscription's charge | Write |
| bulk_create_subscriptions / bulk_update_subscriptions | Batch create/edit subscriptions | Write |
| get_addresses / create_address / update_address / delete_address | List, add, edit, or remove addresses | Read/Write |
| apply_discount_to_address / remove_discount_from_address | Attach or remove a discount on an address | Write |
| merge_addresses / skip_address_charge | Merge duplicate addresses / skip an address's charge | Write |
| get_payment_methods / update_payment_method | List or edit payment methods | Read/Write |
| get_products / search_products / get_plans / get_plan | Browse the product and plan catalog | Read |
| get_orders / get_order | List or fetch orders | Read |
| get_charges / get_charge | List or fetch charges | Read |
| apply_discount_to_charge / remove_discount_from_charge | Attach or remove a discount on a charge | Write |
| skip_charge / unskip_charge / process_charge / reschedule_charge | Skip, restore, process, or reschedule a charge | Write |
| get_onetimes / get_onetime | List or fetch one-time products on a subscription | Read |
The README's tool tables (README.md:716-717, README.md:720) also list swap_subscription and unskip_subscription, but per the source read neither appears as a registered tool name in src/tools/*.js, so they're left off the table above; the source's actual reschedule tool is set_subscription_next_charge, included above under its source-confirmed name rather than the README's set_subscription_next_charge_date.
03 Install and auth: stdio transport, admin token to customer session
Recharge-Storefront-API-MCP runs over stdio transport. The install path, taken verbatim from the project's record, is:
clone + node; RECHARGE_ADMIN_API_TOKEN in .envAuthentication is two-tiered — a pattern not found elsewhere in comparable Recharge tooling: an admin API token (RECHARGE_ADMIN_API_TOKEN) is exchanged for a per-customer storefront session token (st_…) via create_customer_session_by_id, implemented at src/recharge-client.js:785-811. Every subsequent call in that session is scoped to the one customer whose token was minted — the server is Storefront-API-only and deliberately cannot perform merchant-wide admin operations.
04 What the source shows: the README's 87 tools vs the source's 77
This is the page's reason to exist: the public record and source read on 2026-08-31 goes past the README's own tool tables and into the registration code. The README organizes its 87 claimed tools into 16 categories (README.md:49-66). The aggregator at src/tools/index.js:5-19 imports exactly 15 modules, spread into the exported tool set at src/tools/index.js:21-36, and a count of name: registrations across those 15 files totals 77. The gap is the entire "Authentication (8 tools)" category documented at README.md:65 and README.md:805-816 — login_shopify_app_proxy, login_with_shopify_storefront, login_with_shopify_customer_account, send_passwordless_code, validate_passwordless_code, send_passwordless_code_app_proxy, validate_passwordless_code_app_proxy, and login_customer_portal. None of these eight names appears anywhere in the source: there is no auth-tools.js file in src/tools/, no import for one, and no registration.
The session cache has its own quiet gap. createCustomerSessionById returns response.customer_session and stores only its token; any expiry the Recharge API itself reports is discarded. The stored record is token/email/createdAt/lastUsed with no expiry field (src/utils/session-cache.js:9-10, :52-57), and the only eviction is a blanket 4-hour age sweep called from src/recharge-client.js:204-206 (this.sessionCache.clearExpiredSessions(240)), which compares only createdAt (src/utils/session-cache.js:179-196). The README states, at README.md:84, that "old sessions (4+ hours) automatically purged to prevent stale tokens" — true as far as it goes, but it doesn't mention that the API's own expiry value is never consulted.
A related function, clearSessionsForDomain, can't do what its name promises: sessions are never tagged with which store they belong to, so per the in-source comment at src/utils/session-cache.js:160-172 ("Since we don't store domain info with sessions, we clear all sessions"), calling it wipes the entire cache rather than one store's sessions.
05 Quirks, gaps and the honest verdict
- Unproven maintainer base — 2 stars and 3 forks as of 2026-08-31; this is a small, single-maintainer community project, not a vetted integration.
- README overstates its own tool count — 87 tools claimed across 16 categories, 77 registered across 15 modules; the "Authentication" category doesn't exist in code at all.
- Session expiry is locally invented, not API-derived — the 4-hour purge sweep ignores whatever expiry the Recharge API itself returns for a session token.
- Domain-scoped cache clearing is a no-op by another name —
clearSessionsForDomainclears every cached session, not one store's. - Storefront-only by design — every call is scoped to a single customer session; there is no merchant-wide admin path through this server.
The verdict: use Recharge-Storefront-API-MCP for scoped, per-customer storefront actions — subscription skip/swap/cancel, address and payment-method edits — not as an admin-wide or production-hardened integration. It's a 2-star community project whose README overstates its own tool count by ten and documents a phantom Authentication category with no source, import, or registration anywhere in the repo. Unless you need merchant-wide admin operations or a first-party-supported integration — then there currently isn't one to reach for; Recharge has shipped no MCP server or MCP documentation of its own as of 2026-08-31.
07 Frequently asked questions
- Does Recharge have an official MCP server?
- No. As of the public record and source read on 2026-08-31, getrecharge.com and developer.rechargepayments.com carry REST API documentation only, with no mention of MCP or the Model Context Protocol.
- How many tools does Recharge-Storefront-API-MCP actually have?
- The source registers 77 tools across 15 imported modules (src/tools/index.js:5-19, :21-36), not the 87 across 16 categories its README claims.
- What happened to the README's Authentication category?
- It lists 8 tools (README.md:805-816) including login_shopify_app_proxy and send_passwordless_code, but none of them exist in src/tools/ — there's no file, no import, and no registration for any of the eight.
- How does authentication work in this server?
- An admin API token (RECHARGE_ADMIN_API_TOKEN) is exchanged for a per-customer storefront session token (st_…) via create_customer_session_by_id (src/recharge-client.js:785-811); every call in that session is scoped to that one customer.
- Can this server perform merchant-wide admin operations?
- No. It wraps the Storefront API only and is deliberately scoped to per-customer actions, with no merchant-wide admin path.