Enterprise DNAEnterprise DNA

MCP Servers

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.

Visit Stripe ↗

Our verdict

Not reviewed yet

We have not reviewed Stripe Agent Toolkit MCP Server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About Stripe Agent Toolkit MCP Server

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

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.

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

Key facts

What we have checked

Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx skills add https://docs.stripe.com

Clients the listing names (not checked here)

Claude Code, Cursor, ChatGPT

Install

Add Stripe Agent Toolkit MCP Server to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (remote server)

claude mcp add --transport http stripe-agent-toolkit-mcp-server https://mcp.stripe.com

Version 0.2.4 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Cursor

Config checked

Add to .cursor/mcp.json (remote server)

{
  "mcpServers": {
    "stripe-agent-toolkit-mcp-server": {
      "url": "https://mcp.stripe.com"
    }
  }
}

Version 0.2.4 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (remote server)

{
  "servers": {
    "stripe-agent-toolkit-mcp-server": {
      "type": "http",
      "url": "https://mcp.stripe.com"
    }
  }
}

Version 0.2.4 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (remote server)

[mcp_servers.stripe-agent-toolkit-mcp-server]
url = "https://mcp.stripe.com"

Version 0.2.4 · From the Official MCP registry, read · Format checked against Codex's config docs

ChatGPT

Config checked

Fill in the Add custom MCP server form (remote server)

Where
ChatGPT Plugins > + > Add custom MCP server
Name
stripe-agent-toolkit-mcp-server
Description
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Connection
Public endpoint
MCP server URL
https://mcp.stripe.com

Version 0.2.4 · From the Official MCP registry, read · Format checked against ChatGPT's config docs

  • Claude Desktop: Its config file takes local servers only; a remote server is added in the app as a connector.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What Stripe Agent Toolkit MCP Server connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRemote server, version 0.2.4Config checkedClaude Code docs
CursorClientInstall recipe matches the client's documented formatRemote server, version 0.2.4Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRemote server, version 0.2.4Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRemote server, version 0.2.4Config checkedCodex docs
ChatGPTClientInstall recipe matches the client's documented formatRemote server, version 0.2.4Config checkedChatGPT docs

Sources

Where this comes from

No sources recorded yet. Each source we check is listed here with the date we checked it.

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →