pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Stripe

Pod holds 20 of 36 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Stripe.

Most discussed

Support resources/templates/list (return empty) so mcp.stripe.com works with strict MCP clients

Is your feature request related to a problem? Please describe.

Yes. The remote MCP server mcp.stripe.com advertises a resources capability in its initialize response, but returns -32601 Method not found for resources/templates/list. MCP clients that enumerate resource templates during capability sync reject the whole server on that single error.

Registering mcp.stripe.com as an Amazon Bedrock AgentCore Gateway mcp_server target fails synchronization — even though auth

Read the thread · 2026-05-31 · closed · external user · 4 comments

Add policy enforcement for payment and financial operations

This toolkit gives agents access to ~30 Stripe tools with real financial impact:

  • create_payment_intent -- initiates real charges on cards
  • create_refund -- refunds money to customers
  • cancel_subscription -- cancels recurring billing
  • finalize_invoice -- locks invoices for payment collection
  • create_checkout_session -- generates live payment pages

An agent can issue refunds, cancel subscriptions, charge cards, and create payment links. These are irreversible financial operations

Read the thread · 2026-04-12 · open · external user · 17 comments

Support multiple Stripe accounts in MCP server

Feature Request

The MCP server currently supports authenticating with a single Stripe account via OAuth. Many businesses operate multiple Stripe accounts (e.g. one per product line or entity) and need their AI agents to access all of them within the same session. Currently this requires re-authenticating each time, which isn't practical for automated workflows.

Proposed Solution

Support multiple authenticated accounts, either by:

  • Allowing multiple OAuth connections with account aliase

Read the thread · 2026-04-07 · closed · external user · 6 comments

RFC: Cryptographic signing and spend limits for agent-initiated payments

As agent-initiated payments scale via MPP, there are security gaps at the protocol layer that restricted API keys don't address.

No per-agent spend limits

Restricted keys control which operations an agent can perform, but not how much it can spend. An agent with payment_intents:write permission can create unlimited payment intents of any amount. There's no mechanism to say "this agent can spend up to $100 per transaction and $500 per day."

**No cryptographic proof of which agent authorise

Read the thread · 2026-03-23 · closed · external user · 6 comments

Protected resource https://mcp.stripe.com does not match expected https://mcp.stripe.com/

Describe the bug

Hello,

After installing the gemini extension:

$ gemini extensions install https://github.com/stripe/ai

I'm seeing this issue whenever I start up gemini-cli and I am unable to authenticate.

ℹ MCP server 'stripe' requires authentication using: /mcp auth stripe ✕ Error during discovery for MCP server 'stripe': Protected resource https://mcp.stripe.com does not match expected https://mcp.stripe.com/

To Reproduce

  1. $ gemini extensions install https://github.com/str

Read the thread · 2026-01-26 · closed · external user · 9 comments

Optional parameters should be made nullable

Is your feature request related to a problem? Please describe.

I have an agent that uses the Stripe MCP server and sometimes passes null to optional parameters, causing the tool call to fail.

Describe the solution you'd like

It would be great if optional parameters could also be marked nullable to prevent these errors.

Describe alternatives you've considered

I've tuned my prompts as much as possible but there always seems to be another parameter I've missed that ends up being op

Read the thread · 2025-09-14 · closed · external user · 4 comments

Stripe MCP OAuth not working on VSCode 1.103.2

Describe the bug

Following steps outlined at https://docs.stripe.com/mcp?mcp-client=vscode

VSCode fails to get a proper OAuth token, with the following error on dashboard when forwarding the OAuth request

Image

OAuth URL https://marketplace.stripe.com/oauth/v2/authorize?client_id=https%3A%2F%2Fdashboard.stripe.com%2Fsettings%2Fapps%2Fcom.stripe.mcp&response_type=c

Read the thread · 2025-09-10 · closed · external user · 5 comments

Dispute tools not available on MCP

Describe the bug

The two dispute tools added to the MCP server in this PR are not available. Only 18 out of the 20 tools show up (missing both dispute related methods).

Output from using this configuration:

"mcp": {
        "servers": {         
             "stripe": {
                "command": "npx",
                "args": ["-y", "@stripe/mcp", "--tools=disputes.read"],
                "env": {
                  "STRIPE_SECR

[Read the thread](https://github.com/stripe/ai/issues/86) · 2025-05-07 · closed · external user · 4 comments

## Most recent

### stripe-agent-toolkit v0.7.x silently ignores the removed `configuration.actions` policy, fail-opening the toolset handed to LangChain and CrewAI agents

Affected repo: stripe/ai, tools/python (shipped as `stripe-agent-toolkit` 0.7.0+)
Pinned commit: 3ca4090c2aef3fc1fd21754c5ef82efe0d56149e (main, 2026-08-28)
Compared release: stripe-agent-toolkit 0.6.1 (PyPI sdist)
PUBLIC-READY
R05P2-M1 (policy-dialect fail-open), instance R06P2-F1
Honesty ledger: EXECUTED (PoC at pin, offline stub MCP), PROVED (code diff 0.6.1 vs pin), DERIVED (LangChain docs drift observed 2026-08-27)

## Summary

The v0.6.x Python toolkit filtered its tool list through `is_to

[Read the thread](https://github.com/stripe/ai/issues/508) · 2026-08-29 · open · external user · 0 comments

### MCP manifest audit: tool names are clear, but DXT manifest lacks per-tool descriptions

Hi! I’m working on `audit-mcp`, a local CLI that reviews MCP tool surfaces for discoverability issues: overlapping tools, unclear primary vs follow-up actions, weak trigger language, and places where agents may not have enough signal to pick the right tool. (Also really sorry because I wasn't sure what template this issue fit under)

I tried to run it against the local Stripe MCP package. Since the local package proxies to the hosted Stripe MCP server and requires a valid key, I could not safely

[Read the thread](https://github.com/stripe/ai/issues/455) · 2026-06-25 · open · external user · 0 comments

### Optional "Receipt Required" guard for money-movement tools

The toolkit exposes money-movement actions (payments, refunds, payouts) to agents. I maintain EMILIA's open **Receipt Required** rail (Apache-2.0): a small, **opt-in** gate so a money-movement tool refuses to run unless a named human signed an authorization receipt for that *exact* action and amount — the agent-era equivalent of dual control.

The four-step behavior (CI-verified):
- missing receipt → `428 Receipt Required`
- valid, action-bound receipt → runs
- same receipt replayed → refused (o

[Read the thread](https://github.com/stripe/ai/issues/454) · 2026-06-24 · open · external user · 0 comments

### Stripe MCP Server ignores limit and starting_after pagination parameters on list endpoints

### Describe the bug

The Stripe MCP server (stripe_api_read) is not correctly passing pagination parameters to the Stripe API for list operations (confirmed on GetCustomers and GetSubscriptions).
Steps to Reproduce:

Call GetCustomers with limit: 100
Note that only 10 results are returned despite the higher limit
Take the last record's ID and call GetCustomers again with starting_after: <last_id>
Note that the same first 10 records are returned again — the cursor is ignored

Expected Behavior:

[Read the thread](https://github.com/stripe/ai/issues/444) · 2026-06-11 · closed · external user · 3 comments

### Normalized Anthropic model IDs fall back to the wrong default max_tokens

## Summary

The AI SDK provider normalizes Anthropic model IDs to dot-form names like `anthropic/claude-3.7-sonnet`, but the default `max_tokens` logic still only checks dash-form names like `claude-3-7-sonnet`.

That means common Anthropic inputs can silently fall back to `4096` instead of the intended model-specific defaults.

## Affected code paths

This looks to affect both V2 and V3:

- `llm/ai-sdk/provider/stripe-provider.ts`
- `llm/ai-sdk/provider/utils.ts`
- `llm/ai-sdk/provider/stripe-l

[Read the thread](https://github.com/stripe/ai/issues/432) · 2026-05-24 · open · external user · 0 comments

### Missing pagination support (starting_after) across all list and search tools

### Is your feature request related to a problem? Please describe.

## Summary
The Stripe MCP connector is missing cursor-based pagination support across 
all list and search tools. This makes it impossible to retrieve more than 
100 records in Claude, regardless of how many exist in the Stripe account.

## Affected tools
| Tool | Missing parameter |
|---|---|
| `list_subscriptions` | `starting_after` |
| `list_products` | `starting_after` |
| `list_prices` | `starting_after` |
| `search_stripe_

[Read the thread](https://github.com/stripe/ai/issues/388) · 2026-04-16 · open · external user · 0 comments

### Feature Request: Add subscription_schedules and charges support to the Stripe MCP connector

### Is your feature request related to a problem? Please describe.

## Feature Request: Add `subscription_schedules` and `charges` support to the Stripe MCP connector

### Summary

The current Stripe MCP connector is missing two commonly needed Stripe API resources:

1. **`/v1/subscription_schedules`** — for fetching planned/future subscriptions
2. **`/v1/charges`** — for fetching payment attempts including failed and Radar-blocked payments

Without these, AI assistants using the MCP connector h

[Read the thread](https://github.com/stripe/ai/issues/357) · 2026-04-07 · open · external user · 2 comments

### [RFC] Agent-native payment gating for Stripe MCP — pay-per-call via x402/MPP

## What this proposes

Adding pay-per-call payment gating to Stripe's MCP server so AI agents can pay for API operations directly — no human billing account required per deployment.

There's a certain elegance to it: agents paying for access to Stripe tools via agent-native payment rails (x402 USDC on Base, or MPP). The underlying Stripe API costs (per transaction, per call) get passed through to the agent caller seamlessly.

## Working demo

Payment-gated fork: **[github.com/tomopay/stripe-mcp]

[Read the thread](https://github.com/stripe/ai/issues/347) · 2026-03-31 · open · external user · 4 comments

### @stripe/mcp@0.3.2: Cannot find module './userAgent' — dist/userAgent.js missing from published package

## Bug

`@stripe/mcp@0.3.2` (latest on npm) fails to start with:

Error: Cannot find module './userAgent' Require stack:

  • /node_modules/@stripe/mcp/dist/index.js at Function._resolveFilename (node:internal/modules/cjs/loader:1401:15) ...

## Root cause

`dist/index.js` line 10 requires `./userAgent`:

```js
const userAgent_1 = require("./userAgent");

But the published dist/ directory only contains two files:

dist/
├── cli.js
└── index.js

userAgent.js was not i

Read the thread · 2026-03-24 · closed · external user · 4 comments

Suggestion: add a recommended rate limiting / security policy guide

Context

The Stripe agent toolkit exposes 27 MCP tools including create_refund, create_payment_link, cancel_subscription, and finalize_invoice. These are powerful financial operations with no built-in rate limits or per-tool access controls at the MCP layer.

For agents in production workflows, this can be risky. An agent stuck in a loop can batch-issue refunds. A prompt injection can trigger unexpected financial operations. System prompt guardrails saying "be careful with refunds" ar

Read the thread · 2026-03-17 · closed · external user · 0 comments

Security policy template for Stripe MCP server

We've built an open-source policy template for the Stripe MCP server that lets teams enforce guardrails on every tool call an AI agent can make.

The template covers all 27 tools exposed by your server — categorised into read, write, and destructive operations — with a ready-to-use YAML scaffold for adding rate limits, argument constraints, and access controls.

Example — constraining create_refund:

create_refund:
  rules:
    - name: "cap refund amount"
      conditions:

[Read the thread](https://github.com/stripe/ai/issues/293) · 2026-03-04 · open · external user · 0 comments

### MCP server hangs on initialize when client sends protocol version 2025-11-25

### Describe the bug

The Stripe MCP server (`@stripe/mcp` v0.2.3) hangs indefinitely when Claude Desktop sends an `initialize` request with `protocolVersion: "2025-11-25"`. The server never responds, causing Claude Desktop to timeout after 60 seconds.

**Note:** This is distinct from OAuth-related issues (#221, #288). I'm using a pre-configured API key (not OAuth), and the server starts successfully. The hang occurs specifically during the MCP protocol handshake when the client sends `protocolV

[Read the thread](https://github.com/stripe/ai/issues/290) · 2026-03-02 · open · external user · 1 comment