# Recharge setup for PopMCP

You paste one Recharge Admin API token from the merchant portal into PopMCP. The token belongs to one store, so the connection is locked to that store.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.rechargeapps.com
- Credentials screen: https://admin.rechargeapps.com/admin/login
- Provider docs: https://docs.getrecharge.com/docs/recharge-api-key

## Before you begin

- The Recharge store owner's login, or a staff account the owner has given access to the API Tokens page. By default only store owners can see API tokens.
- Any Recharge plan for the core subscription, customer, charge and order tools. Recharge reserves some permissions for specific plans, such as Pro or Pro + Retain, and the Checkouts endpoint needs a Pro or Custom license.
- A decision on what the AI may change: Read access for a look-only connection, Read and Write access for the resources it should edit

## Get your credentials

### 1. Open API tokens

Sign in to the Recharge merchant portal, open Tools & apps and click API tokens.

Screen: https://admin.rechargeapps.com/admin/login

### 2. Name the token

Click Create an API Token. In the Details fields, enter a name such as `PopMCP` and a contact email. Recharge uses the email to reach you if there is a problem with the token.

Screen: https://admin.rechargeapps.com/admin/login

### 3. Set permissions per resource, then save

For each resource choose No access, Read access or Read and Write access. Give Read and Write access to what the AI should change (for example subscriptions, customers and orders), Read access to the rest, and include Read access to the store so PopMCP can show its name. The only permission PopMCP never needs is External Tokens. Click Save.

Screen: https://admin.rechargeapps.com/admin/login

### 4. Copy the token

Copy the token value Recharge shows for the saved token.

Screen: https://admin.rechargeapps.com/admin/login

### 5. Paste the token into PopMCP

In PopMCP, paste the token into Admin API token and click Connect Recharge. PopMCP reads the token's permissions and your store's name, currency, time zone and checkout platform.

## Fields PopMCP asks for

- Admin API token (apiToken) [required]: In Recharge: Tools & apps → API tokens → Create an API Token (not the Storefront token). Name it, set Read and Write access for what the AI may change (Read access for a read-only MCP), include Store read access so we can show your store name, then Save and copy the token. Stored encrypted and used only on our servers.

## Verify

PopMCP shows Recharge as Verified under your store name (or `Recharge (<token name>)` when the token lacks store read access). Asking the AI how many active subscribers you have returns a real count.

## Troubleshooting

### That's a Storefront API token (it starts with strfnt_)

Cause: The token came from Create a Storefront API token. Storefront tokens are customer-scoped and cannot call the Admin API.

Fix: Go back to Tools & apps, API tokens and use Create an API Token instead.

### Recharge didn't accept this API token

Cause: Recharge answered 401 `bad authentication`: the token was copied incompletely or has been deleted.

Fix: Copy the token again from Tools & apps, API tokens, or create a new Admin API token, and reconnect.

### Recharge refused this API token

Cause: Recharge answered 403: the token was deleted, or Recharge is no longer installed on the store.

Fix: Check Recharge is installed, then create a new Admin API token and reconnect.

### A tool fails with a permission error while others work

Cause: The token lacks that resource's permission, for example write_orders for skip_charge or write_payment_methods for refund_charge.

Fix: Raise that resource to Read and Write access on the token in Tools & apps, API tokens. The connection profile lists the token's scopes.

### You cannot see API tokens under Tools & apps

Cause: By default only the store owner can view and access API tokens.

Fix: Sign in as the store owner, or ask the owner to give your staff account access to the API Tokens page.

### Charges older than 90 days are missing

Cause: Since March 19, 2025, Recharge no longer returns processed charges older than 90 days from its charge endpoints.

Fix: Ask the AI to use orders for billing history. Older charge data is still in the merchant portal and its exports.

### Error 429 - Too many requests

Cause: The token's request bucket (40 calls, draining at 2 a second) is full.

Fix: Wait a few seconds and retry. PopMCP retries 429s automatically; for bulk changes, use Recharge's async batch tools.

---

Source: https://www.docs.popmcp.com/docs/integrations/recharge/