Skip to main content
Glama
605,063 tools. Updated 2026-09-23 22:39

"Retrieving customer data from Stripe" matching MCP tools:

  • Returns the exact details to collect from the customer for a line of insurance — the same rating inputs MIB's own quote forms use. Call this FIRST, ask the customer the questions, then call compare_insurance_quotes with their answers. Omit product_type to see every line.
    ConnectorNo auth
  • Create a Stripe checkout link for an eSIM package. MANDATORY PRE-STEP: before calling this tool you MUST know the customer's BILLING/RESIDENCE country (not the travel destination). If you don't have it from the conversation, ASK the user explicitly and WAIT for the answer - do NOT guess from destination, IP, or language. Pass it as customer_country (ISO-3166-1 alpha-2). The optional activation_mode field uses internal API values only. NEVER show NOW, FIRST_USE, ON_DEMAND, activation_mode, or similar technical identifiers to the customer. Use these customer-facing names instead: Activate now, Activate on arrival, Manual activation. If the customer has not already said when they want validity to start, ask naturally: 'Would you like to activate it right now, or when you land? There is a manual option available too, but you will need to access AskMia.app settings to activate.' Use Activate now only if the customer is already at the destination, Activate on arrival for automatic activation when the phone connects at the destination, and Manual activation only if the customer explicitly wants control from AskMia.app. IMPORTANT: Worldwide/global plans do not support Activate on arrival; ask whether the customer prefers Activate now or Manual activation. MANDATORY POST-STEP: relay the returned `tax_note`, `activation_note` and `post_payment_note` verbatim before they click pay. AFTER sending payment_url you MUST STOP, then call `check_order_status` with the returned session_id; do not assume the eSIM is ready based on the user saying 'I paid'. Open access (2/min per IP), or pass a Bearer API key for 60/min.
    ConnectorNo auth
  • Use this from the customer card or browser bridge after customer_lookup verifies SMS and supplies private proof. Shared agents must use the history returned by customer_lookup or open the customer portal; an MCP connection alone never authorizes history. Searches the authenticated account records available from the customer portal by repair keywords, date text, and status. No customer IDs or portal bearer tokens are accepted. If verification expires, use customer_lookup again. Results cover only the records loaded by the portal, not a guaranteed lifetime archive.
    ConnectorNo auth
  • Complete email verification: pass the verificationId from vivid_identity_start and the 6-digit code the customer received. On success returns a short-lived identity token — pass that token to vivid_reorder / vivid_order_status to unlock the customer's private data. Codes expire in 10 minutes; attempts are limited.
    ConnectorNo auth
  • Get a company's customer-concentration risk disclosure — statements like "one customer accounted for 31% of revenue": each disclosed figure's basis (revenue or receivables), customer count, percentage, and period, with the source filing. Untagged disclosures come from verified narrative extraction with a verbatim quote; issuers that tag ConcentrationRiskPercentage in structured XBRL (e.g. NVDA, AAPL) return those customer-specific dimensioned facts directly. A miss is never a statement of no risk. Pass maxFilings > 1 to also see earlier filings' disclosures (the concentration trend).
    ConnectorNo auth
  • Attach a Stripe payment method to your Disco account. The payment method must be tokenized via Stripe's API first — card details never touch Disco's servers. Required before purchasing credits or subscribing to a paid plan. To tokenize a card, call Stripe's API directly: POST https://api.stripe.com/v1/payment_methods with the stripe_publishable_key from your account info. Args: payment_method_id: Stripe payment method ID (pm_...) from Stripe's API. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • MCP server for customer-io

  • Payments and billing on Stripe with the full official REST API (api.stripe.com), covers the entire d

  • Check the status of a Stripe checkout session created by `create_checkout`. You MUST call this after sending payment_url to the user; never trust the user's word that they paid. Returns a status (awaiting_payment | paid_processing | delivered | failed). Safe to poll every few seconds while waiting for `paid_processing` -> `delivered`. When status is `delivered` it also returns an `esim` block (package, activation code / LPA string, qr_code_image_url, iOS/Android install links, activation mode) plus `install_instructions` - show these to the customer directly in the chat, the email is only a backup. No payment or billing data is ever returned. If `failed`, give them the escalation block returned by this tool verbatim.
    ConnectorNo auth
  • Issues a single-use Stripe-Issuing virtual card hard-capped at fundedUsd, billed at funded + 25% markup + $2 service fee. PAN + CVC are returned ONCE in the response and TMV never persists them. Card auto-freezes 24h after creation. In sandbox mode (test key) cards auth only against Stripe test-mode merchants, perfect for verifying customer checkout flows without real money. Charged in credits at 1 credit = $0.10 (so a $10 funded card costs ~125 credits all-in). Provisioning fee absorbed into the markup.
    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
  • MUTATES Codat data — create a new data connection on a company for a given source platform. Provide the platformKey (from codat_list_integrations, e.g. "gbol" for QuickBooks Online sandbox). The connection is created in a PendingAuth state; the customer completes authorization via the returned linkUrl. Codat API: POST /companies/{companyId}/connections. Returns the created connection.
    Connector
    Destructive
    No auth
  • Lists all automation-enabled Data Templates (Forms) available for the current group. Use this tool first when you need to determine which Data Template (Form) should be used for a user's request, before retrieving its schema or working with submissions.
    ConnectorNo auth
  • Assemble a cart and get a Stripe-hosted checkout URL the customer opens to pay; no card data passes through the agent. Item ids come from the search tools (`diamond:<report>`, `setting:<slug>`, `jewelry:<slug>`); a complete ring is one setting plus one diamond. Needs the shipping address (prices tax and shipping into the link). Expires after 24 hours. No credential needed. Without a production credential this tool runs in the sandbox: the link is simulated and no Stripe session is created. Pass `env: "production"` when the customer actually wants to buy — that returns a live, payable link.
    ConnectorNo auth
  • Check the processing status of an inquiry previously sent with send_inquiry, using the status_token from its response. The token is issued ONLY to the inquiry's creator — possession proves ownership; there is nothing to guess or enumerate. Returns ONLY the processing status, never any customer data. Status values: novo (received, not yet read), procitano (read by the sales team), odgovoreno (the team has contacted the customer), zatvoreno (closed).
    ConnectorNo auth
  • Get saved Ideal Customer Profiles (ICPs) from Customer Hunter. Use this when the user asks about their target customer, ideal customer, customer avatar, ICP, or who they should be selling to. Returns structured profiles including nightmare scenario, dream outcome, pain points, financial profile, and tech-savviness — plus class ('customer' or 'partner') and agentProfile (how that customer's own AI assistant participates in buying: tier, agents, surfacesRead, purchasePath). Each profile also returns publicName — the public-facing audience label to use in published copy — NEVER the internal persona name/codename (the "name" field is a private targeting label). Routing: Call this before update_icp — its "id" field is the exact value update_icp needs
    ConnectorNo auth
  • Generate and send an invoice for a completed job. Auto-pushes to connected accounting software (Xero/QuickBooks/MYOB/FreshBooks), generates Stripe payment link, and notifies the customer via SMS. Full pipeline: invoice → accounting sync → payment link → customer notification → team alert.
    ConnectorNo auth
  • Draft a professional customer-support reply from a raw customer message. Tenant-agnostic: no account or ticket id needed. Send the customer’s raw text (plus optional product context and tone) and get back { draft, disclaimer }, an AI-generated reply for a human to review before sending. Nothing is stored and nothing is sent to any customer. [price: $0.05]
    ConnectorNo auth
  • Erase profile facts and consent history; retain a retraction marker. Admin scope. Already committed customer hook outputs are not silently deleted. No profile data is used for secondary learning or cross-customer retrieval today. One-way replay-key tombstones prevent delayed keyed writes from recreating the profile. Requires the current expected_version and confirm="delete". Errors: unauthorized, forbidden, not_found, conflict, idempotency_conflict, invalid_request, configuration_unavailable, rate_limited.
    Connector
    Destructive
    No auth
  • List members (Relay connection): each edge has a cursor + node (profile, Stripe customer id, unrestricted-access flag, total spend, and their subscriptions). Paginate with `first` + `after` (pass the last edge's `cursor`); `first` defaults to 50. Set `activeOnly` to return only members with an ACTIVE membership state. For member-state filters beyond active, use memberful_query. Memberful GraphQL: members connection.
    ConnectorNo auth
  • 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