Skip to main content
Glama
warfare-hub

Revenue MCP

by warfare-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Revenue MCP

No user-submitted related servers found.

    Related Servers

    • Indie Founder Revenue MCP

      charlie-morrison
      A
      license
      Not graded
      quality
      D
      maintenance
      Aggregates revenue across Lemon Squeezy + Gumroad + Polar + Stripe into a single Claude-queryable view. Six tools: summary_mrr, top_customers, refund_signal, recent_orders, export_csv_for_tax (Ukrainian FOP format), health. Lemon Squeezy adapter live-validated against production.
      MIT

    • stripe-analytics-mcp

      npow
      A
      license
      A
      quality
      F
      maintenance
      Provides real-time Stripe subscription analytics including MRR, churn, failed payments, and expiring trials. Enables AI assistants to answer business health questions like 'How's my business doing?'
      8
      MIT

    • saas-brain-mcp

      Mohd16kaif
      F
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server for Claude AI that connects Stripe and Supabase to enable natural language SaaS analytics, including churn analysis, subscription tracking, and revenue insights.
      -

    • Stripe MCP Server

      jsyapps
      A
      license
      C
      quality
      D
      maintenance
      Enables Claude to integrate with Stripe for creating payment links, processing payments, and managing products and customers.
      17
      41 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.
      -
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool focuses on a distinct aspect of revenue data: product breakdown, churn summary, overall summary, MRR by platform, and recent revenue. There is no overlap in their purposes.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix and snake_case pattern, making it predictable for an agent to infer functionality.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a revenue analytics domain, covering key metrics without being overwhelming or sparse.

    Completeness5/5

    The tool set covers essential revenue metrics: summary, breakdowns by product and platform, churn, and time-based revenue. No obvious gaps for basic revenue analysis.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources