Payments

Stripe MCP Server

Stripe's remote MCP server lets an assistant work with Stripe objects such as customers, products, invoices and payment links.

What it is and why it matters

What it does

• Looks up customers, charges and subscriptions
• Creates products, prices and payment links
• Searches Stripe documentation

Best for

Finance and operations questions, and building billing flows.

How to connect it

1. In the Stripe Dashboard, create a restricted API key with read access to the resources you need, or use the sign-in method Stripe documents for your client.
2. Add Stripe's remote MCP server to your AI tool's settings using the address and authentication shown in Stripe's MCP documentation.
3. Begin in test mode and run a harmless query, such as listing recent test customers.
4. Only move to live mode after you are happy with the permissions and how the assistant behaves.

Exact commands and addresses change. Use the official documentation for the current steps.

Questions you can ask it

• Which payments failed in the last 7 days and what were the decline reasons?
• Find the customer with this email and show their recent charges and subscriptions.
• Create a payment link for the 49 euro starter product in test mode.
• How do I handle a refund for a partially shipped order? (answered from Stripe documentation)

What it cannot do

• It does not know your product margins, shipping costs or ad spend, so it cannot report profit.
• It can only act within the key's permissions.
• It is not a substitute for your accountant or Stripe's own reporting for reconciliation.

Staying safe

• Use restricted keys, never your full secret key, and keep write permissions off by default.
• Prefer test mode for anything new.
• Require human confirmation for refunds, payouts, subscription changes or anything that moves money.

Watch out for: Use a restricted key. Never connect a full-access production key to an assistant.

Frequently asked questions