Stripe MCP permissions: full access vs restricted keys

Understand which Stripe permissions are needed for read tools, billing object creation, refunds, and subscription actions.

• Category: Accounts Integrations
• Tags: Stripe, Billing, Payments, MCP
• Updated: Jun 8, 2026

Stripe MCP lets the connected AI inspect products, prices, customers, subscriptions, invoices, payment links, checkout sessions, payment intents, coupons, and account status. Write actions stay behind separate brand toggles and dry runs.

Fastest setup

A full-access Stripe secret key works fastest because Stripe does not block individual endpoints. It is powerful, so only store it when you trust the brand workspace and need broad billing management.

Safer setup

A restricted key is safer because you can choose specific read and write permissions. If an endpoint is blocked, Best AI CEO shows the missing permission and what to add.

High-risk actions are separate

• Normal Stripe AI actions can create billing objects only when the Stripe mutation toggle is enabled.

• Refunds require the separate refunds toggle.

• Canceling, pausing, or resuming subscriptions requires the separate subscription toggle.

• All mutation tools support dry runs and write audit history.