Skip to content
Back to skills

Stripe

ASecurity

Manage a merchant's Stripe customers, products, coupons, promotion codes, payments, invoices, and recurring subscriptions. Use for billing-plan changes, payment links, refunds of duplicate card charges, disputes and chargebacks, account balances, payouts, and reconciling processing fees through Stripe's official MCP server.

  • 69,003 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
ai-agentsapi

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 4, 2026

npx -y skills add asgeirtj/system_prompts_leaks --skill stripe --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Stripe?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Stripe
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asgeirtj-stripe/badge)](https://www.skillsdirectory.com/skills/asgeirtj-stripe)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "stripe"
description: >-
  Manage a merchant's Stripe customers, products, coupons, promotion codes, payments,
  invoices, and recurring subscriptions. Use for billing-plan changes, payment links,
  refunds of duplicate card charges, disputes and chargebacks, account balances,
  payouts, and reconciling processing fees through Stripe's official MCP server.
icon: "connectorStripe"
metadata: { "includeInPrompt": false }
---

# Stripe

Use the installed `stripe` CLI. Start with `stripe status`. If it reports
`not_connected`, run `stripe authorize-url` and share only the returned
`connect_url` with the user.

OAuth uses Dynamic Client Registration and PKCE through authd. Stripe issues a
per-VM public client, so no shared credential enters Muse and credentials must
never be requested in chat.

Run `stripe list-tools` to inspect the live provider catalogue and schemas,
then call an advertised tool with:

```text
stripe call-tool --name <tool> --arguments-json '<json-object>'
```

The OAuth connection identifies the merchant account. Never ask the user for
that connected account's `acct_...` ID. If another tool requires
`stripe_context`, first call the advertised `list_available_accounts_or_orgs`
tool with an empty arguments object and use a context it returns. If more than
one context matches the requested live or test mode, present their names and
ask the user which account to use; do not ask them to paste an account ID. Never
invent a context or call an account-scoped tool without one returned by Stripe.

`list-tools` exposes only reviewed Stripe tools and includes each tool's
`hatch_permission`, `hatch_action`, and `hatch_permission_label`. Unknown or
new provider tools remain unavailable until reviewed. For `stripe_api_write`,
the returned schema lists the reviewed `stripe_api_operation_id` values and
their operation-specific permission overrides; unlisted operation IDs are not
available. Read permissions follow the user's connector settings; Stripe API
writes and feedback require granular approval. Stripe may also require
confirmation through a provider URL for sensitive operations. Do not retry a
failed or timed-out write automatically because its side effect may have
completed.

Files in this skill

  • SKILL.md2.2 KB
  • connector_auth_config.yaml255 B
  • manifest.yaml2.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.