PAYMENTS INTEGRATION / Stripe
Stripe MCP
Lets an assistant discover Stripe APIs, inspect account data and perform authorized API operations with additional confirmation for selected sensitive writes.
“Stripe MCP server”
01 / THE REASONING
Why this made the selection.
- Provides API discovery and documentation alongside account operations, useful while implementing an integration.
- Documents environment-specific grants and extra confirmation for selected high-impact operations.
- Stripe’s documentation describes an MCP server whose tools call the Stripe API and search Stripe’s documentation and support articles for the account tied to the OAuth session or API key.
- The official registry entry names com.stripe/mcp, and the docs say OAuth is not supported when the agent acts for connected accounts.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://docs.stripe.com/mcp (setup, access and capability sections)
- Official MCP Registry publisher entry: endpoint matched against official setup documentation
- https://docs.stripe.com/mcp
- https://registry.modelcontextprotocol.io/v0.1/servers?search=stripe&version=latest&limit=100
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- stripe_api_write covers POST/PATCH/PUT/DELETE operations within the authorized account.
- The companion Stripe AI toolkit licence does not establish the hosted MCP implementation’s licence.
- The docs page says Stripe MCP tools talk to the Stripe API and the Stripe knowledge base, on the account associated with the OAuth session or API key.
- OAuth opens Stripe’s consent page for ordinary clients, but the page says MCP does not support OAuth when acting for connected accounts.
- Beginning October 31, 2026, the server no longer accepts full-access secret keys or restricted API keys without the Agent tag. The registry row for com.stripe/mcp describes tools for customers, products, payments, and more.
- Revoking an OAuth session is scoped to the account or organization and live/sandbox environment currently being viewed in the Dashboard.
Not established by this review
- Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add https://mcp.stripe.com using the official client instructions, or let Stripe’s agent plugin (stripe agent setup from the Stripe CLI) configure it.
- Authorize the intended sandbox/account and environment permissions; review human-confirmation links for sensitive writes.
Before you start
- A Stripe account and permission for the intended environment; an OAuth-capable client or supported API-key setup.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"stripe": {
"url": "https://mcp.stripe.com"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.stripe.com/mcp
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample
https://registry.modelcontextprotocol.io/v0.1/servers?search=stripe&version=latest&limit=100
Supports: transports