Customer and product context
Expose Stripe customer and product operations through MCP tools.
Documentation ↗MCP server / payments / source-linked
Stripe MCP
Stripe MCP connects compatible AI clients to Stripe’s hosted tools at mcp.stripe.com through OAuth, and Stripe also publishes a local package for restricted-key deployments. The integration covers customers, products, payments, and related Stripe workflows. Tool availability is permissioned by a Restricted API Key in local/toolkit paths; payment mutations require human review.
Before you choose.
Identify the implementation and the job it supports.
Stripe MCP connects compatible AI clients to Stripe’s hosted tools at mcp.stripe.com through OAuth, and Stripe also publishes a local package for restricted-key deployments. The integration covers customers, products, payments, and related Stripe workflows. Tool availability is permissioned by a Restricted API Key in local/toolkit paths; payment mutations require human review.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Remote Streamable HTTP; local stdio package is available
- Authentication
- Hosted OAuth; local deployment uses a Stripe Restricted API Key (RAK).
For hosted use, connect the official endpoint through a supported client and authorize. For local use, run @stripe/mcp with a restricted key and keep it outside source control.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
npx -y @stripe/mcp --api-key=YOUR_RESTRICTED_KEYWhat it actually exposes.
Concrete capabilities with maintainer sources.
Payment workflows
Support payment-related tools including payment links and other account operations, subject to key permissions.
Documentation ↗Permission-aware toolkit
Stripe’s current toolkit fetches tools from mcp.stripe.com and uses RAK permissions rather than the older actions configuration.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Payment-safe support workflow
Suggested evaluation, not an observed test result.
- Connect a test or restricted Stripe account with only read tools needed for the task.
- Ask the agent to inspect customer/product context and draft the intended change.
- Require explicit human confirmation before refunds, charges, or account mutations.
What to inspect: A reviewed payment operation plan with a narrow permission boundary. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Stripe’s current migration notes say network access to mcp.stripe.com is required; there is no local fallback for the hosted toolkit connection.
Boundary reference ↗A secret key or broad RAK can enable consequential writes; this is a security inference from the documented payment/customer tools and permission model.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A reviewed payment operation plan with a narrow permission boundary. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| HubSpot MCP | Choose for CRM records, deals, and marketing activity instead of payment primitives. | HubSpot is CRM-centric; Stripe is the correct system of record for billing and payments. Documentation ↗ |
| Composio MCP | Choose when you need to combine Stripe with many other SaaS toolkits under one session policy. | Adds an integration layer and separate credentials; Stripe MCP is more direct. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Does hosted Stripe MCP use OAuth?
Yes. Stripe’s registry documents a hosted endpoint at https://mcp.stripe.com with OAuth access.
Documentation ↗
How do I restrict tools locally?
Create a Restricted API Key with only the permissions required; current toolkit configuration no longer uses the old actions field.
Documentation ↗
Source trail.
Maintainer documentation used in this record.