Stripe MCP server

Endpoint: https://mcp.stripe.com · Authentication: Sign in with OAuth

Remote MCP server for Stripe payments, billing, customers, and developer documentation.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint in your client, start Connect or Sign in, approve the requested scopes, and return to the client. OAuth discovery finds the authorization server; client registration requirements vary by provider. Follow the provider guidance and client setup below.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.stripe.com
Live-validated endpoint: https://mcp.stripe.com/
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Not yet verified — Latest validation did not verify a transport
Declared authentication: OAuth 2.1
Detected authentication: OAuth 2.1 detected or retained from publisher evidence
Protocol lifecycle: Not yet negotiated
Authorization server: https://access.stripe.com/mcp
Category: Payments

Product documentation · Official listing documentation

More Payments MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

No app registration needed

The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.

Publisher evidence reviewed 2026-08-24.

Publisher documentation

Connect it

Live-validated endpoint: https://mcp.stripe.com/ · Not yet verified. No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.

Agent prompt for Claude Code or Codex

Add the Stripe MCP server to my MCP client configuration and verify that it works.

What it is: Remote MCP server for Stripe payments, billing, customers, and developer documentation.
Server URL: https://mcp.stripe.com/
Transport: Not yet verified (remote MCP server, no local install).
Authentication: OAuth 2.1. No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
Claude Code setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
Codex CLI setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
VS Code setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/stripe/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "stripe" in that client's MCP configuration, user scope unless I ask otherwise.
Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

Claude Code setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Codex CLI setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

Codex CLI setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "stripe": {
      "url": "https://mcp.stripe.com/"
    }
  }
}

VS Code setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

VS Code setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

Publisher evidence (reviewed 2026-08-24): https://access.stripe.com/.well-known/oauth-authorization-server/mcp

Client compatibility

Client	Status	Why
Claude Code	Partial	The endpoint transport has not been verified.
Codex	Partial	The endpoint transport has not been verified.
Cursor	Partial	The endpoint transport has not been verified.
VS Code	Partial	The endpoint transport has not been verified.
Claude	Partial	The endpoint transport has not been verified.
Claude Desktop	Partial	The endpoint transport has not been verified.
ChatGPT	Partial	The endpoint transport has not been verified.
Windsurf	Partial	The endpoint transport has not been verified. Windsurf's documentation does not state support for OAuth sign-in.
Gemini CLI	Partial	The endpoint transport has not been verified.
MCP SDK	Partial	The endpoint transport has not been verified.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

PayPal — Remote MCP server for PayPal payment-platform workflows, merchant questions, and transaction-related tasks. OAuth 2.1
Square — Calls the Square API for customers, orders, catalog items, payments, inventory, and other seller data. Requires Square OAuth. OAuth 2.1
SumUp — Calls the SumUp API for merchant accounts, checkouts, transactions, and card readers, and exposes SumUp developer documentation as resources. Requires SumUp OAuth. OAuth 2.1
Paddle — Searches and calls the Paddle Billing API, covering products, prices, customers, subscriptions, and transactions, through search and execute tools. Uses OAuth or a live Paddle API key; sandbox accounts use a separate endpoint. OAuth 2.1
Razorpay — Creates and reads Razorpay payments, orders, payment links, refunds, QR codes, settlements, and payouts. Uses OAuth, or Razorpay API keys with HTTP Basic authentication. OAuth 2.1
Mollie — Manages Mollie payments, payment links, customers, subscriptions, settlements, invoices, and webhooks. Requires Mollie sign-in through OAuth. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Stripe? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/stripe.svg)](https://mcptest.io/servers/stripe/)

HTML

<a href="https://mcptest.io/servers/stripe/"><img src="https://mcptest.io/badge/server/stripe.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/stripe.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/stripe/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 2:08 PM
Validation detail: Authentication challenge at https://mcp.stripe.com/ returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication oauth

Tool inventory

Requires authorization; inventory not observed

The catalog validator lists tools only on servers that answer without credentials. Stripe asks for OAuth 2.1 sign-in first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.