indie-metrics-mcp
Ask Claude how your apps are doing. This is a small MCP server that reads your own App Store Connect sales, RevenueCat subscribers and PostHog events, and answers with this week against last week. It runs on your machine with your keys.
Shipping an app and want the checklist? The App Store launch kit.
Tools
| Tool | Answers |
|---|---|
downloads(app?, days) |
First-time downloads, last days against the days before (App Store Connect Sales and Trends) |
proceeds(app?, days) |
Developer proceeds by currency, same two windows |
revenuecat_projects() |
Your RevenueCat project ids |
subscribers(project, days) |
Active subscriptions, trials, MRR and 28-day revenue now; active subscriptions at the end of each window |
events(project, names?, days) |
PostHog event counts, same two windows (HogQL) |
days is 1 to 30. Windows are whole days ending yesterday. Apple's report days are Pacific time; PostHog days are UTC. Apple posts a day's report the next day, so a missing day is listed under days_without_report.
Install
From the first release (not on PyPI yet), one line, no clone:
claude mcp add indie-metrics -- uvx indie-metrics-mcp
This needs uv. Get your keys as in steps 4 to 6 below. Pass them with -e NAME=value on claude mcp add, or use the Keychain items from step 7. The clone steps below work today and stay as the second route.
Set up (from a clone)
- Install Python 3.10 or newer.
git clonethis repository andcdinto it.python3 -m venv .venv && .venv/bin/pip install .- App Store Connect: in Users and Access, Integrations, create a key with the Sales role. Download the
.p8file and note the key id, the issuer id and your vendor number (Payments and Financial Reports). - RevenueCat: create a v2 secret API key with read-only access to projects, customers and charts.
- PostHog: create a personal API key with read access to query. Note your numeric project id.
- Give the server your keys as environment variables or as macOS Keychain items (service
indie-metrics.<NAME>;security add-generic-password -s indie-metrics.<NAME> -a "$USER" -wprompts for the value). Names:ASC_KEY_ID,ASC_ISSUER_ID,ASC_KEY_PATH(path to the.p8),ASC_VENDOR_NUMBER,REVENUECAT_API_KEY,POSTHOG_API_KEY, and optionallyPOSTHOG_HOST(defaulthttps://us.posthog.com; usehttps://eu.posthog.comfor the EU cloud). - Add it to Claude Code:
claude mcp add indie-metrics -- /full/path/to/.venv/bin/indie-metrics-mcp. Any MCP client that starts a stdio server works the same way. - Ask: "How many downloads did I get this week against last week?"
You only need the keys for the sources you use. A tool without its key says which setting is missing.
What this will not do
- No writes. It only reads; it never changes an app, a price, a product or an event.
- No hosted service, no account, no telemetry. It talks to Apple, RevenueCat and your PostHog host and nothing else.
- No Google Play in this version.
- No keys in this repository, and none printed in output or errors.
- No guesses. When an API answers with an error the tool says so; it does not fill the gap.
Tests
pip install ".[test]" && pytest. The tests use recorded response shapes with invented ids and a throwaway signing key made at test time.
Licence
MIT. Dependency licences: LICENCES.md.
Metadata
Release files for indie-metrics-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| indie_metrics_mcp-0.1.0.tar.gz | 12.6 kB | With provenance | Details for indie_metrics_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| indie_metrics_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for indie_metrics_mcp-0.1.0-py3-none-any.whl |
Total release size: 23.0 kB
Release files / indie_metrics_mcp-0.1.0.tar.gz
| Download URL | indie_metrics_mcp-0.1.0.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc9cab5e540547de7c245638e827b9d58f1a9a62a514fb90891170a869f5c191
|
|
BLAKE2b-256 checksum How to use checksums |
9e0e5ae8d3e6a75db9cf1b4b6d83b426a587ee333ee8e4582efa8431b625038d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logRelease files / indie_metrics_mcp-0.1.0-py3-none-any.whl
| Download URL | indie_metrics_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08cea4b70ec58b64400383a247efd4b9d7a74abb384fdb32a2f51df92c5cc82a
|
|
BLAKE2b-256 checksum How to use checksums |
7fe1c85a3978f4566823dac976c4846aa4c629d01ff13470d6115214a8c76d63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logSecurity for indie-metrics-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for indie_metrics_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.