Stripe MCP server: connect AI agents to Stripe from the EU

Stripe is a payments platform used by many online businesses in Europe to accept cards and other payment methods, run subscriptions and send invoices. Stripe, Inc. is based in South San Francisco, with its European entity in Dublin.

Stripe's official MCP server runs at https://mcp.stripe.com. It authenticates with OAuth, which lets an account owner grant access through a consent screen, or with an API key sent as a Bearer token. Stripe recommends restricted API keys so that each agent only has the permissions it needs. The tools available depend on what the key or OAuth grant allows.

A support agent can answer "why was I charged twice?" by finding the customer, listing recent payments and explaining what happened, then proposing a refund for a person to approve. A finance agent can list failed payments and open disputes each morning and prepare a summary.

Sales teams can have an agent create a customer, an invoice with the agreed line items and a payment link after a deal closes. Developers can ask the agent questions about Stripe's API and get answers drawn from Stripe's own documentation.

Add the Stripe connector on inference.eu and either sign in with Stripe through OAuth or paste a restricted API key. With a restricted key, choose read access for objects the agent only needs to see, and write access only where it must act, such as invoices or refunds.

Start in a Stripe sandbox or test mode to see how the agent behaves before connecting live data. Keys and tokens are stored encrypted in the EU and used only by the agents you allow. You can roll or delete the key in the Stripe Dashboard at any time.

Payment data is fetched from Stripe's own MCP server and API, so it stays with Stripe as it does for your other Stripe integrations. Stripe serves European customers through Stripe Payments Europe in Ireland.

On inference.eu, the model that reads your payment data runs in EU data centres, and your Stripe credentials are stored encrypted in the EU. Stripe data includes customer names, emails and billing addresses. Card numbers are not exposed through the API. Give agents only the restricted-key permissions they need and avoid connecting a full secret key.

Refunds move money, cancelled subscriptions stop revenue and finalised invoices are sent to customers. These actions are hard to reverse and directly affect customers.

On inference.eu you can let lookups and documentation searches run on their own and require a person's approval for refunds, subscription changes, invoice finalisation and dispute updates. The approval shows the customer, amount and currency, so the reviewer knows exactly what will happen. Restricted keys add a second layer: an agent without refund permission cannot refund, whatever it is asked.