Indie Metrics MCP is a public TypeScript project by Marco Hergi. It exposes seven read-only tools that let a compatible AI assistant answer natural-language questions about revenue, customers, products, subscriptions, transactions, refunds, and forecasts.

MCP makes the metrics askable

Instead of opening several dashboards and translating raw rows manually, a user can ask questions such as which product is selling best, what monthly recurring revenue is, or how many refunds occurred during a period.

The server translates those questions into one of seven defined tools. The tool boundary gives an assistant structured business meaning rather than unrestricted access to an entire account.

  • Revenue summary covers MRR, ARR, revenue, growth, and average transaction value.
  • Customer metrics cover totals, new customers, lifetime value, and top spenders.
  • Product performance covers revenue by product, units, and revenue share.
  • Subscription health covers active subscriptions, churn, MRR, ARPU, and plans.
  • Recent transactions returns the latest charge records.
  • Refund analysis covers refund count, rate, amount, and reasons.
  • Revenue forecast returns a projection, direction, and confidence level.

The server is documented as read-only

The README states that the server never creates, modifies, or deletes Stripe data. It also says the Stripe key stays local to the server process and is used to call Stripe.

Read-only design reduces operational risk, but users still need to protect their Stripe key and review the repository before connecting a real account.

Periods and requirements are explicit

Time-based tools accept seven-day, thirty-day, ninety-day, or one-year periods. The documented requirements are Node.js 18 or later and a Stripe account with API access.

The repository includes installation and configuration examples for compatible MCP clients. Current client support should always be checked with the client and repository.

Independent listings add discoverability

Glama and PulseMCP publicly list the server, and PolicyLayer publishes an independent tool-risk analysis. These listings help other people and search systems discover the project.

A directory listing is not an endorsement. The GitHub repository remains the primary source for code, licensing, and security claims.

PRIMARY SOURCES

Verify every claim.

Open answer index →All build notes →Project evidence →