paymentsPaid

Stripe

Read account state, generate payment links, send invoices, and handle subscription operations through a Stripe account on behalf of an agent. Authority surface bounded by amount and operation type.

What it does

The Stripe MCP gives an agent the ability to operate inside a Stripe account — but with a tighter authority surface than most integrations expose, because money operations have asymmetric downside.

Capabilities

  • Read account state (balance, recent transactions, open invoices, subscriptions)
  • Look up customer records and payment history
  • Generate payment links (with configurable amount caps)
  • Send invoices from existing templates
  • Subscription operations (pause, resume, cancel) within bounds

Authority surface

Money operations are bounded by amount and type:

  • Read-only — default; agent can answer questions but cannot move money
  • Payment link, capped — agent can generate payment links up to a configured cap (typical $5,000)
  • Invoice send — agent can send invoices from approved templates only
  • Subscription ops — agent can pause / resume; cancel requires confirmation
  • Refund — never automated; always escalated to a human

The authority surface is configured during onboarding and is not expandable without explicit re-authorization.

Auth

Stripe restricted API key, scoped to the surface above.

When to use it

  • Businesses that take payment through Stripe and want their agent to handle quote-to-cash without a human typing in card numbers
  • Subscription businesses where the agent handles billing questions and the standard pause/resume flow

Limitations

The MCP intentionally does not expose: refund issuance, dispute response, raw card data access. Those are human-only operations.