Specific implementation researched
Stripe MCP
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Stripe
- Publisher
- Stripe
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- OAuth or an agent API key as a bearer token.
- Read capabilities
- Read Stripe API data · Search documentation and support articles · Retrieve account information and analytics
- Write capabilities
- Call authorized Stripe API methods to make changes
- Permissions
- Permissions are separate for each live account or sandbox; certain sensitive actions require additional confirmation in Stripe.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- Public preview. From December 2026, Stripe MCP will no longer accept full-access secret keys or restricted keys without an agent tag.
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Not verified | — |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
Model Context Protocol (MCP) | Stripe-Documentation ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.stripe.com