-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
Stripe's MCP server only accepts Bearer tokens, when trying to connect is not working.
Currently, this remote server only supports bearer token authentication. OAuth isn’t supported. To avoid phishing attacks, verify that you only use trusted MCP clients, and that the URL you’re using is the official https://mcp.stripe.com/ server.
Stripe docs: https://docs.stripe.com/building-with-llms#mcp-remote
To Reproduce
Steps to reproduce the behavior:
- Go to https://playground.ai.cloudflare.com/
- Set MCP server to https://mcp.stripe.com/
- Set bearer token from stripe
Expected behavior
Should connect and interact to Stripe's MCP server using Bearer Tokens
Logs
Logs from https://playground.ai.cloudflare.com/ debug console
[debug] Auth callback message listener added.
[debug] useMcp mounted, initiating connection.
[debug] BrowserOAuthClientProvider initialized/updated on mount/option change.
[info] Connecting attempt #1 to https://mcp.stripe.com/...
[debug] MCP Client initialized in connect.
[info] Attempting connection with HTTP transport...
[debug] HTTP transport created.
[info] Connecting client via HTTP...
[debug] Client connect error via HTTP: {}
[warn] HTTP transport failed (CORS). Will attempt fallback to SSE.
[info] Attempting connection with SSE transport...
[debug] SSE transport created.
[info] Connecting client via SSE...
[debug] Client connect error via SSE: {"event":{"isTrusted":false,"message":"Failed to fetch"}}
[error] Failed to connect via SSE: SSE error: Failed to fetch {"event":{"isTrusted":false,"message":"Failed to fetch"}}
[debug] Connection sequence finished with status: fallback
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working