Stripe Agent Toolkit MCP Server

Overview

Connects your AI assistant to Stripe so you can ask what invoices are outstanding, look up a customer's billing history, issue a refund, or check a subscription, all without opening the Stripe dashboard. It covers the day-to-day billing tasks a business runs through Stripe: customers, charges, subscriptions, invoices, and refunds. Stripe's restricted API keys let you limit what the assistant can see or change, so you can start with read-only access and expand from there.

Best for

Best for
Businesses running billing through Stripe who want quick answers without the dashboard

Use cases

• Ask what invoices are outstanding for a customer
• Issue a refund on a charge from a plain-English request
• Check a customer's subscription status before a support call
• Pull a quick revenue summary from recent charges
• Set up a subscription for a new customer in one request

Notes

What it does

Stripe Agent Toolkit (@stripe/agent-toolkit) exposes the Stripe REST API as a structured set of agent-callable tools, with a built-in MCP server that any MCP-compatible host can connect to via stdio. The core tool groups cover customers (create, retrieve, update, list), charges (create, retrieve, list, capture), payment intents (create, confirm, cancel, retrieve), subscriptions (create, update, cancel, list items), invoices (create, finalize, pay, void, retrieve line items), refunds (create, retrieve, list), and products and prices (create, update, list). Each tool maps directly to a Stripe API endpoint with typed parameters, so agents get structured responses they can reason over without parsing raw HTTP.

How to deploy

Install the package with npm install @stripe/agent-toolkit and set the STRIPE_SECRET_KEY environment variable to a Stripe API key (use a restricted key in production). For MCP hosts, add the server to your claude_desktop_config.json or equivalent config under mcpServers, pointing at the toolkit’s MCP entry point. For LangChain or Vercel AI SDK, import the toolkit directly and pass your key at initialization — no MCP host required.

Best practices

Always use restricted API keys scoped to the minimum resources your agent workflow actually needs — for example, a support agent that only looks up customers and invoices should have a key restricted to customers:read and invoices:read. Pair with the Slack MCP server to close the loop on support workflows: the agent can look up a charge, issue a refund, and post a confirmation to a Slack channel in a single session. For write-heavy workflows (subscription mutations, refund issuance), add a human-in-the-loop confirmation step before the agent calls the mutating tool.