Skip to main content
Glama
687,020 tools. Updated 2026-10-22 08:07

"Stripe" matching MCP tools:

  • THE answer to 'is <service> connected?' - every connected account/instance this company has (service, instance, accountId, region), filterable with `service` and narrowed with `match` (looking for one plane's instance? pass `match` - the full list is ~50 rows). 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 a billing portal URL for the authenticated company. Use this when a human needs to update a payment method, view invoices, or change an existing subscription. Requires a company API key (aa_...) or an MCP OAuth access token. Returns url when Stripe is configured and the company has a Stripe customer. The call itself does not change the plan or charge a card. When local billing bypass is enabled, Stripe is not called and url is the console URL. If Stripe is not configured or the company has no Stripe customer, the JSON includes error stripe_not_configured. To buy Pro, use billing_checkout. billing_machine_pay only returns prepaid REST instructions.
    ConnectorAPI key
  • Store the app's Stripe API credentials so billing (checkout, subscriptions, the billing portal) works. Arguments: secretKey (the Stripe SECRET key, "sk_live_..." or "sk_test_...") and publishableKey (the Stripe publishable key, "pk_live_..." or "pk_test_..."). Both are found in the Stripe dashboard under Developers > API keys. Ask the user for these — never invent or guess a key. Returns { connected, webhookConfigured } and nothing else: the keys are never echoed back. connected=false means the credentials were stored but Stripe did not confirm them, so re-check the keys. webhookConfigured=false means Stripe events will not reach Bridge; see get_stripe_status. Use get_stripe_status to check the current state without writing. IMPORTANT: this stores the credentials but does NOT enable payments — Stripe stays switched off until setup_payments turns it on. For first-time setup prefer setup_payments, which does both. Use this only to rotate keys on an app where payments are already enabled. Before writing app code that consumes this, call get_integration_guide with topic=billing and the framework the app uses.
    ConnectorOAuth
  • Connect Stripe to the Bridge app in one step: stores the Stripe API credentials AND turns payments on, so checkout, subscriptions and the billing portal start working. Arguments: stripeSecretKey (the SECRET key, "sk_live_..." or "sk_test_...") and stripePublicKey (the publishable key, "pk_live_..." or "pk_test_..."), both from the Stripe dashboard under Developers > API keys. ASK THE USER FOR THESE — never invent, guess, or reuse a key from another context. The keys are never echoed back in the result. This does NOT create any plans; use create_plan / set_plan_price for those, and list_plans to see what exists. Prefer this over connect_stripe when setting billing up from scratch: connect_stripe only stores the keys and leaves Stripe disabled. Check the returned stripeSetupStatus — "failed" means Stripe rejected the credentials or Bridge could not set up its Stripe webhook, and stripeSetupError says why. webhookConfigured=false means subscription changes, cancellations and payment failures made in Stripe will not reach Bridge; calling setup_payments again with the same keys re-runs setup and replaces the webhook endpoint. Before writing app code that consumes this, call get_integration_guide with topic=billing and the framework the app uses.
    ConnectorOAuth
  • 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

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.
    18,973 npm
    1,965
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables read-only querying of payments and billing data via the full official REST API, covering customers, charges, payment intents, subscriptions, invoices, refunds, and more.
    MIT

Matching MCP Connectors

  • 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
  • Pay a quoted job. method=stripe returns a Stripe Checkout URL (cards + PayNow). method=x402 (default) returns x402 v2 payment requirements (USDC on Base); pay, then call again with the PAYMENT-SIGNATURE header or _meta["x402/payment"] to settle. Work starts only after payment is verified AND settled.
    ConnectorNo auth
  • Use when the user names a company and wants its current open roles, e.g. "is Stripe hiring engineers in London?" or "list this company's remote jobs". Reads the public Greenhouse, Lever or Ashby job board and returns title, location, department, remote flag, job URL and posting date, newest first. company = board slug (stripe in boards.greenhouse.io/stripe); if not found on one ATS, retry the other two. For companies newly hiring across the market use list_hiring_signals.
    ConnectorNo auth
  • Starts connecting Stripe to a page. Returns a link for the person to open and approve — nothing is connected until they do, and no password or key is ever passed through here. Check list_connectors afterwards. The Stripe account's country cannot be changed after it is created, so confirm it with the person before calling.
    ConnectorAPI key
  • Open a billing URL for an explicitly selected eligible plan. After human confirmation, a Free account without a subscription receives a one-hour Stripe Checkout URL; an existing subscriber receives Stripe billing management instead. Plans not offered to the account are refused. Cancellation creates nothing and account identifiers are never accepted from the model.
    ConnectorNo auth
  • 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
  • Create a Stripe Checkout session for the authenticated company so a human can subscribe to Pro, monthly or yearly (optional interval month or year). Requires a company API key (aa_...) or an MCP OAuth access token. It does not accept a console session or a bootstrap token, and it does not mint a company or an aa_ secret. Returns url. Creating the session does not charge a card; the human pays on the Stripe page. When local billing bypass is enabled, there is no Stripe call and no charge: Pro is granted immediately with no period end, and url is the console success URL (/console?billing=ok), not a Stripe Checkout URL. If Stripe is not configured and bypass is off, the JSON includes error stripe_not_configured. For prepaid purchase instructions, use billing_machine_pay. To manage an existing subscription, use billing_portal.
    ConnectorAPI key
  • Payment helpers. Use action=machine_pay to learn how to unlock Pro or buy an agent SKU with Stripe Machine Payments. Returns sku, amount, currency, periodDays, and the POST URL the agent must call with an MPP Payment credential. This call does not charge. Default sku is pro_prepaid_30d. Use action=portal for a Stripe Customer Portal URL (subscription and invoices, for a human). Returns {url}. Fails when the account cannot open a portal. Use action=purchases to list local MPP purchases and logged Stripe events. Returns purchases and a cursor. Pass includeStripe=true to merge unlogged Stripe charges when a customer exists. No quota spend and no email. Sibling bootstrap_agent creates the account first. get_usage reads quotas. ACL is not consulted (billing_machine_pay, billing_portal, and billing_purchases_list were ungated).
    ConnectorAPI key
  • Tip the pro for one of the client's own appointments (id from my_bookings), in dollars. Returns a secure Stripe payment link to give the client; the tip goes straight to the pro's own Stripe account. Only when the client asks to tip, and only for pros who take tips online.
    ConnectorNo auth
  • Payments the user's customers made for bookings on the user's own website (Stripe via oriiion): totals, last 30 days, fees, the latest payments with receipt links, and a one-time link to their Stripe dashboard with every receipt, payout and report. Use when the user asks about payments, receipts, payouts, revenue from bookings, or their Stripe account. Not their oriiion subscription — that is get_billing_status.
    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
  • 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