Skip to main content
Glama
306,578 tools. Last updated 2026-07-25 15:19

"Retrieving customer data from Stripe" matching MCP tools:

  • 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.
    Connector
  • 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.
    Connector
  • Sends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads) — this is not a draft and reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]
    Connector
  • 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.
    Connector
  • See your plan and get a link to manage, switch, or cancel your paid Bassethound subscription. Call this when the user wants to cancel, update their payment method, view invoices, move between Pro and Business, or check which plan they're on. A paid user gets a Stripe Customer Portal link — Stripe hosts all billing management, and cancelling there keeps the plan active until the end of the billing period; a free user is told how to upgrade.
    Connector
  • 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.
    Connector

Matching MCP Servers

  • A
    license
    -
    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.
    Last updated
    12,199
    1,700
  • A
    license
    -
    quality
    C
    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.
    Last updated
    25
    MIT

Matching MCP Connectors

  • MEOK Stripe ACP Checkout MCP — ChatGPT shopping bridge. Issues + verifies + signs Stripe Agentic

  • Bright Data MCP — Bright Data Web Unlocker + SERP API (brightdata.com)

  • 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, period, and verbatim filing quote, with the source filing. Figures come from verified extractions of the filings' own narrative text and cover only filers who leave the disclosure untagged — issuers that tag it in structured XBRL (e.g. NVDA, AAPL) are skipped by design and answered with a pointer to GetFinancialFact's 'customer-concentration' concept. A miss is never a statement of no risk. Pass maxFilings > 1 to also see earlier filings' disclosures (the concentration trend).
    Connector
  • <tool_description> Settle pending payments for media buys. Supports manual CSV export, Stripe invoice (Phase 2 stub), and x402 micropayments (Phase 2 stub). </tool_description> <when_to_use> When a publisher wants to collect earned revenue or an advertiser needs to settle outstanding charges. Use method='manual' for CSV export. Stripe and x402 are stubs (Phase 2). </when_to_use> <combination_hints> get_campaign_report → settle (after verifying amounts). Filter by media_buy_id, publisher_id, or period. </combination_hints> <output_format> Settlement totals (gross, platform fee, net), entry count, and method-specific data (CSV for manual). </output_format>
    Connector
  • Get customer testimonials tied to a specific project (by slug or keyword) from the testimonials table. Returns star rating, customer name, project name, and quote text. Use to source social proof or case-study quotes for a particular job. For unfiltered reviews, use list_reviews.
    Connector
  • 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.
    Connector
  • 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.
    Connector
  • 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.
    Connector
  • Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.
    Connector
  • Return the agent payment manifest: every way to pay (HTTP 402 + Bearer key, MCP, Stripe checkout, x402, RSL per-crawl), the exact 402 retry loop, what is always free, and the recommended path per use case. Same data as /api/payment.json.
    Connector
  • Create a lead: ask a specific locksmith for a quote. ONLY call this when the user has chosen a provider and wants to be contacted — it sends a real request to the locksmith. Provide a phone (preferred) or email so the locksmith can reach the customer. Returns a reference id (HL-####); the locksmith confirms availability, price, and ETA directly. Args: locksmith_id: id from search_locksmiths / get_locksmith. name: Customer name. phone: Customer phone (preferred). Phone OR email is required. email: Customer email (alternative to phone). zip: 5-digit ZIP of the job (improves routing/records). service: Job type, e.g. "lockout", "automotive". details: Free-text description of the job. urgency: e.g. "emergency", "today".
    Connector
  • Ask the directory a customer question in natural language. Returns schema.org cards of businesses that genuinely answer it (LLM-reranked, strictly from the directory — never invented) + grounding links. Use when the customer describes a NEED rather than a search term.
    Connector
  • List ranked REAL Customer Evidence for this company (paying > telemetry > review > relayed > agent_as_user > prospect). Use before customer-facing work or when asked what real customers have said. Empty + company has ICPs = LOUD EMPTY (sim only — do not treat generated ICP as a customer).
    Connector
  • Check current billing status including whether billing is set up, credit balance, Stripe customer ID, and payment method status. Use this to determine if billing setup is needed before making paid API calls.
    Connector
  • Check a public registry package before install or version bump — frameworks (next, react, vite), payments (stripe), auth (next-auth, clerk), ORMs (prisma, drizzle). task=check: exists, slopsquat, deprecation, CVEs (pass version); task=upgrade|migrate: breaking_changes + migration_steps from release notes; task=security: CVEs for your version. Returns summary, data, next_calls, meta.credits (5 hosted). No project path — just package name + version. Call BEFORE npm install or bumping next/stripe/prisma. NOT for repo layout (get_project_context), import search (find_code), tests (check_test), architecture (explain_architecture), live URLs (audit_headers). Example: check_package({ package: 'next', task: 'upgrade', from_version: '14.2.0' }). Read-only.
    Connector
  • Find a person's professional profile by name (+company) via Coresignal — returns title, current company, location, LinkedIn URL, work experience and education. LinkedIn-adjacent people data. Example: coresignal_employee({ name: "Patrick Collison", company: "Stripe", _apiKey: "your-key" })
    Connector