Skip to main content
Glama
juansalas22

stripe-ops-mcp

by juansalas22

Related Servers

Alternatives to stripe-ops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to safely inspect Stripe billing data such as subscriptions, invoices, failed payments, and churn, with read-only access, per-tool permissions, and a tamper-evident audit log.
      2 npm
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Read-only Stripe finance, ops, and risk reporting exposed via MCP, HTTP API, and CLI. Enables querying balances, payments, customers, payouts, reconciliation, and risk alerts without mutating Stripe state.
      MIT
    • 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,607 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.
      28 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing charges, detecting duplicates, summarizing revenue, and fetching customer profiles. No overlap in functionality; an agent can easily select the right tool for the job.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but three follow a verb_noun pattern (list_, find_, get_) while revenue_summary is a noun-only phrase. Minor inconsistency, yet still predictable and readable.

    Tool Count4/5

    Four tools is slightly on the lower side, but the set is tightly scoped to stripe operations monitoring. The count feels acceptable rather than overly thin for a focused utility.

    Completeness2/5

    The tools cover only read/analytics operations: listing charges, detecting duplicates, revenue summaries, and customer lookup. Missing obvious operational capabilities like creating refunds, retrieving charge details, or managing customers/subscriptions, leaving significant gaps for real-world ops.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues