indie-metrics-mcp
Related Servers
Alternatives to indie-metrics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.536 npmMIT
- FlicenseAqualityDmaintenanceEnables natural language querying of Google Analytics 4, Google Search Console, Meta Ads, and Google Ads data through Claude.23-
- AlicenseNot gradedqualityAmaintenanceEnables querying and analyzing marketing data from Google Analytics 4, Search Console, YouTube, and optionally Google Ads and Meta Ads, stored in a unified DuckDB database, via natural language in Claude.1MIT
- AlicenseAqualityAmaintenanceEnables AI agents and Claude Code to query podcast download analytics from OP3, including unique listeners, retention cohorts, audience geography and apps, episode performance, and show comparisons via natural language.2228 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides statistical analysis and usage tracking for Claude Code, enabling users to query daily/monthly stats, compare users, analyze trends, detect anomalies, and generate usage reports through natural language.1-
- AlicenseAqualityDmaintenanceMCP server for Claude Desktop that exposes App Store Connect and RevenueCat APIs, enabling indie iOS developers to query portfolio metrics, sales reports, subscriptions, and customer reviews directly in chat.17MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct metric/data source: App Store downloads, App Store proceeds, RevenueCat subscriptions, RevenueCat project listing, and PostHog events. The only mild overlap is downloads vs proceeds, which share the same parameter shape and source, but the descriptions make the metric difference explicit. revenuecat_projects is clearly a helper for subscribers, which is stated in both descriptions.
All names are lowercase snake_case nouns, which is consistent and readable. The minor deviation is that one tool carries a vendor prefix (revenuecat_projects) while the sibling RevenueCat tool (subscribers) and the other source-specific tools (downloads, proceeds, events) do not, so the source-to-name mapping is slightly uneven.
Five tools is well-scoped for a compact cross-source metrics server: one per metric plus a project-discovery helper. No redundant or trivial tools, and each has a clear job.
Coverage spans three sources but is thin within each: App Store lacks ratings/reviews/refunds, RevenueCat lacks a revenue breakdown or churn detail beyond the summary, and PostHog has only event counts. A notable asymmetry is that RevenueCat has a project-discovery tool (revenuecat_projects) but PostHog's events requires a numeric project id with no tool to list PostHog projects, creating a dead end for agents that don't already know the id.