The interesting part is what it is built on: an API key against Substack's documented Publisher API, rather than the session cookies that other Substack servers scrape with and that break whenever the site changes. The trade is that this is a reading tool — despite the name, nothing here publishes.
A community-built server over Substack's official Publisher API. Every tool reads: posts, their stats, subscriber figures and the publications your key covers. It authenticates with an API key rather than browser cookies, which is what the vendor's own API expects.
- The publications your key is configured for
- Posts listed, and any single post pulled back in full
- Per-post analytics
- Subscriber counts for a publication
- A single subscriber looked up
Node.js 18 or newer, and a Substack Publisher API key generated from your publication's dashboard. The Publisher API is not enabled on every publication yet, so the dashboard is where you find out whether yours can issue one.
Build from source — clone the repository and build it, then point your client at the binary