Skip to directory

About Stripe MCP

Stripe's hosted MCP server lets AI clients search Stripe API methods and documentation, inspect account data, and call Stripe API operations subject to the authorized account, environment, and permissions.

What you can use it for

  • Search Stripe API methods and inspect required parameters
  • Read Stripe customer, payment, subscription, and other resources allowed by the connected account
  • Build and troubleshoot Stripe integrations using Stripe documentation
  • Work with billing and payment resources through supported API methods
Connection and setup
Hosting
Remote, Stripe-hosted
Transport
Streamable HTTP
Endpoint
https://mcp.stripe.com
Authentication
OAuth for interactive clients; Stripe Agent API key as bearer token for clients that cannot use OAuth. Team administrators can manage MCP access separately for live and sandbox environments.

Requirements

  • Stripe account or sandbox
  • MCP-capable client supporting OAuth, or a Stripe Agent API key stored locally as an environment variable
  • For Claude Team/Enterprise, workspace owner must enable the connector before members connect

Setup steps

  1. Add `https://mcp.stripe.com` as a remote MCP server in the client, or use Stripe's agent setup command: install `@stripe/cli` and run `stripe agent setup`.
  2. For Codex, Stripe documents `codex mcp add stripe --url https://mcp.stripe.com`; after adding it, authenticate with OAuth.
  3. For Claude Code, run `claude mcp add --transport http stripe https://mcp.stripe.com/`, then start Claude Code and run `/mcp` to authenticate.
  4. For Claude Desktop or ChatGPT, install the official Stripe connector/plugin and sign in through the OAuth window; enable Stripe in the conversation.
  5. Use an Agent API key only when OAuth is unsupported. Store it in a local environment variable and reference that variable in config; never paste the key into chat.
  6. Enable tool approval in the client. Verify with a read-only account or documentation lookup before making changes.
Tools 15

The current Stripe reference enumerates 15 MCP tools. Atlas formation and five Treasury tools are preview-gated; Analytics has preview/Sigma requirements. Many Stripe API methods are selected through stripe_api_search/details/read/write rather than registered as separate tools. Available operations depend on account, permissions, mode and product eligibility.

  • stripe_api_search

    Search Stripe API methods by keyword.

    01
  • stripe_api_details

    Get parameter details for a Stripe API method.

    02
  • stripe_api_read

    Read data through Stripe API GET methods.

    03
  • stripe_api_write

    Write data through Stripe API POST, PATCH, PUT, and DELETE methods.

    04
  • get_stripe_account_info

    Retrieve Stripe account information.

    05
  • search_stripe_documentation

    Search Stripe documentation.

    06
  • stripe_implementation_planner

    Guide integration planning across Stripe products.

    07
  • stripe_analytics

    Preview analytics querying; SQL generation requires Sigma.

    08
  • send_stripe_feedback

    Send feedback about Stripe products.

    09
  • atlas_company_formation

    Start or resume a Delaware C corporation or LLC formation.

    10
  • get_balance_summary

    Public preview: display an interactive summary across Stripe balance and Treasury accounts.

    11
  • convert_currency

    Public preview: convert funds between currencies within a Treasury account.

    12
  • send_money

    Public preview: send money from a Treasury account to a recipient.

    13
  • setup_recipient

    Public preview: set up a recipient account for Treasury payments.

    14
  • transfer_money

    Public preview: transfer money between supported Stripe balances.

    15
Limitations and notes
  • Writes can create consequential changes. Stripe requires human confirmation for certain actions such as refunds and outbound payments. Enable tool approval and review each action.
  • OAuth support for connected-account operations is not available; Stripe documents restricted API keys and a Stripe-Account header for that mode.
  • Analytics/Sigma, Treasury, Atlas, and other tools have preview or product-specific access conditions.
  • Stripe notes that existing non-Agent keys will cease to be accepted for MCP API-key authentication beginning November 30, 2026; follow current official migration guidance.
Original sources
  • official tool reference

    Stripe’s hosted MCP exposes four general API tools plus account, Atlas, analytics, Treasury, documentation, integration-planning and feedback tools. Preview tools and API methods depend on account eligibility, permissions, environment and product access; API operations are routed through generic read/write tools rather than one MCP tool per endpoint.

  • official documentation or source

    Stripe’s hosted MCP exposes four general API tools plus account, Atlas, analytics, Treasury, documentation, integration-planning and feedback tools. Preview tools and API methods depend on account eligibility, permissions, environment and product access; API operations are routed through generic read/write tools rather than one MCP tool per endpoint.

Documentation checked 2026-10-28T12:38:00.000Z. Connection has not been runtime tested.