Stripe
Remote MCP server for Stripe payments, billing, customers, and developer documentation.
Connection specification
- Remote endpoint
https://mcp.stripe.com- Live-validated endpoint
https://mcp.stripe.com/- Browser access
- Not yet measured
- Declared MCP transport
- Streamable HTTP
- Live-validated MCP transport
- Not yet verified — Latest validation did not verify a transport
- Declared authentication
- OAuth 2.1
- Detected authentication
- OAuth 2.1 detected or retained from publisher evidence
- Protocol lifecycle
- Not yet negotiated
- Authorization server
https://access.stripe.com/mcp- Category
- Payments
Product documentation · Official listing documentation
Browse all MCP servers · Test this endpoint in the MCP Playground
Connect this server to your client
Claude Code setup
Run in a terminal. This user-scoped entry is available across projects.
claude mcp add --transport http --scope user 'stripe' 'https://mcp.stripe.com/'
No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Using live-validated endpoint: https://mcp.stripe.com/
- No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Publisher evidence (reviewed 2026-08-24): https://access.stripe.com/.well-known/oauth-authorization-server/mcp
- After adding the server, open Claude Code, run /mcp, select the server, and follow the browser flow to authenticate.
Codex CLI setup
Run in a terminal; Codex stores the entry in ~/.codex/config.toml.
codex mcp add 'stripe' --url 'https://mcp.stripe.com/'
codex mcp login 'stripe'
No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Using live-validated endpoint: https://mcp.stripe.com/
- No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Publisher evidence (reviewed 2026-08-24): https://access.stripe.com/.well-known/oauth-authorization-server/mcp
Cursor setup
Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.
{
"mcpServers": {
"stripe": {
"url": "https://mcp.stripe.com/"
}
}
}
No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Using live-validated endpoint: https://mcp.stripe.com/
- No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Publisher evidence (reviewed 2026-08-24): https://access.stripe.com/.well-known/oauth-authorization-server/mcp
VS Code setup
Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.
{
"servers": {
"stripe": {
"type": "http",
"url": "https://mcp.stripe.com/"
}
}
}
No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Using live-validated endpoint: https://mcp.stripe.com/
- No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
- Publisher evidence (reviewed 2026-08-24): https://access.stripe.com/.well-known/oauth-authorization-server/mcp
Latest validation evidence
- Validation status
- Online when last tested
- Validation checked at
- Aug 18, 2026 at 1:34 PM
- Validation detail
- Authentication challenge at https://mcp.stripe.com/ returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication oauth