Enterprise DNA
M MCP Servers Data and DB low

Stripe Agent Toolkit MCP Server

by Stripe

Expose Stripe's full payments and billing API as MCP tools — customers, charges, subscriptions, invoices, and refunds for any MCP-compatible agent.

SA

MCP

Stripe Agent Toolkit MCP Server

Added 28 Jan 2025

#payments #billing #finance #api #stripe #mcp #official #subscriptions

Overview

Stripe Agent Toolkit is Stripe's official open-source library that surfaces the Stripe API as callable tools for AI agents, including a first-class MCP server implementation. It exposes tools for managing customers, creating and inspecting charges, handling subscriptions and subscription items, generating and voiding invoices, issuing refunds, and working with payment intents and products — giving agents the ability to automate the full payments and billing lifecycle without custom API wrappers. The toolkit ships as an npm package (`@stripe/agent-toolkit`) and integrates natively with MCP-compatible hosts such as Claude Desktop, Claude Code, Cursor, and Windsurf via stdio transport, as well as with LangChain and Vercel AI SDK for non-MCP agent frameworks. Authentication uses standard Stripe API keys with support for restricted keys, enabling least-privilege scoping so agents can be limited to read-only or specific resource types. Teams running SaaS billing, marketplace payouts, or support automation workflows will find this the fastest path to giving agents safe, structured access to their Stripe account.

Best for

Best for
SaaS and marketplace teams that want agents to automate payments, billing, and customer operations across the full Stripe API surface

Use cases

  • Look up a customer record and their open invoices from a support agent workflow
  • Issue a refund or apply a credit note to a charge without leaving the agent session
  • Create or update a subscription plan and attach it to a customer in one agent loop
  • Generate monthly revenue summaries by querying charges and invoices through an agent
  • Automate dunning workflows by inspecting failed payment intents and retrying charges

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.

Pros

  • Official Stripe library — kept current with Stripe API changes and new products
  • Restricted-key support enables tight per-agent permission scoping
  • Works with both MCP hosts (Claude Desktop, Cursor) and non-MCP frameworks (LangChain, Vercel AI SDK)
  • Covers the full billing lifecycle: customers, charges, subscriptions, invoices, refunds
  • MIT licensed and open source — auditable and forkable for custom tool surfaces

Cons

  • Live-mode API keys require deliberate guardrails to prevent accidental mutations
  • Advanced Stripe products (Connect, Radar, Tax) have limited or no tool coverage
  • Multi-account or multi-entity setups require per-account key management discipline
  • No built-in rate-limit handling — high-volume agent loops can hit Stripe API limits