Set up Stripe MCP in test mode

Stripe MCP lets agents search developer documentation and work with Stripe resources when you supply a restricted API key. Start in test mode with the smallest tool surface your workflow needs.
What Stripe MCP is
Stripe MCP combines Stripe docs search with tools for customers, products, invoices, and payment links. Access stays bounded by the permissions on your API key.
Install command
npx -y @stripe/mcp --tools=all --api-key=$STRIPE_SECRET_KEY
Setup steps
- Create a restricted Stripe secret key in test mode with only the permissions you need.
- Pass the key through your MCP client’s environment variables—not inline in committed config.
- Limit enabled tools to documentation search first, then add create/update tools if required.
- Verify whether a tool can create billing objects before running it against live data.
Security notes
Some tools can create customers, invoices, and payment links. Never attach a full-access live secret key to an agent. Rotate keys if a config file was shared accidentally.
Related: MCP Servers Directory, GitHub MCP setup, and Bowora’s finance startups directory.
FAQ
- Should I use a live Stripe key?
- No. Start with a restricted test-mode key and enable only required tools.
- Can Stripe MCP create billing objects?
- Some tools can create customers, invoices, and payment links when the key allows it.
- Which clients does Bowora list?
- Claude, Codex, Cursor, and VS Code.
- Where is the source?
- Linked from /mcp/stripe.


