What it takes off you is the API legwork: find the customer, check the charge, issue the refund, without opening the dashboard or writing the call yourself. That reaches the whole documented API rather than a fixed set of actions, so the same connection can also stand up a new integration.
Stripe runs the server, so there is nothing to install. Authorize over OAuth and the agent acts as you — no secret key sitting in a config file.
- Search the API, read a method's parameters, then call it — read or write
- Any of the 115 documented Stripe API methods, reached through two proxy tools
- Account info, refunds and a balance summary as named tools
- Documentation search and an implementation planner
A Stripe account with MCP switched on by an admin. Sandbox and live are separate switches, so turning it on for testing does not turn it on for real money.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen