Skip to main content
Glama
569,274 tools. Updated 2026-09-14 22:20

"stripe" matching MCP tools:

  • Expert developer playbooks — not your repo. Stripe webhooks & checkout, Supabase RLS, Next.js auth (clerk, next-auth), payment flows, CSP/HSTS, deploy patterns. operation=search finds entries by question; operation=get returns full guidance by slug from search. Read summary and checklist first. 2 credits hosted. No project path. Call when standard patterns beat guessing — wiring stripe checkout, fixing auth middleware, Supabase RLS policies, hardening after audit_headers. Use AFTER repo tools if code context is still thin. NOT for user's codebase (get_project_context, find_code, read_code), registry packages (check_package), tests (check_test), live URL (audit_headers), or saving decisions (project_memory). Example: Zephex_dev_info({ operation: 'search', query: 'Stripe webhook raw body verification', category: 'payments' }) then get with returned slug. Read-only.
    ConnectorNo auth
  • Start (or resume) Stripe Connect onboarding so this account can RECEIVE author royalties. Returns a one-time onboarding_url the human author must open in a browser to complete KYC. Required before a book can be published: an author with no payouts-enabled Connect account can save drafts but their books stay in draft until onboarding finishes. Payouts stay disabled until Stripe verifies the details — poll connect_status afterward.
    ConnectorNo auth
  • Check if a domain is available for purchase and get its price. Always call this before buying. After showing the price, ask the user two things before proceeding: 1. Confirm they want to purchase at that price. 2. Which payment method they prefer: - "card" / "Stripe" → call buy_domain (opens Stripe checkout in browser) - "crypto" / "USDC" / "x402" → call buy_domain_crypto (autonomous USDC payment, no browser; requires Coinbase Payments MCP or another x402 wallet) - "MPP" / "agent pay" → call buy_domain_mpp (Stripe agent payments via Shared Payment Token, no browser) If the user has Coinbase Payments MCP configured in their session, suggest crypto as the default. Otherwise default to buy_domain (Stripe). Args: domain: The full domain name to check (e.g. "coolstartup.com"). Returns: Dict with availability status, price in cents, and formatted price.
    ConnectorNo auth
  • Buy more credits to fund test runs that TestMyVibes' agents will execute on your behalf. Returns a Stripe Checkout URL the user must open to complete payment (Stripe requires human payment completion per their agentic-commerce policy). Once the user pays, the credits are added automatically by the Stripe webhook — poll get_credit_balance to confirm.
    ConnectorNo auth
  • Return the seller's Stripe Connect state: not_started | in_progress | pending_verification | ready | disabled. When status != 'ready' the user can't list sites. Includes a one-shot onboardingUrl (if not_started or in_progress) and dashboardUrl (if ready). Refreshes from Stripe on every call.
    ConnectorNo auth
  • Completa una sesión de checkout UCP. Sin manejador de pago nativo: si checkout.payment.instruments[] trae una credencial Shared Payment Token de Stripe (handler_id 'stripe', credential.token 'spt_…') se cobra y se entrega al instante; si no, la sesión pasa a requires_escalation y el comprador termina en continue_url. Un informe incluido en el plan se completa sin cobro. Requiere meta['idempotency-key'] además de meta['ucp-agent'].
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
    8,372 npm
    1,799
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for the Stripe API with 10 tools covering payments, customers, invoices, and subscriptions. Generated with MCPForge. Destructive and financial operations require human approval.
    15 npm
    MIT

Matching MCP Connectors

  • Transmit a fax. Two ways to pay: (1) human-in-the-loop — pass the payment_id from create_fax_payment after the human has paid the Stripe Checkout link; (2) autonomous machine payment (x402/MPP) — call WITHOUT payment_id and the server replies with a payment challenge (JSON-RPC error -32042) for USDC-on-Tempo or a Stripe Shared Payment Token; pay it and retry with the credential in _meta['org.paymentauth/credential']. Either way the server verifies the payment covers the server-computed price of the actual content before sending via a real fax carrier. One fax per payment; card/Checkout and Stripe machine payments are refunded automatically if the fax fails to send or deliver (on-chain payments are refunded manually).
    ConnectorNo auth
  • THE answer to 'is <service> connected?' - every connected account/instance this company has (service, instance, accountId, region), filterable with `service`. Pass an instance as connections_execute's `instance` to target one. Two kinds: a normal row holds a credential in this vault; a kind:'brokered' row is owned by ANOTHER first-party plane (named in `via`) that holds the credential - notably every Stripe account linked through Pay, which you reach with Pay endpoints per the row's `callWith`, NOT with service:'stripe'. Stripe can appear BOTH ways at once and they are different accounts: a brokered row is Pay's Connect link, while a normal stripe row is a secret key this workspace pasted directly and IS called with service:'stripe' as its own instance - so read the row's `kind` before choosing how to call it. A `brokeredUnavailable` field means that plane could not be reached, so the list is INCOMPLETE - never read it as 'not connected'.
    ConnectorOAuth
  • Create or resume an owner-bound hosted Stripe checkout for a current plan from list_plans. Requires business_id, plan_id, and a durable idempotency_key. Reuse the same key for retries; a changed plan requires a new key. The owner must open the returned link and authorize payment in Stripe. This tool never proves payment or phone activation. After checkout, use get_checkout_status with the returned session_id.
    ConnectorOAuth
  • Oppretter en Stripe Checkout-lenke for valgte produkter og leveringsmåte. Kunden åpner lenken selv og fyller inn adresse og betaling der; ingenting belastes før kunden betaler på Stripe-siden. Lenken gjelder i 24 timer. Priser hentes fra butikken (ikke fra deg), frakt fra postnummeret, mva beregnes av Stripe. delivery_method: pickup (henting i Hamar, ingen frakt), hentested eller hjemlevering (krever shipping_postcode). Kjøpsvilkår: https://ferbu.no/kjopsvilkar
    ConnectorNo auth
  • Retrieves live payment data from a Stripe account via the Stripe API. Supports four query types: recent_payments returns the latest payment intents with status, amount, and currency; failed_charges returns declined or failed charges with failure reasons and error codes; customers returns customer records with name, email, and payment method details; subscriptions returns active and cancelled subscription plans with billing interval and status. Use stripe_payments when an agent needs to investigate payment failures, audit recent transaction activity, retrieve customer billing records, or check subscription status within a Stripe account — it returns full Stripe charge objects with customer IDs, metadata, and processing details. Prefer stripe_payment_records for a lighter-weight Stripe query returning only a simple records array without full Stripe object structure. Do not use for bank account transactions or PSD2 Open Banking data — use open_banking_transactions instead. Do not use for generic bank account history — use bank_accounts instead. Requires a Stripe secret key to be configured on the server.
    ConnectorNo auth
  • Return aggregate active live-mode subscription count, MRR minor units, and plan mix. No account or Stripe identifiers are exposed.
    ConnectorNo auth
  • Create a Stripe Checkout link for a new paid subscription, or a Stripe Billing Portal link for an existing Stripe subscription. Use only after the user explicitly asks to upgrade or fix billing.
    ConnectorNo auth
  • Retrieves live payment data from a Stripe account via the Stripe API. Supports four query types: recent_payments returns the latest payment intents with status, amount, and currency; failed_charges returns declined or failed charges with failure reasons and error codes; customers returns customer records with name, email, and payment method details; subscriptions returns active and cancelled subscription plans with billing interval and status. Use stripe_payments when an agent needs to investigate payment failures, audit recent transaction activity, retrieve customer billing records, or check subscription status within a Stripe account — it returns full Stripe charge objects with customer IDs, metadata, and processing details. Prefer stripe_payment_records for a lighter-weight Stripe query returning only a simple records array without full Stripe object structure. Do not use for bank account transactions or PSD2 Open Banking data — use open_banking_transactions instead. Do not use for generic bank account history — use bank_accounts instead. Requires a Stripe secret key to be configured on the server.
    ConnectorNo auth
  • Complete payment using Stripe ACP (Shared Payment Token). Only use this if your platform supports Stripe Agentic Commerce Protocol and can provision an SPT. If your platform does NOT support ACP, use the `payment_url` from checkout_create instead, then poll checkout_status. Requires authentication.
    Connector
    Destructive
    No auth
  • Complete payment using Stripe ACP (Shared Payment Token). Only use this if your platform supports Stripe Agentic Commerce Protocol and can provision an SPT. If your platform does NOT support ACP, use the `payment_url` from checkout_create instead, then poll checkout_status. Requires authentication.
    Connector
    Destructive
    No auth
  • Create an immutable USD-to-CPTM quote for the calling registered parent agent or an intentional gift target, then return a short-lived Stripe Checkout URL for browser handoff. Requires an Authorization: Bearer header and idempotency_key. Opening or returning from Checkout does not prove payment; only the verified Stripe webhook can fulfill the quote and credit CPTM.
    ConnectorNo auth
  • List subscriptions on a Stripe account via the Stripe API (api.stripe.com/v1/subscriptions), authenticated with a Stripe secret or restricted key passed as _apiKey, with optional customer id and status filters (active, canceled, past_due, trialing, unpaid) and a limit of 1-100. Returns each subscription id, customer, price and plan items, status, and current period start and end. Answers who is subscribed to a Stripe billing plan and on what terms.
    ConnectorNo auth
  • Get a Stripe Billing Portal URL for the human to manage their subscription — update payment methods, view invoices, change plans, or cancel. Requires an existing Stripe subscription.
    ConnectorNo auth
  • Create a Stripe Checkout link for a new paid subscription, or a Stripe Billing Portal link for an existing Stripe subscription. Use only after the user explicitly asks to upgrade or fix billing.
    ConnectorNo auth