About
Stripe's official MCP server lets AI agents operate the Stripe API in natural language — create payment links, query balances and transactions, issue invoices, handle refunds and more; a remote OAuth endpoint is also hosted at mcp.stripe.com.
Our Verdict
Stripe MCP brings payments capabilities to the MCP ecosystem. Its GitHub popularity reflects community trust, and the standardized protocol ensures broad compatibility across AI clients.
Pricing
Use Cases
- Integrating payments capabilities into AI agent workflows
- Building custom AI-powered tools with Stripe MCP
- Enhancing AI agent functionality with standardized MCP access
Pros
- Stripe MCP provides standardized MCP protocol access
- Open source with 1,715 GitHub stars
- Active development and community support
Cons
- Requires MCP-compatible client (Claude, Cursor, etc.)
- Setup complexity varies by client
- Some features may depend on client capabilities
Installation
npx -y @stripe/mcpFrequently Asked Questions
What can an agent do with Stripe MCP?
It lets an AI agent handle payment operations in natural language: create payment links and customers, query balances and transactions, issue invoices, start refunds, manage products and prices, and more — ideal for embedding Stripe into coding or ops workflows.
Should I use the local stdio server or the mcp.stripe.com remote endpoint?
The local npx -y @stripe/mcp runs with a restricted API key and suits scripting and self-hosting; mcp.stripe.com uses OAuth for safer access without storing keys locally. Prefer remote OAuth for production and local for flexible dev/testing.
Is Stripe MCP safe? Could it charge money by mistake?
Use a Restricted API key scoped to only the capabilities you need, and test under test-mode keys first; combined with your client's tool-call confirmation, this effectively prevents accidental operations on real funds.