Stripe
Search customers and charges through the Stripe MCP server, and choose which AI agents can issue refunds or write data
An agent with Stripe can search customers, charges, and invoices, but it can also issue refunds and send any write request to the Stripe API. Adding Stripe here puts each tool behind a policy rule and records each call in the audit log, so you decide which agents can refund payments or change your account and which can only read.
Server URL: https://mcp.stripe.com/
Credential modes
Stripe supports per-org dynamic registration only, so there is no app to create on Stripe's side and no client ID or secret to enter. See Credential modes for how it compares with Use SecureAuth's app and Bring your own app.
Before you begin
- A Stripe account that can reach the data your agents need.
- Administrator access to your Agent Authority workspace, to add the resource.
Setup
- In the Agent Authority console, go to Tools & Services and click Add Resource.
- Select Stripe from the catalog.
- On Choose how to install Stripe, click Per-org dynamic registration. Selecting it adds the resource right away with its tools pre-configured.
Dynamic client registration
When you add the resource, the gateway registers its own OAuth client with Stripe, the credential that lets it sign users in. Stripe's own account and role-based permissions still apply, so an agent can only reach what the person who signed in could already reach.
Verify the connection
The gateway syncs the Stripe tools automatically. To check the connection end to end, ask your agent to run a request:
Get my Stripe account infoIf your Stripe account details come back, the connection is working.
How users connect
Access is per user. Each additional user connects their own Stripe account the first time their agent calls a Stripe tool: the gateway returns a sign-in link, the user authorizes once, and the tools work from then on. Go to Connections to manage linked accounts.
Available tools
| Tool | Tags | Description |
|---|---|---|
get_stripe_account_info | read-only | Get information about the connected Stripe account |
search_stripe_resources | read-only | Search across Stripe API resources (customers, charges, invoices, etc.) |
fetch_stripe_resources | read-only | Fetch specific Stripe API resources by ID |
stripe_api_search | read-only | Search the Stripe API for relevant endpoints |
stripe_api_details | read-only | Get details about a specific Stripe API endpoint |
stripe_api_read | read-only | Make a read (GET) request against the Stripe API |
stripe_api_write | destructive, external | Make a write (POST/DELETE) request against the Stripe API |
create_refund | destructive, external | Create a refund for a charge or payment intent |
stripe_implementation_planner | read-only | Plan an implementation for integrating with Stripe |
search_stripe_documentation | read-only | Search Stripe's documentation |
send_stripe_mcp_feedback | write, external | Send feedback about the Stripe MCP server to Stripe |
stripe_api_write is the tool to watch.
It takes an arbitrary API path and payload, so it can reach write endpoints that no other tool in this list exposes.
Required scopes
The gateway requests this scope automatically when it registers the client, so there is nothing for you to configure. Stripe decides what to grant, and any scopes it returns during registration replace the list below.
mcp: grants access to Stripe's hosted MCP server.
Policy examples
Read-only Stripe access, denying refunds and generic API writes:
Deny - MCP: stripe - Tools: create_refund, stripe_api_write - Effect: DenyScope an agent to documentation and API discovery only:
Allow - MCP: stripe - Tools: search_stripe_documentation, stripe_api_search, stripe_api_details, stripe_implementation_planner - Effect: AllowBlock destructive tools by built-in tag:
Deny - MCP: stripe - Tools: tag destructive - Effect: DenyNext steps
- Create a policy – start from the read-only pattern in Policy examples above.
- Connections – manage the Stripe accounts your users have linked.