Stripe

Name: Stripe MCP Server
Availability: InStock
Author: Stripe

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Finance23 tools

Read customers, invoices, subscriptions and disputes, and issue refunds, from your AI assistant. Anthropic's snapshot names 23 tools; Stripe's current docs list 11, four of them dispatchers over 115 API methods.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Stripe via MCP

https://mcp.stripe.com

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Stripe once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Stripe Tools & Capabilities (23)

search_documentation

get_stripe_account_info

create_customer

list_customers

create_product

list_products

create_price

list_prices

create_payment_link

create_invoice

list_invoices

create_invoice_item

finalize_invoice

retrieve_balance

create_refund

list_payment_intents

list_subscriptions

update_subscription

cancel_subscription

list_coupons

create_coupon

list_disputes

update_dispute

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The connector is in public preview. Stripe badges its MCP documentation page Public preview. That badge appears in the rendered page and is dropped from the Markdown version, so a machine-read of the docs alone would miss it.
Anthropic's tool list is stale, not merely incomplete. Its 23 names match a version: 0.1.0 manifest in Stripe's repository whose tool array has not been edited since October 2025. Stripe's current documentation lists 11 tools, and only two names appear on both lists. Check your own client's tool list rather than either published one.
Counting tools does not measure capability. Four of the 11 documented tools are dispatchers. stripe_api_write reaches any POST, PATCH, PUT or DELETE method on Stripe's published allowlist, of which 27 write.
Stripe's own two descriptions of that allowlist are not identical. The tool table says stripe_api_write writes with any method of those verbs, while the section below it enumerates 115 specific methods. We treated the enumerated list as the boundary, because it is the specific claim, but a reader depending on an endpoint's absence should verify it in their own client.
A refund cannot be reversed through the connector. Stripe states that only Dashboard cancellations are currently supported for card refunds, and that a refund must not have been processed as a charge reversal to be cancellable at all. The cancel-refund API method is not on the connector's allowlist.
Refunds are not free and not always immediate. Stripe's processing fees from the original transaction are not returned. If your available balance is short, Stripe holds a card refund as pending and refunds for other payment method types fail.
finalize_invoice is not a bookkeeping step. Stripe's invoice object defaults collection_method to charging automatically, which Stripe describes as attempting to pay the invoice using the customer's default source. The invoice pay and send endpoints are both absent from the connector's allowlist, but finalising a draft against a customer with a stored payment method can still start a charge.
create_refund can email your customer. Stripe sends a refund notification when the charge was created on a customer record with a stored email address and refund emails are enabled in the Dashboard.
One endpoint serves both environments. Test and live share https://mcp.stripe.com. Stripe isolates the objects and gates access per environment, which Razorpay does not document, but two configured connectors still look identical in a client's UI.
There is no read-only OAuth grant. The authorization server advertises one scope, mcp. Read-only is reachable only by using a restricted API key with per-resource permissions instead of OAuth, which trades a revocable session for a long-lived secret.
The tool list depends on your credential. Stripe's agent toolkit documents that restricted API key permissions now control which tools are available, so this page's tables cannot predict what your client will show.
Tool parameters and safety annotations were not readable. The endpoint returned HTTP 401 to an anonymous initialize on 2026-08-18. We read no readOnlyHint or destructiveHint off the wire and make no claim about them. No tool was called and no OAuth flow was started.
Stripe recommends human confirmation. Its MCP page advises enabling human confirmation of tools and warns about prompt injection when combining the Stripe server with others.
get_balance_summary is itself a preview. Stripe marks that tool's Treasury row public preview in its own table.

Frequently asked questions

It can refund a payment, and it can finalise an invoice. Stripe documents a create_refund tool, and refunds draw on your available Stripe balance. No payout, transfer, top-up or charge-creation method appears in the 115 API methods Stripe lists as reachable, even though all of those endpoints exist in the Stripe API.

By authorising in the environment you want, not by changing the URL. Stripe documents a single endpoint for both, and says MCP access is managed separately between sandbox and live mode. Sandbox and live objects are fully isolated from each other, and OAuth sessions are scoped to the account and environment you were viewing when you authorised.

An administrator. Stripe states that administrators can enable MCP access in the Dashboard, and manages that access separately for sandbox and live mode. Revoking another user's MCP session also needs a role with permission to manage team members and OAuth sessions, which Stripe gives the Administrator role as its example.

Yes. Stripe documents passing a restricted API key as a bearer token in the Authorization header for clients that do not support OAuth, and for autonomous agents. Stripe recommends restricted keys over secret keys whenever a key is given to an AI agent, because each key carries per-resource Read, Write or None permissions you choose yourself.

Yes, but not over OAuth. Stripe states Connect platforms can make MCP calls as their connected accounts using restricted access keys with the appropriate Connect permissions, and that OAuth cannot be used for this. The connected account is selected by passing a Stripe-Account header alongside the key in your client configuration.

Stripe publishes no MCP-specific numbers, and its general API limits apply. Stripe documents a global limit of 100 requests per second in live mode and 25 per second in a sandbox, measured per account, with individual endpoints capped at 25 per second unless noted. Exceeding a limit returns HTTP 429.