Stripe MCP Server – Payments and Billing Automation
Stripe's official MCP server gives AI agents controlled access to supported Stripe API operations and Stripe's knowledge base. Use it for payment and billing workflows, account research, customer and subscription management, invoice operations, product configuration, refunds, and Stripe integration help.
Overview
Stripe's official MCP server connects compatible AI agents to supported Stripe
API tools and Stripe's knowledge base. It allows an agent to work with current
account data and perform authorized operations instead of relying only on
static model knowledge or information copied manually from the Stripe Dashboard.
What the MCP server enables
Stripe documents tools covering account and balance information, coupons,
customers, disputes, invoices, payment links, PaymentIntents, prices, products,
refunds, subscriptions, Stripe resource search, object retrieval, and Stripe
documentation search. Depending on the authenticated account and granted
permissions, an AI agent can:
- Retrieve Stripe account information and balances.
- Create or list customers, products, prices, coupons, and invoices.
- Add invoice items and finalize invoices.
- Create payment links and list PaymentIntents.
- List, update, or cancel subscriptions.
- Create refunds and review or update disputes.
- Search Stripe resources and retrieve supported Stripe objects.
- Search Stripe documentation and support knowledge.
When to use it
Use Stripe MCP when an agent needs live Stripe context or must perform a
supported payment, billing, or account-management operation. Practical
workflows include provisioning customers and subscriptions, preparing invoices,
creating product and price records, generating payment links, investigating
account balances, reviewing disputes, issuing approved refunds, and answering
implementation questions with current Stripe documentation.
Connection and authentication
Stripe hosts a remote MCP server at https://mcp.stripe.com. OAuth is the
preferred connection mechanism because it provides user-based authorization
and granular access. When a client does not support OAuth, Stripe permits a
restricted API key in the Authorization header as a Bearer token.
Stripe also provides an official local stdio server through the
@stripe/mcp@latest npm package. It reads credentials from the
STRIPE_SECRET_KEY environment variable. Although that variable retains its
documented name, Stripe recommends supplying a restricted API key with only
the permissions the agent needs.
Key considerations
Stripe MCP can perform financial and account-changing actions. Enable human
confirmation for tool calls, especially refunds, subscription cancellation,
invoice finalization, dispute changes, and any live-mode operation. Administrators
can manage MCP access separately for sandbox and live environments. Build and
test in a Stripe sandbox before using live data. Store credentials in a secret
manager or environment variable, never in source control, and use restricted
keys with the minimum necessary permissions. Stripe also warns about prompt
injection risks when its MCP server is combined with other servers.
Supported Transports
streamable_http
URL: https://mcp.stripe.com
stdio
Command: npx
Args:
-y@stripe/mcp@latest
Frequently Asked Questions
- When should an AI agent use the Stripe MCP server?
- Use it when a workflow needs current Stripe account context or supported payment and billing actions, such as managing customers and subscriptions, preparing invoices, creating products or payment links, reviewing balances and disputes, issuing approved refunds, or researching Stripe documentation.
- What does the Stripe MCP server add to an AI agent's capabilities?
- It gives the agent structured access to supported live Stripe API operations and Stripe's knowledge base, allowing it to retrieve account information, manage selected billing resources, and answer implementation questions using current Stripe documentation rather than static model knowledge alone.
- What can an AI agent access or manage through Stripe MCP?
- Depending on permissions, the agent can work with accounts, balances, customers, coupons, invoices, payment links, PaymentIntents, prices, products, refunds, subscriptions, disputes, Stripe resource search, object retrieval, and documentation search.
- How is authentication configured for the Stripe MCP server?
- The hosted server should use OAuth when the MCP client supports it. Clients without OAuth can send a restricted API key as a Bearer token. The local server reads its credential from STRIPE_SECRET_KEY; use a restricted key, store it in a secrets manager or environment variable, and grant only the permissions required by the enabled workflows.
- Which transport should be used for the Stripe MCP server?
- Use Streamable HTTP with https://mcp.stripe.com for Stripe's managed remote server and prefer OAuth authentication. Use stdio with the official @stripe/mcp package when a local process is required or the MCP client is designed for locally launched servers.