Stripe MCP Server
Stripe MCP Server
Connect Claude to Stripe through Stripe's official remote MCP server.
The Stripe MCP Server enables Claude to query payments, manage customers, check subscription status, and interact with your billing operations using natural language.
What Can Claude Do with the Stripe MCP Server?
The Stripe MCP Server exposes Stripe API functionality to Claude through the Model Context Protocol.
Core capabilities:
- Query Payments — Retrieve payment intent status, charge details, and transaction history
- Customer Management — View customer information, payment methods, and billing details
- Subscription Queries — Check subscription status, billing cycles, and plan details
- Invoice Access — Retrieve invoice data, payment status, and line items
- Refund Information — View refund status and transaction details
Access scope: Claude can only access Stripe resources based on your OAuth authorization or API key permissions. The integration respects Stripe's API scoping and account permissions.
How to Install the Stripe MCP Server
Stripe provides an official remote MCP server.
Preferred Connection Method: OAuth
Remote MCP endpoint: https://mcp.stripe.com
Authentication: OAuth (recommended)
Connect using your MCP client's OAuth flow. This is the preferred and most secure connection method.
Fallback: API Key for Compatibility
If your MCP client does not support OAuth, a restricted API key can be passed as an Authorization header in supported clients. This is a fallback compatibility path, not the primary recommended method.
Stripe OAuth & API Key Setup
The Stripe MCP Server supports OAuth as the preferred authentication method.
OAuth connection (Recommended):
- Your MCP client initiates connection to Stripe's remote MCP server
- You're redirected to Stripe's authorization page
- You authorize access to your Stripe account
- Stripe generates OAuth credentials
- Your MCP client stores these credentials securely
API Key fallback (for compatibility):
If your MCP client doesn't support OAuth:
- Log in to Stripe Dashboard
- Go to Developers → API keys
- Create a Restricted Key with minimal necessary permissions
- Use test mode keys (
rk_test...) during development - Configure the key in your MCP client according to its documentation
Important: OAuth is more secure than API keys. Use OAuth when your MCP client supports it.
Test mode vs Live mode:
- Test mode — Use for development (keys start with
rk_testorsk_test) - Live mode — Use for production (keys start with
rk_liveorsk_live)
Always develop and test in test mode first.
Stripe MCP Use Cases & Query Examples
Example workflows that become possible with the Stripe MCP Server.
Check Payment Status
Example prompt:
> "What's the status of payment intent pi_3ABC123?"
Claude can retrieve payment intent details and current status.
Query Recent Charges
Example prompt:
> "Show me all successful charges from the last 7 days."
Claude can list and filter charge transactions.
View Customer Information
Example prompt:
> "Show me customer details for customer ID cus_ABC123, including their payment methods."
Claude can retrieve customer data and associated payment information.
Check Subscription Status
Example prompt:
> "Is subscription sub_ABC123 active? When does it renew?"
Claude can access subscription details, billing cycles, and status.
Review Invoice Data
Example prompt:
> "Show me the most recent invoice for customer cus_ABC123."
Claude can retrieve invoice information and line items.
Note: These are example use cases. Actual capabilities depend on your OAuth permissions or API key scopes. Write operations (creating charges, refunds) require appropriate permissions and should be used with caution.
Security reminder: These capabilities apply mainly to API-key-based fallback workflows. The preferred OAuth remote MCP path provides secure, scoped access.
Stripe MCP in a Payments Ops Workflow
Stripe MCP is relevant when assistants need to inspect payment flows, billing objects, and operational revenue events.
What this shows: This screenshot uses Stripe's API docs as the real scenario reference for checkout, payment, and subscription workflows connected to AI tooling.
Why this scenario matters: It ties the page to the actual payment system surface, where assistants can help teams inspect billing flows, checkout objects, and revenue-side operations.
Typical assistant task: Inspect billing objects, reason about payment state, and support checkout or subscription operations from one assistant session.
Source: Stripe API Docs
When to Pick Stripe MCP Server vs PayPal REST APIs
This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.
| Decision Lens | This Page's MCP Path | Competitor |
|---|---|---|
| Best For | Developer-led payments teams that need programmable billing, checkout, and subscription operations. | Workflows where PayPal-native checkout preference and market familiarity are more important than developer ergonomics. |
| Where MCP Wins | Stripe MCP wins when assistant workflows need a developer-centric payment model with strong billing primitives. | |
| Tradeoff to Watch | It is not always the best fit when the practical requirement is PayPal-native checkout and its surrounding ecosystem. | |
| Choose This Path When | Choose Stripe MCP for programmable billing operations; choose PayPal APIs when PayPal preference is dominant in the workflow. | |
| Sources | ||
Frequently Asked Questions
Is the Stripe MCP Server free?
Should I use OAuth or API keys?
Can Claude process payments?
What's the difference between test and live mode?
Can Claude issue refunds?
What are Stripe's API rate limits?
How do I revoke access?
Use Stripe MCP in Verdent
Verdent provides streamlined Stripe integration with secure credential management. This is Verdent's platform-level integration flow, not the default setup path from Stripe's official documentation.
Connect your Stripe account once and access payment data across all Verdent projects without manual configuration.