Stripe

Overview

Proxy Stripe's hosted MCP server so AI agents can work with customers, payments, subscriptions, invoices, and the broader Stripe API through stackgate.ai. Tools are mirrored dynamically from https://mcp.stripe.com, including meta tools such as stripe_api_read and stripe_api_write.

This is separate from stackgate.ai subscription billing (Cashier). Connecting Stripe here uses your Stripe account credentials, not the platform's billing keys.

You can connect multiple Stripe accounts (for example one test and one live) under the same integration. AI clients always use the default connection you select in My Integrations.

Prerequisites

• A Stripe account with MCP access enabled (sandbox and live are managed separately)
• A stackgate.ai account

Getting credentials

Option A — OAuth (recommended)

1. Open My Integrations → Stripe in stackgate.ai.
2. Click Activate, then Connect Stripe.
3. Enter an account name and choose the Stripe environment (test or live).
4. Complete Stripe's MCP OAuth consent screen.
5. To add another account, use Connect another Stripe account and repeat.
6. Set the default connection on the Stripe integration page — that token is used for /mcp/stripe and gateway stripe__* tools.
7. Optionally open Advanced to set a Connect Stripe-Account id (acct_…) on the default connection.

You can revoke OAuth sessions later under Stripe user settings → OAuth sessions.

Option B — Restricted API key

1. In the Stripe Dashboard → API keys, create a Restricted API key (rk_…) with only the permissions your agents need.
2. On the Stripe integration page, use Add Restricted API key, enter a name, choose test or live, and paste the key.
3. Set that connection as default if you want MCP calls to use it.

Prefer Restricted API keys over secret keys (sk_…).

Using with AI clients

• Dedicated endpoint: POST /mcp/stripe
• Private gateway: stripe__* namespaced tools (mirrored from upstream)
• Tools always run against the default Stripe connection (no connection_id tool argument)
• Run refresh_tools after connect (or after Stripe updates tools) to sync the latest upstream tool list

Upstream capabilities include API discovery (stripe_api_search, stripe_api_details), generic read/write (stripe_api_read, stripe_api_write), resource search, documentation search, refunds, reports, and more. See Stripe MCP documentation.

Troubleshooting

• MCP access denied — an administrator must enable MCP under Dashboard → Settings → MCP for the correct mode (sandbox vs live).
• Empty tool list — call refresh_tools after connect; confirm your token or RAK still has permissions.
• OAuth failed / token expired — reconnect that Stripe connection from My Integrations, or add a Restricted API key. Dynamic client registration must use scope mcp (not mcp:use).
• Wrong account data — confirm the default connection is the account you intend (test vs live).
• Rate limits (429) — Stripe enforces account rate limits; retry with backoff or reduce write volume.
• Wrong Stripe account — hub billing keys (STRIPE_KEY / Cashier) are not used here; reconnect the merchant account you intend to query.
• Connect platforms — OAuth is not used for connected-account calls; use a platform Restricted API key with Connect permissions and set Advanced → Connected account ID on the default connection.