Sign in Book a demo
Back to Tools
Finance & Payments API Key
Build Your Agent View Stripe Documentation
stripe logo

Stripe MCP Tools for AI Agents

Let an agent create customers, invoices, products, payment links, and refunds, or read Stripe balances and payment data.

Available Tools

16 tools available in this integration

Stripe.CreateBillingPortalSession

This tool will create a billing portal session.

Stripe.CreateCustomer

This tool will create a customer in Stripe.

Stripe.CreateInvoice

This tool will create an invoice in Stripe.

Stripe.CreateInvoiceItem

This tool will create an invoice item in Stripe.

Stripe.CreatePaymentLink

This tool will create a payment link in Stripe.

Stripe.CreatePrice

This tool will create a price in Stripe.

Stripe.CreateProduct

This tool will create a product in Stripe.

Stripe.CreateRefund

This tool will refund a payment intent in Stripe.

Stripe.FinalizeInvoice

This tool will finalize an invoice in Stripe.

Stripe.GetBalance

This tool will get the balance from Stripe.

Stripe.ListCustomers

This tool will fetch a list of Customers from Stripe.

Stripe.ListInvoices

This tool will list invoices in Stripe.

Stripe.ListPaymentIntents

This tool will list payment intents in Stripe.

Stripe.ListPrices

This tool will fetch a list of Prices from Stripe.

Stripe.ListProducts

This tool will fetch a list of Products from Stripe.

Stripe.RetrieveBalance

This tool will retrieve the balance from Stripe.

Working directly against the raw API? 220 more tools in the Stripe API server →

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "refund the duplicate payment for Acme and return the refund status." Arcade picks the right Stripe tools without guessing payment-intent IDs or refund details first.

Up to 100x fewer tokens

Stripe list operations return focused records such as IDs, amounts, statuses, and timestamps, so the agent can review customers, invoices, or payment intents without loading unnecessary billing data into the model.

Complete the workflow end to end

Find the customer, create the invoice items, prepare the invoice, request approval, finalize it, and return the result through one toolkit designed around the complete Stripe billing task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Stripe

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Stripe, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Stripe.CreateRefund from agents unless the roles your IDP marks as billing owners are active, so an agent cannot return customer payments without authorization.
  • Restrict Stripe.CreatePaymentLink to agents operating under your sales-operations role, so unreviewed automation cannot publish a new way to charge customers.
  • Deny Stripe.FinalizeInvoice to agents outside your accounts-receivable role, so an agent cannot turn an unreviewed draft into a customer-facing invoice.
Pre-execution before each tool call
  • Require human approval before Stripe.CreateRefund runs, so a mistaken or fraudulent refund cannot move money without review.
  • Require human approval before Stripe.CreatePaymentLink runs, so an agent cannot publish a payment page with an unapproved price.
  • Block Stripe.FinalizeInvoice when the invoice lacks an approved billing owner, so an agent cannot send an incorrect amount to a customer.
Post-execution after the tool returns
  • Redact email addresses, phone numbers, and billing addresses from Stripe.ListCustomers results before they reach the model.
  • Strip invoice descriptions, customer contact details, and payment terms from Stripe.ListInvoices results, so the model receives invoice status without unnecessary customer data.
  • Deny the output of Stripe.RetrieveBalance to agents outside your finance role, so account balances do not reach unauthorized workflows.

How to use Stripe with your agent

Pick your MCP client below and follow the setup to connect your agent to Stripe. Then try prompts that create, read, and manage payment data.

Your questions, answered

A Stripe MCP server exposes Stripe capabilities as structured tools that an AI agent can call through the Model Context Protocol. With Arcade, an agent can inspect balances, customers, invoices, payment intents, products, prices, and create or manage supported billing and payment records.

Arcade provides the MCP access layer for Stripe and adds authenticated tool execution, agent-optimized actions, approval workflows, redaction, and access controls. You configure a shared Stripe API key or secret once instead of building credential handling into each agent.

Arcade agents can retrieve balances and list customers, invoices, payment intents, products, and prices. They can also create customers, products, prices, invoices, invoice items, payment links, billing portal sessions, finalize invoices, and refund payment intents.

Stripe access is determined by the API key or secret configured for the connection; this integration does not use per-user OAuth scopes. Give Arcade a key with only the Stripe permissions needed for the actions your agent will perform, and use a restricted key where appropriate.

No. This integration uses one shared API key or secret configured once, rather than having each user connect an individual Stripe account. Calls run with the access granted to that configured credential, which is brokered to the agent without exposing the secret to the model.

Yes. Contextual Access policies can require human approval before consequential Stripe actions such as creating a refund, finalizing an invoice, creating a payment link, or creating billing records. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Stripe API calls and does not persist your Stripe content as part of normal tool execution. The configured credential is brokered and stored encrypted at rest, and the model never receives the raw API key or secret.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the configured authorization remains valid. If the Stripe key or secret is revoked, rotated, or can no longer be used, calls stop until the credential is reconnected or replaced.

Stripe's API rate limits and any account-level restrictions still apply to calls made through Arcade. The available details do not specify a separate Stripe limit for this integration, so plan around Stripe's current limits for the endpoints and account you use.

Ready to actually ship your agent?

Connect your agent to Stripe with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Stripe Quickstart