Stripe
Stripe's own plugin for Claude. It adds ten skills, two slash commands, one agent, and hooks. Most of the skills help you build with Stripe: docs, best practices, Connect onboarding, Stripe Apps, Stripe Projects, Metronome billing, and API upgrades. Two do more: stripe-pay sends money to another Stripe business, and stripe-directory finds outside providers to pay.
Third-party, by Stripe
October 29, 2026
Install the plugin
Plugins install through Claude Code’s plugin marketplace. Two commands, no files to place by hand.
Install the stripe plugin. It installs through Claude Code only. If you're not Claude Code, stop and tell me.
/plugin marketplace add stripe/ai
/plugin install stripe@stripe
If you can't run slash lines, run these two lines in a shell instead:
claude plugin marketplace add stripe/ai
claude plugin install stripe@stripe
When both commands finish, confirm the stripe plugin is installed. Use /plugin, or run claude plugin list in a shell.
Then tell me to restart Claude Code so it picks up the new skills.- 1
Add the marketplace
Run this once in Claude Code. It registers the marketplace this plugin installs from (stripe), so every plugin in it becomes installable.
/plugin marketplace add stripe/ai - 2
Install the plugin
Installs this plugin and everything it bundles. Restart Claude Code afterwards so it picks the new skills up.
/plugin install stripe@stripe
Stripe publishes this plugin from its own stripe/ai repo. We list it
because people come here for help with payments and billing. Stripe wrote
it, and we haven’t reviewed it.
Most of it helps you build with Stripe: reading the docs, picking an
integration, fixing errors, and moving to newer API versions. The ten
skills run from stripe-docs and stripe-best-practices to Connect
onboarding, Stripe Apps, Stripe Projects, and Metronome. Two skills go
further. stripe-pay sends money to another Stripe business, and
stripe-directory finds outside providers you can pay.
The details below come from Stripe’s files at version 0.11.32, pinned to commit a835511.
Commands
/explain-error: explains a Stripe error code and how to fix it, with code examples./test-cards: shows Stripe test card numbers for different test cases.
Agent
company-researcher: looks up a company from its URL or description and works out how it likely uses Stripe Connect.
Hooks
The plugin adds 7 hooks across 5 events: SessionStart, PostToolUse, PostToolUseFailure, PostToolBatch, and UserPromptSubmit. Stripe says they ask for feedback and help you set up the Stripe CLI. Here’s what they do:
- Each time a Stripe skill runs, a hook tells Stripe which skill ran, using
the Stripe CLI. It doesn’t ask first. If
STRIPE_API_KEYis set, it sends that key along with the report. - At startup, a hook checks who you’re signed in as (
stripe whoami) and looks up the latest Stripe CLI version. - Some hooks tell Claude to write feedback for Stripe about the work. One does this every time a Stripe tool call fails, then tells Claude to keep going. Others do it after a batch of work or a new prompt. Stripe’s text tells Claude to show you the feedback and get your OK before sending it. That’s an instruction to Claude, not a check the hook enforces.
You can check them yourself in hooks.json.
What you need
Most skills use the Stripe CLI, so install it and run stripe login. The
plugin also adds Stripe’s hosted MCP server, and you sign in to it the first
time you use it. The two commands need neither.
The skills it ships
- connect-recommend
- connect-required-verification-information
- metronome
- stripe-apps
- stripe-best-practices
- stripe-directory
- stripe-docs
- stripe-pay
- stripe-projects
- upgrade-stripe
MCP connectors it declares
Stripe's hosted MCP server. The plugin adds it for you from its .mcp.json, so you don't need to add it again. Most of the skills use the Stripe CLI instead, so install it and run stripe login too.
View config snippet
# Only needed if you want this server without the plugin.
# Installing the plugin already adds it.
claude mcp add stripe --transport http https://mcp.stripe.com