Stripe MCP Server (Official)

Stripe's official MCP server (part of the Stripe Agent Toolkit) giving agents the ability to create payment links, manage customers, handle subscriptions, retrieve transaction data, and automate billing workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Other stripe mcp official payments billing invoices subscriptions checkout

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

100

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Restricted API keys with per-resource, per-operation permissions. PCI DSS Level 1 certified. Never pass raw card numbers — use Stripe.js/Elements on frontend. Audit logs available in Stripe Dashboard. Radar for fraud detection built-in.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

Your agent needs to perform Stripe billing operations — creating charges, managing customers, handling subscriptions. Official server means Stripe-maintained tool definitions that stay current with the API.

Avoid When

You need webhook-driven event processing — that's not what MCP is for. Use Stripe webhooks + your own handler for event-driven flows.

Use Cases

• Agents creating payment links and checkout sessions on demand
• Automated invoice generation and subscription management
• Customer lookup and account management via natural language
• Refund processing and dispute management automation
• Revenue analytics and transaction reporting via agents

Not For

• PCI DSS card data handling — never pass raw card numbers through MCP
• High-frequency financial transaction processing (use Stripe's event-driven webhooks instead)
• Complex multi-party marketplace payouts at scale

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Yes

Webhooks

Authentication

Methods: api_key

OAuth: No Scopes: Yes

Stripe restricted API keys with specific permission scopes. Use restricted keys (not secret keys) for agents — grant only the permissions needed (e.g., write:payment_links, read:customers). Never use live secret keys in agent configs without restricted key isolation.

Pricing

Model: open_source

Free tier: Yes

Requires CC: No

MCP server is free/MIT. Stripe API itself charges 2.9% + $0.30 per successful card charge. No API call fees. Test mode is completely free.

Agent Metadata

Pagination

cursor

Idempotent

Full

Retry Guidance

Documented

Known Gotchas

⚠ CRITICAL: Use test mode (sk_test_...) until thoroughly tested — live mode charges real money
⚠ Restricted API keys are essential — never give agents your full secret key
⚠ Idempotency keys are agent's responsibility — the MCP server may not auto-generate them
⚠ Customer ID vs email — agents should look up customer by email before creating to avoid duplicates
⚠ Stripe objects use IDs (cus_xxx, pi_xxx) — agents must track these across workflow steps
⚠ Rate limits: 100 read, 100 write requests/second — sufficient for most agent workflows

Alternatives

stripe-api paddle-api lemon-squeezy-api

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Stripe MCP Server (Official).

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.