---
title: "Stripe MCP server · Connect AI agents to Stripe"
description: "Connect inference.eu agents to Stripe's official MCP server to look up customers and payments, create invoices and payment links, and search Stripe docs."
canonical: "https://inference.eu/connect/stripe/"
language: "en"
---

MCP servers · Banking and payments

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

Stripe runs an official remote MCP server that lets agents work with the Stripe API and search Stripe's documentation. Agents can look up customers, payments and subscriptions, create invoices and payment links, and handle refunds. inference.eu agents connect to it with OAuth or a restricted API key.

[Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools)

1.  01Authentication: OAuth
2.  02Official server
3.  03EU data centres

## What agents can do with it

-   1

    ### Customers, payments and balance

    List and search customers, payment intents, charges, subscriptions and disputes, fetch any Stripe object by ID and read the account balance, so an agent can answer billing questions.

-   2

    ### Invoices, products and payment links

    Create customers, products and prices, create invoice items and invoices, finalise them, create coupons and generate payment links that can be sent to a customer.

-   3

    ### Refunds, subscriptions and documentation

    Create refunds, update or cancel subscriptions, update disputes with evidence, and search Stripe's own documentation and knowledge base to answer integration questions.

## What Stripe and its MCP server are

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.

## What agents can do with Stripe

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.

## Setup and authentication

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.

## Data protection and where the data goes

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.

## Approvals and safe use

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.

## Stripe

Vendor

Stripe, Inc.

Vendor based in

United States

Category

Banking and payments

Authentication

OAuth

Transport

Remote (HTTP)

Server

[Official server](https://docs.stripe.com/mcp)

Documentation

[docs.stripe.com](https://docs.stripe.com/mcp)

## Stripe: common questions

The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly.

Yes. Stripe runs its own remote MCP server at https://mcp.stripe.com, documented at docs.stripe.com/mcp. It supports OAuth and API keys sent as Bearer tokens, and also offers a tool for searching Stripe's documentation.

Look up customers, payments, subscriptions, disputes and balances, create customers, products, prices, invoices and payment links, create refunds, update or cancel subscriptions, and search Stripe's documentation, depending on the permissions granted.

OAuth lets an account owner grant access through Stripe's consent screen and revoke it later. A restricted API key lets you set read or write permission for each type of object. Both work; restricted keys give the finest control.

Add the Stripe connector on inference.eu and sign in with Stripe or paste a restricted API key. Credentials are stored encrypted in the EU and used only by the agents you allow. Testing in a sandbox first is recommended.

Only if its credentials allow it and you let it. Leave refund permission off a restricted key to rule refunds out, or keep it and require a person's approval for every refund on inference.eu, with amount and customer shown.

No. Stripe does not expose full card numbers through its API, and the MCP server works through the same API. An agent can see details such as card brand, last four digits and expiry where your key allows.

Yes. Connect the agent with a sandbox or test mode key first. It can create test customers, invoices and refunds without touching real money, so you can check its behaviour and approval rules before going live.

Stripe serves payment data from its own systems, with European customers contracting with Stripe Payments Europe in Ireland. The model on inference.eu that reads it runs in EU data centres, and your credentials are stored encrypted in the EU.

[Ask a question](https://inference.eu/contact/)

## Related

[All MCP servers](https://inference.eu/connect/#directory)

-   [MollieConnect inference.eu agents to the official Mollie MCP server. Look up payments, settlements and customers, and create payment links or subscriptions with approval.Banking and payments](https://inference.eu/connect/mollie/)
-   [AdyenConnect inference.eu agents to Adyen's official MCP server. Create payment sessions and links, handle refunds and cancels, and manage terminals and webhooks.Banking and payments](https://inference.eu/connect/adyen/)
-   [HubSpotConnect inference.eu agents to HubSpot's official remote MCP server to search, read and update contacts, companies, deals and tickets in your CRM.CRM and sales](https://inference.eu/connect/hubspot/)
-   [SalesforceConnect inference.eu agents to Salesforce Hosted MCP Servers to query and update records with each user's own permissions, sharing rules and field security.CRM and sales](https://inference.eu/connect/salesforce/)

## Move your AI workloads to EU infrastructure

Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps.

-   Reply within one working day
-   Pricing for your volume
-   DPA ready to sign
