Skip to main content
Glama
jsyapps

Stripe MCP Server

by jsyapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Stripe MCP Server

No user-submitted related servers found.

    Related Servers

    • Stripe MCP

      ampcome-mcps
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Stripe APIs through function calling, supporting operations on customers, products, invoices, subscriptions, and more.
      8,372 npm
      MIT

    • Stripe MCP Server

      DanFrModa
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to query Stripe data—customers, charges, subscriptions, invoices, balance, events, and more—through 17 read-oriented tools, with optional write protections and a read-only default for remote deployments.
      -

    • Stripe MCP Server

      Lokesh-2025
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.
      29 npm
      1
      MIT

    • Revenue MCP

      warfare-hub
      A
      license
      A
      quality
      F
      maintenance
      Enables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.
      5
      20 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Tools are clearly divided by resource (payment links, payment intents, products, prices, customers), but there is some potential overlap between payment links and payment intents, and between list_payment_intents and get_customer_payments. Descriptions help distinguish them, but an agent might occasionally misselect.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_payment_link, list_prices, get_customer), using lowercase snake_case throughout. This makes the API predictable and easy to navigate.

    Tool Count4/5

    17 tools is slightly above the ideal range but still appropriate for Stripe's domain, covering payment links, intents, products, prices, and customers. Each tool addresses a distinct need, though a few could be consolidated without loss.

    Completeness3/5

    Core CRUD operations exist for payment links, products, and customers, but are incomplete: products and customers lack update/delete, prices lack a get endpoint, and payment intents lack cancel/refund capabilities. This creates workflow gaps for managing the full lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources