MCP · Payments and billing · Stripe
Stripe MCP
Read Stripe documentation and account data or request permitted API actions, with separate live and sandbox authorization.
Wrong environment. A plausible request against live mode can cause an actual financial or customer-facing change.
Understand the tool
What it does.
Stripe's remote MCP server exposes documentation search and account operations to an AI host. Select the account, environment and permissions first: sandbox and live actions have different consequences.
Why use it?
Use it to investigate an integration with current documentation and account evidence. Begin with synthetic sandbox invoices. Separate observed API facts from the agent's proposed next action.
A useful fit for
- Sandbox integration work
- Billing investigations
- Stripe documentation lookup
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Explain a sandbox invoice
A developer needs to understand an invoice's state during testing.
- Confirm the sandbox and invoice identifier.
- Read the invoice and relevant documentation.
- Explain its status and the next test to perform.
Intended outputA supported diagnosis without sending an invoice or moving money.
Use case 02
Plan a subscription integration
A team needs a clear implementation outline.
- State the intended subscription behavior.
- Look up the applicable Stripe APIs.
- List the events and sandbox cases to verify.
Intended outputAn implementation checklist tied to current documentation.
A concrete starting point
Illustrative prompt: sandbox diagnosis
Authorize only the intended sandbox and permissions.
In the Stripe sandbox I select, explain the state of the invoice ID I provide. Read only the necessary objects and documentation. Do not finalize or send invoices, issue refunds, change subscriptions or move money.What this can change
Reading may expose customer information to the AI host. Write access can affect billing and real funds in live mode.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- A trusted remote MCP host and Stripe account authorization.
- An explicit sandbox or live-mode scope and the minimum necessary permissions.
- Administrator approval where the organization controls MCP access.
- Authentication
- OAuth for interactive access or a scoped agent API key for persistent agent access.
- Can read
- Authorized Stripe objects and documentation
- Can write or change
- Permitted API mutations, including consequential billing operations
- Network and data flow
- mcp.stripe.com and Stripe authentication/API services
- AI host/model provider
- Approval and control
- Keep host tool approvals enabled. Stripe documents additional human confirmation for certain writes, such as refunds; do not assume every write has that gate.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Remote MCP hosts supporting the documented OAuth or key flow
- Host/team connector policies vary
- Older full-access or non-agent key setups need migration by November 30, 2026
Costs and account requirements
Stripe product and transaction charges still apply, as may AI host costs. No universal standalone MCP fee is asserted.
Current pricing or plan information ↗Hosted service terms
No public source license for the hosted implementation is asserted; separate SDK repositories are not treated as identical. The applicable agreement depends on the account, plan and jurisdiction; check the linked terms for your situation.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Wrong environment
A plausible request against live mode can cause an actual financial or customer-facing change.
Sensitive account data
Avoid unnecessary personal data in queries and reports. Keep keys out of prompts and committed configuration.
Where it may fall short
- No account was connected and no financial operation was performed.
- This review does not validate financial calculations, API coverage or approval enforcement.
Observed behavior · 2026-10-18
Runtime and security findings.
Stripe rejected the credential-free request before initialization and provided OAuth discovery. No sandbox, account data or financial operation was exercised.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation
A missing-key error can still lead to OAuth
The endpoint returned HTTP 401 with missing_api_key and a WWW-Authenticate resource-metadata URL. That URL returned HTTP 200, advertised the mcp scope and named https://access.stripe.com/mcp as the authorization server.
In practice: Follow the supported OAuth setup rather than assuming the missing-key message requires a full-access secret key.
Documented concern
Authentication requirements are changing
Stripe's current guide sets November 30, 2026 as the migration deadline for API-key authentication. Starting in December, it says full-access secret keys and restricted keys without the Agent tag will no longer be accepted by MCP.
In practice: Use OAuth for an interactive connection or a narrowly permissioned Agent API key. Test the chosen setup in a sandbox before replacing an existing integration.
Documented concern
Confirmation covers specified actions
Stripe documents human confirmation for certain consequential write actions, including refunds and outbound payments. That is not a claim that every write requires a second confirmation.
In practice: Keep host tool approval enabled and distinguish sandbox from live mode. Review the target account, amount and operation before approving a financial action.
Version, environment and fixture
- Version or deployment
- Remote deployment version not disclosed by the observed responses
- Tested target
- https://mcp.stripe.com/
- Artifact identity
- HTTPS certificate verification enabled. Public resource-metadata body SHA-256: eb719853257ba65fa26ae77a583231363174251d597d2776d93ff27a3caa9c9a. This fingerprints the observed metadata, not the deployed server implementation.
- Environment and fixture
- Windows 11 build 26200; Python 3.12.10 urllib; OpenSSL 3.0.16.
- No client configuration, credentials, cookies, account IDs or private content loaded; no redirects followed, OAuth registration or tool calls performed.
- Observed 2026-10-19T00:47:10.969895+00:00 through 2026-10-19T00:47:20.954258+00:00 UTC.
- One request per listed check; 20-second timeout and 64-KiB response cap. Initial sandbox DNS failures were retained separately and resolved with approved network access; they are not endpoint failures.
Checks and results
2 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationMet expectation
- Method
POST https://mcp.stripe.com/; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream. Content-Type: application/json; MCP-Protocol-Version: 2025-03-26; body: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"IonBin-account-free-evaluation","version":"1.0.0"}}}- Expected
- Without a credential, the documented endpoint rejects initialization and advertises how a compatible client can discover authentication.
- Observed
- HTTP 401 at 2026-10-19T00:47:10.969895+00:00. WWW-Authenticate: Bearer; resource_metadata=https://mcp.stripe.com/.well-known/oauth-protected-resource. Parsed error indicator: missing_api_key.
Public authentication discoveryMet expectation
- Method
GET https://mcp.stripe.com/.well-known/oauth-protected-resource; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream.- Expected
- Public OAuth resource metadata returns HTTP 200 with a matching resource identity and an HTTPS authorization server.
- Observed
- HTTP 200 at 2026-10-19T00:47:20.954258+00:00; Content-Type: application/json. Resource: https://mcp.stripe.com. 1 supported scopes: mcp. Authorization server: https://access.stripe.com/mcp.
Practical caveats
- OAuth sessions can cover multiple accounts or environments. Revocation applies to the account/organization and environment being viewed, so verify the whole intended scope.
- Connected-account use has a distinct API-key and Stripe-Account setup; this unauthenticated probe did not test it.
What this evaluation does not establish
- OAuth or Agent API-key authentication, sandbox/live separation, connected-account authorization and revocation.
- Actual tools, approval-token flows, refunds, payments, data access or prompt-injection resistance.
- The announced December authentication change; this is an October observation and a documented future requirement.
- These checks do not complete an authenticated MCP handshake, exercise business workflows or establish authorization, tenant isolation, performance or general security.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
Clear sandbox use cases and documented access controls make it valuable. Financial consequences place it after lower-impact starting points.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Current server tools
- Agent-key migration
- confirmation behavior
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official server and approvals ↗docs.stripe.com
- API and agent keys ↗docs.stripe.com
- Stripe pricing ↗stripe.com
- Service terms or terms index; account applicability not evaluated ↗stripe.com