Skip to main content
Glama
joeyaflores

revenuecat-charts-mcp

by joeyaflores
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rc_list_metricsA

List all available RevenueCat Charts API metrics with descriptions. Use this to discover what subscription data you can query before calling rc_get_chart.

Args:

  • category (string): Filter by category — "all", "revenue", "actives", "trials", "conversion", or "cohorts" (default: "all")

Returns: Markdown-formatted list of metrics grouped by category, each with metric name (for use in rc_get_chart) and description.

Examples:

  • "What metrics can I query?" -> category="all"

  • "Show me revenue metrics" -> category="revenue"

  • "What trial data is available?" -> category="trials"

rc_get_overviewA

Get a real-time snapshot of key subscription health metrics. No date range needed — returns current state.

Args:

  • api_key (string): RevenueCat secret API key starting with "sk_"

  • project_id (string, optional): RevenueCat project ID (e.g., "proj058a6330"). Auto-detected if omitted.

Returns: Markdown summary with: Active Trials, Active Subscriptions, MRR ($), Revenue (28d), New Customers (28d), Active Users (28d), Transactions (28d).

Examples:

  • "What's my current MRR?" -> call with just api_key

  • "Give me a subscription health check" -> call with just api_key

  • "How many active subscribers do I have?" -> call with just api_key

rc_get_chartA

Query any RevenueCat Charts API metric as a time series. Returns formatted markdown table with dates, measures, and summary statistics.

Supports 21 metrics across revenue, subscriptions, trials, conversion, and cohorts. Use rc_list_metrics to discover available metrics.

Args:

  • api_key (string): RevenueCat secret API key starting with "sk_"

  • metric (string): Chart metric name. Common values: "mrr", "revenue", "churn", "actives", "trials", "trial_conversion_rate", "ltv_per_customer"

  • start_date (string): Start date in YYYY-MM-DD format

  • end_date (string): End date in YYYY-MM-DD format

  • resolution (string, optional): "day", "week", or "month" (default: "month")

  • segment (string, optional): Dimension to segment by (e.g., "country")

  • project_id (string, optional): RevenueCat project ID. Auto-detected if omitted.

Returns: Markdown with chart description, period, resolution, summary statistics, and a data table. Multi-measure charts (like churn) include all measures as columns. Segmented charts show top 10 segments as columns.

Examples:

  • "Show me MRR for 2025" -> metric="mrr", start_date="2025-01-01", end_date="2025-12-31"

  • "What's my churn week over week?" -> metric="churn", resolution="week"

  • "Break down revenue by country" -> metric="revenue", segment="country"

  • "How are trial conversions trending?" -> metric="trial_conversion_rate"

Error Handling:

  • Invalid metric: returns list of valid metric names

  • Rate limited: auto-retries up to 3 times with backoff

  • Invalid date format: returns error with expected format

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: rc_list_metrics for discovering available metrics, rc_get_overview for a real-time snapshot of key metrics, and rc_get_chart for time-series queries of any metric. The overlap between overview and chart is minimal—one is a fixed snapshot, the other is flexible time series—so misselection is unlikely.

Naming Consistency5/5

All tools share the rc_ prefix and follow a consistent verb_noun pattern: list_metrics, get_overview, get_chart. The use of 'list' for enumeration and 'get' for data retrieval is natural and consistent.

Tool Count5/5

Three tools is well-scoped for a read-only RevenueCat Charts API server. Each tool covers a distinct need: discovery, snapshot, and time-series querying. No superfluous tools, and the count is appropriate for the narrow domain.

Completeness5/5

The tool set fully covers the core functionality of the RevenueCat Charts API: listing available metrics, getting a quick health snapshot, and querying any metric as a time series. There are no obvious dead ends—the overview covers common key metrics, and the chart tool covers all supported metrics. For a read-only API, this is complete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources