Skip to content

Working with clients? Stay ahead of what they ask for.

Stripe

by Stripe

Financial intelligence layer for customer lookup, subscription management, payment history, and refund processing. Restricted keys enforce least-privilege access by default.

★ 1,520·14 listed tools·Released JAN 2026·MIT
npx @stripe/mcp --tools=all --api-key=$STRIPE_KEY
Share:

“The production-grade payments MCP. Restricted keys by default, scoped tool access, and the full Stripe API surface. The only payments integration worth running in production.”

Reviewed by M. Nouriel · APR 2026

INSTALL THIS SERVER

Requires authenticationStripe Restricted Key via STRIPE_SECRET_KEY env var
{ "mcpServers": { "stripe": { "command": "npx", "args": ["@stripe/mcp", "--tools=all", "--api-key=rk_test_your_key"] } } }
PrereqClaude Desktop v1.4+ . Use restricted keys only

14 SELECTED TOOLS

list_customers
List customers with optional filters
Read
get_customer
Get a customer by ID with payment methods
Read
create_customer
Create a new customer record
Write
list_charges
List charges with date and status filters
Read
get_charge
Get charge details including refund status
Read
create_refund
Create a full or partial refund
Write

OUR ASSESSMENT

Stripe's MCP server gives AI agents secure access to Stripe's payment infrastructure through a remote server at mcp.stripe.com, with OAuth and Restricted API Key controls. It covers the billing lifecycle including customer management, invoicing, subscriptions, payment links, and refunds. Developers building payment-aware AI agents and teams automating support or billing workflows on Stripe will find this the most capable official payments MCP available.

Strengths
  • First-party Stripe support with restricted key enforcement
  • Scoped tool access (enable only the tools your agent needs)
  • Covers customers, charges, subscriptions, invoices, and refunds
  • Production-tested at Stripe scale
Weaknesses
  • Restricted keys require manual setup in the Stripe dashboard
  • Complex operations (multi-currency, Connect) need additional configuration
Security Notes

Always use restricted keys (prefer these over secret keys). Scope the key to the minimum required resources (e.g., read-only for customer lookup, write for refunds). Test in Stripe test mode first.

Best For

Agents that need to look up customers, manage subscriptions, or process refunds

TECHNICAL DETAILS

Language
typescript
Transport
stdio
Clients
Claude DesktopClaude CodeCursorVS Code
License
MIT
GitHub
npm
@stripe/agent-toolkit
Last Release
v0.1.2APR 8, 2026
First Released
JAN 20, 2026

RECORDED ADOPTION METRICS

Saved directory snapshots. Record last checked MAY 3, 2026. The review date above does not refresh these figures.

// GitHub Stars
1,520
↓ 130 since previous snapshot (-7.9%)

// Recorded note1,520 stars on the stripe/agent-toolkit repo. 9 commits on main in the last 30 days. Audit (2026-05-03) corrected stored star count (1,800 → 1,520, mild downward drift).

// Recorded Weekly Downloads
12,800
↑ 1,600 since previous snapshot

// Recorded noteDownloads concentrated among fintech and SaaS teams. Weekly growth tracks with Stripe platform feature releases.

// Popularity Rank
#11
Recorded directory rank · #1 in API Integration

// Recorded note#1 in API Integration for financial services. Globally #11 reflects the specialised audience.

SOURCES & RECORDED CHECKS

These are the directory listings and check details held in this record. Client compatibility, directory listings and installation testing are separate signals. Recorded client names describe the scope of a check; they do not establish a security assessment or a recurring test schedule.

01
Discovered
Smithery
First indexed APR 24, 2026
02
Directory listings
3 directories
PulseMCP, Smithery, Glama
03
Recorded client testing
Claude Desktop + Claude Code
Check current setup against the provider documentation
04
Record last checked
MAY 3, 2026
Record date; functional retest scope may differ
// How other directories see it

The same server, 3 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4editorial1,52012.8K / wkMAY 3, 2026
PulseMCP4.3 community1,20011.6K / wkAPR 21, 2026
Smithery4.4 installs1,20013.1K installsAPR 20, 2026
Glama— unrated1,210unavailableAPR 18, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →