Stripe MCP Server

Stripe's MCP server connects AI agents to Stripe's payment APIs to inspect customer billing profiles, query invoice statuses, review payment transactions, and handle refund workflows. It enables agents to assist support and finance operations with access to subscription statuses, balance histories, and payment reconciliation data.

Start for free

Stripe MCP Server

Benefits with Ory + Stripe MCP Server

Stripe's MCP server gives your agents access to customers, products, payments, invoices, subscriptions, and refunds in your Stripe account, and many of its tools perform administrative actions on money and billing. Ory Agent Security lets a finance agent read and write payment data with the administrative tools blocked, while a coding agent working for an engineer or user stays read-only on the same server. Every Stripe tool call is recorded with the user and agent behind it.

View documentation

Use Cases

— 01 use case

Agent IAM

Support agents look things up at Read, billing agents draft invoices at Write, refunds and payouts stay at Admin, and Block keeps unrelated agents away from money.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Stripe MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for engineering agents debugging an integration, write for finance agents that create invoices and customer records, admin for the few agents that own refunds and other money movement, and no access for agents with no role in billing.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied refund stops before it reaches Stripe, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents touch payment data and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the Stripe MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Stripe MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent issued a refund or changed a subscription, and for which user.