Best for
- Teams that need Stripe capabilities in AI applications or agents
- Developers building Stripe products with MCP, LLM, or agent frameworks
S
Stripe MCP
Official
Connect AI applications and agents to Stripe.
- Category
- Other #179 of 230
- Stars
- ★ 2.0k Very popular
- Transport
- Streamable HTTP
- Runtime
- Hosted (no local runtime)
- Credentials
- API key / credential required
- License
- MIT
- Last commit
45FMRS · D
An official Stripe remote MCP server for developers who want to expose Stripe customer, product, and payment capabilities to AI applications and agents. The source does not provide canonical tool identifiers, a client compatibility list, or detailed permission scopes.
Strongest · Setup experience 10/20 Weakest · Reliability 8/20
Why each score
- Reliability 8/20
- The manifest declares a streamable-HTTP remote endpoint and an MCP server version, while the README mentions OAuth, making initialization and tool-list access plausible. However, the supplied material contains no source code, CI, committed tests, tool definitions, or error-handling evidence, so handshake behavior, tool fidelity, and dependency control are unverified. The score is conservative and remains below the static-review cap of 12.
- Security and permissions 9/20
- The README states that the remote server provides secure client access through OAuth, and the endpoint is scoped to Stripe's MCP service, showing a basic authentication boundary. There is no evidence for OAuth scopes, least privilege, data flows, tenant isolation, sensitive-data handling, side-effect disclosure, or confirmation for payment-related operations. Those omissions materially reduce the score, although no red-line behavior is evidenced in the supplied material.
- Maintenance 10/20
- The repository is not archived, uses the MIT license, and the manifest reports version 0.2.4, supporting basic ownership, licensing, and versioning. The supplied material does not show commit history, release cadence, CI, dependency-update practice, issue response, vulnerability disclosure, or a security contact. The issue count alone is not evidence of sustained maintenance, so the score is moderate rather than high.
- Documentation 8/20
- The README describes the project, remote MCP endpoint, and OAuth concept, and provides installation commands for several clients or plugin ecosystems with links to further documentation. It does not provide reviewable tool parameters, permission scopes, limits, costs, failure behavior, troubleshooting, or payment-risk guidance. Linked content is not treated as evidence here, so documentation completeness is limited.
- Setup experience 10/20
- The manifest supplies a remote streamable-HTTP URL, the README mentions OAuth, and commands are listed for Claude Code, Codex, Cursor, and Grok Build, indicating entry points for mainstream clients. There is no concrete MCP client configuration example, detailed authentication flow, compatibility matrix, or connection verification step; manual setup also depends on an external command. The path is plausible but incomplete.
Static review · not runListed 2026-07-29
Read the FMRS scoring method →Fit and risk
What it can accessUses the networkChanges third-party account data
Not for
- Applications with no Stripe integration requirement
- Clients limited to local stdio or SSE and unable to use Streamable HTTP
- Clients unable to complete OAuth access
Required permissions
- The MCP client must use OAuth to access the remote server
- Actual Stripe resource permissions depend on the connection and authorization scope; the source does not provide a detailed permission list
Risks and side effects
- An AI agent may perform Stripe-related actions on a user's behalf, so authorization scope and results should be reviewed
- The remote server depends on network connectivity and OAuth authorization
- The source does not specify individual tools or the permission boundary of each operation
Setup
Before you start
Runtime：Hosted (no local runtime)
Connect an MCP client that supports Streamable HTTP and OAuth to https://mcp.stripe.com. Refer to Stripe's MCP documentation for the client-specific connection procedure.
Check that it works
Connect your MCP client to https://mcp.stripe.com via OAuth; once connected, Stripe tools for customers, products, and payments should appear in the client's tool list, confirming the connection works.
Troubleshooting
- Confirm that the client supports Streamable HTTP
- Confirm the server URL is https://mcp.stripe.com
- Check OAuth sign-in, authorization, and token status
- If connection issues persist, consult Stripe's MCP connection documentation
Things to try
Once connected, you can ask your AI assistant things like:
- List the customers in my Stripe account.
- Create a new Stripe product with a price.
- Check the status of my recent payments.
- Create an invoice for a specific customer.
Use cases
Give AI applications or agents access to Stripe customer, product, and payment capabilities
Build AI-powered products and businesses on Stripe
Use Stripe in MCP-based agent workflows
Overview
Stripe-hosted remote MCP server for integrating with Stripe capabilities including customers, products, payments, and more. It is exposed over Streamable HTTP and supports secure MCP client access through OAuth.
Similar servers
Hevy MCP
77 · B
Manage your Hevy workout data from AI assistants via MCP.
Firecrawl MCP Server
75 · B
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
BioMCP
75 · B
One binary. One grammar. Evidence from the biomedical sources you already trust.
Compartment
75 · B
Encrypted, fully offline long-term memory for AI agents
Source revision 24947f1632ee Data synced 2026-10-19 Read the FMRS scoring method