Payments

Stripe logo

Stripe MCP server

Give AI agents governed access to the Stripe MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.

What is the Stripe MCP server?

The Stripe MCP server is an open Model Context Protocol (MCP) server that connects AI agents to Stripe payments, customers, subscriptions, and invoices. Through it an agent can look up charges, create payment links, issue refunds, and read balances without bespoke integration code, while the Averta MCP Gateway keeps every action scoped and audited.

stripe-search-payments

Search charges and payments by status, amount, or customer.

stripe-create-payment-link

Generate a payment link for a product or price.

stripe-create-customer

Create a customer record with billing details.

stripe-retrieve-balance

Read the current account balance and pending funds.

stripe-list-subscriptions

List active and past subscriptions for a customer.

stripe-create-refund

Issue a full or partial refund on a charge.

stripe-list-invoices

List and filter invoices by status and customer.

stripe-create-product

Create products and prices in the catalog.

stripe-list-disputes

List open disputes and their evidence status.

stripe-get-metrics

Read revenue and payment metrics over a period.

Why the Averta MCP Gateway

Centralized governance

Unified authentication, audit logging, and rate control for every Stripe MCP connection.

Observability and control

Real-time visibility into usage, anomalies, and SLA compliance across every request.

One-click deployment

Enable the Stripe MCP server for your AI teams through one governed gateway, with no manual setup.

Enterprise hardening

High availability, security, and compliance alignment turn MCP from a developer utility into production-grade infrastructure.

OAuth and SSO enforcement

Enterprise authentication and SSO applied automatically to every Stripe endpoint.

Shared and per-user auth

Configure service accounts or per-user access, with secrets protected and centralized revocation.

One managed endpoint

Connect agents to Stripe through a single governed endpoint instead of locally run servers, improving your security posture.

Granular tool access control

Allow only the tools each role needs. Enable read-only access and block write tools like create and delete.

Works with every major AI platform

ChatGPT logoChatGPT
Gemini logoGemini
Mistral logoMistral
Claude Code logoClaude Code
Cursor logoCursor
Windsurf logoWindsurf
Cognition logoCognition
OpenCode logoOpenCode
Continue logoContinue
Manus logoManus
Hermes logoHermes
Lindy logoLindy
OpenClaw logoOpenClaw
Your own logoYour own

Built for enterprise teams.

Cloud, private VPC, embedded SDK, or gateway integration. Run Averta where your data, policies, and auditors need it.

AWS
Google Cloud
Azure
Oracle
Book a demo

Cloud (SaaS)

Fully managed by Averta. Fastest path to production, no infrastructure to run.

Private / VPC

Deploy in your own environment, so data never leaves your boundary.

Embedded SDK & Proxy

Drop Averta into your stack at the SDK or proxy layer, wherever your agents run.

Gateway Integration

Route agent traffic through the gateway, so policy and audit apply at the edge.

Stripe MCP use cases

Where teams put the Stripe MCP server to work, governed end to end through the Averta MCP Gateway.

Agents reconcile charges against expected revenue and surface mismatches, read-only.

Book a demo
Stripe MCP · Payment reconciliation

Find charges from yesterday that do not match an invoice.

You

Found 3 unmatched charges to review.

  • Listing yesterday's charges
  • Matching against invoices

All actions logged and governed

Powering safe AI execution at leading teams.

Cyfrin secures its production AI agents with Averta.

Book a demo
Averta gave our agents enforceable boundaries for the dev environment, so instructions like ‘don’t read .env files’ became policy instead of polite suggestions.
Mikhail Karan

Mikhail Karan

Head of Engineering

Explore other MCP servers

Stripe MCP server, answered

Security and setup questions teams ask before connecting the Stripe MCP server to AI agents.

Yes. The Averta MCP Gateway sits between your AI agents and any MCP server, giving each agent scoped, per-agent permissions, applying allow, escalate, or block policies on every tool call, and recording a tamper-evident audit of every action. The “Why the Averta MCP Gateway” section on this page covers what it enforces.

It is as safe as the controls around it. The server can move money through refunds and payment links, so write access is the real risk. The Averta MCP Gateway keeps those actions read-only or behind approval and records every call.

Apply tool-level policy through the Averta MCP Gateway so read operations like searching payments run automatically while refunds and payouts escalate for approval. Every action is logged.

Route agents through Averta's MCP Gateway for scoped per-agent permissions, tool-level policy, and tamper-evident audit across every Stripe action.

Yes. Stripe publishes an official MCP server as part of its agent toolkit. Whichever server you run, routing it through the Averta MCP Gateway is what keeps refunds, payment links, and other write actions behind policy with a tamper-evident audit trail.

See Averta OS in action

Book a demo and see how Averta OS secures your AI agents from input to execution.

Book a demo