Skip to main content
Glama
649,985 tools. Updated 2026-10-11 00:06

"Guide to Coding and Implementing Stripe Elements" matching MCP tools:

  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • 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
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    ConnectorNo auth
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    ConnectorNo auth
  • Create up to 100 whiteboard elements in one transactional call (all-or-nothing, one realtime event). Native sizes, colors, and text placement are applied server-side — usually give just type + text (+ color). Omit x/y and elements are auto-arranged (grid by default; arrange: row|column|grid, origin_x/origin_y/gap to tune); give x/y for full control. Frames contain elements via parent_id (an existing frame uid) or parent_ref (the ref of a frame earlier in THIS call). Connectors bind elements by uid (source_id/target_id) or batch ref (source_ref/target_ref) — never coordinates; anchors are computed by the UI. Requires a Pro or trial workspace.
    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.
    21,341 npm
    1,865
    -
  • 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.
    39 npm
    MIT

Matching MCP Connectors

  • Research intensity for 118 elements and topics, ~10M papers. Free element scores; x402 pay-per-call.

  • Suggest ICD-10-CM codes from a diagnosis description. Returns ranked codes with confidence, reasoning, coding notes, differential alternatives.

  • Create a Stripe Checkout session for the authenticated company so a human can subscribe to Pro. 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
  • 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
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    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
  • Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.
    ConnectorNo auth
  • Mamanida's editorial buying guides for one storefront, in that storefront's own language. Called without `guide` it lists the published guides (metadata only: title, deck, meta description, pillar, topics, dates and the canonical Mamanida URL), optionally filtered by `topic`. Called with `guide` (the guide slug from the listing) it returns that one localized edition plus its structured body: paragraphs, headings, lists, comparison tables, callouts, links to other guides and category calls-to-action. A `category_cta` gives a `category_slug` you can pass straight to search_products, which is the intended guide → category → product path. Retailer and affiliate URLs are never returned.
    ConnectorNo auth
  • Return the user's personalization guide — how they want a person researched before you write to them. Call this only when you are going to personalize a message; follow the returned guide. When none is set, returns a note and you should fall back to the default research rules in the outreach craft skill.
    ConnectorOAuth
  • 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
  • Start a purchase of the full paid SEO Remediation Guide for a COMPLETE scan ($8.99). Returns a Stripe `checkout_url` — payment CANNOT be collected through this tool. AUTONOMOUS FLOW: after calling this, do NOT stop and wait for a new user instruction. (1) Show the user `checkout_url` and ask them to complete payment in their browser. (2) Then poll `get_purchase_status` with the same scan_id about every 15 seconds: while `paid` is false the user hasn't finished — keep waiting (poll for up to a few minutes). (3) Once `paid` and `runbook_ready` are both true, call `get_remediation_plan` once, save the returned markdown to the file it names, and begin the remediation automatically — no further prompting needed. If this call returns already_purchased=true, skip the wait and go straight to get_remediation_plan.
    ConnectorNo auth
  • 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
  • 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