---
name: stripe-essentials
description: Ground rules for using Stripe through the Stripe MCP server, covering confirming the account and live or test mode, looking up the API before calling it, reading before writing and never moving money without explicit approval. Use when the user asks for anything in Stripe and no more specific Stripe skill fits.
---

# Working with Stripe

## Which account, which mode

- `list_available_accounts_or_orgs` shows the accounts this connection can reach. Confirm which one, and whether it is live or test mode, before anything else. Say the mode in every answer.
- `manage_stripe_accounts` switches or manages accounts; only use it when the user asks.

## Look up, then call

- Stripe's API is large. Find the right endpoint with `stripe_api_search`, and read its parameters with `stripe_api_details`, before calling.
- `stripe_api_read` performs GET requests: customers, subscriptions, invoices, charges, payment intents, refunds, disputes, payouts and prices. Use list filters, such as `customer`, `created` ranges and `status`, and limits.
- `search_stripe_documentation` answers how-to and concept questions from Stripe's docs.
- For balances and revenue questions, prefer `get_balance_summary` and `stripe_analytics` over paging through raw objects.
- `stripe_implementation_planner` plans a new Stripe integration.

## Money and customers

`stripe_api_write` can refund, cancel, create charges, change subscriptions and edit customers. Before any write, show the account, mode, endpoint, every parameter and the amount and currency, and wait for the user's explicit yes. In live mode, say clearly that it moves real money or affects a real customer. Never retry a failed write without asking.

## Privacy

Show only the customer data the question needs. Never print full card or bank details; Stripe returns only the last four digits anyway.

## Feedback

`send_stripe_mcp_feedback` sends feedback to Stripe about the MCP server. Use it only when the user asks, with text they approved.