Skip to main content

FrootAI — AmpliFAI your AI Ecosystem Get Started

All servers

Stripe Payments & Billing

stripe

Create and inspect Stripe customers, products, prices, payment links, and invoices via the official Stripe MCP server.

Installs
1.6k
Namespace
stripe
Version
>=0.3.0 <1.0.0
Last attach
reviewed1 months ago
Reliability
96.7% uptime (30d)· validated 2026-06-27

Add to your mcp.json

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "<STRIPE_SECRET_KEY>"
      }
    }
  }
}

Attach in a FrootAI play (fai-manifest)

mcp_scope:
  attached:
    - stripe

Authentication

restricted-api-key

create a Restricted API Key (`rk_…`) at dashboard.stripe.com/apikeys with the desired tool permissions, then set STRIPE_SECRET_KEY; use a test-mode key (`rk_test_…`) for development.

Required credential: STRIPE_SECRET_KEY

Environment variables

VariableRequiredAuth modeDescription
STRIPE_SECRET_KEYyesrestricted-api-keyStripe API key. Strongly prefer a Restricted API Key (`rk_…`) scoped to the exact tool permissions you need over a full secret key (`sk_…`). Tool availability is bounded by the key's permissions; pass via env, never inline in args (doctrine #6).

Sample tools

  • stripe.create_customer

    Create a new Stripe customer.

  • stripe.list_customers

    List existing customers.

  • stripe.create_product

    Create a product in the catalog.

  • stripe.create_payment_link

    Create a shareable payment link for a price.

  • stripe.create_invoice

    Create an invoice for a customer.

  • stripe.search_documentation

    Search Stripe's documentation to answer an integration question.

  • stripe.retrieve_balance

    Retrieve the current Stripe account balance.

Used in recipes

FAI cookbook recipes that attach stripe.

Destructive-action audit

No destructive tools — audited read-only

Destructive-action audit (X2.18): the server exposes no delete/destroy tools (`destructive_tools` is empty); financial mutations such as refunds still confirm per-call because the trust policy sets `allowDestructive: false` (X1.7 evidence).

Known limitations

  • Requires a Stripe API key (STRIPE_SECRET_KEY); without it the server cannot authenticate and every tool returns an auth error.
  • Tool availability is bounded by the Restricted API Key's permissions — a read-only key cannot create customers, invoices, or payment links.
  • Operates against real Stripe data when given a live key (`sk_live_…` / `rk_live_…`); use a test-mode key for development to avoid real charges.

Spec contributors

Maintainers who landed commits onmcp-specs/stripe.json.

  • pspsbali

Freshness

When this spec was last reviewed by a maintainer and last machine-validated against the live server.

Spec last reviewed
1 months ago(2026-06-25)
Auto-validated
never