Launched this week
Statable Analytics
Web analytics built for you and your AI agents
755 followers
Web analytics built for you and your AI agents
755 followers
Statable is web analytics built for humans and AI agents. Use the simple dashboard yourself, or connect Claude, ChatGPT, Cursor, Codex, and other agents through MCP to read reports, analyze traffic, and configure tracking, goals, and funnels. No cookies, no analytics consent banner in most cases, and your data stays hosted in the EU.
Build Check
That's impressive Yevhen! Congrats on the launch
Statable Analytics
@german_merlo1 Thanks Germán! Day one and already at #2, still a bit surreal. Appreciate you stopping by
Dial
the read vs configure split on the OAuth connection is the detail that would actually get this approved internally, most MCP analytics tools I've seen just hand the agent full write access and hope for the best. one thing I'd want to know before connecting it to anything real: if I only grant read access, can the agent still see raw visitor-level data (IPs, hashed IDs, individual sessions) or is it aggregated numbers only at that permission level? that distinction matters a lot once you're piping traffic data through a model you don't fully control.
Statable Analytics
@galdayan read access is aggregates only. We don't store visitor IPs. We use them on arrival to look up country, region and city, and to build a visitor hash. Then we discard them. The hash is salted daily and never exposed. No tool lists individual visitors or sessions. With read access, the agent sees totals: visitors and pageviews by page, source, country, device, etc
Page paths, UTM tags and custom event properties come back as your site sends them. We strip query strings from page URLs, but nothing else. So keep emails and customer IDs out of them.
Dial
@anatolii_vasylenko that clears it up, the daily-salted hash plus stripped query strings is basically the config I'd want to see documented on the site itself, not just in a comment thread. most tools bury this kind of detail in a privacy policy page nobody reads before granting access. good answer.
Statable Analytics
@anatolii_vasylenko @galdayan Fair, and that is on me. A comment thread is not documentation. I will add a short page in the docs this week: what the read scope can see, what the write scope can change, and the fact that no endpoint returns a visitor or a session row at any permission level. I will drop the link in this thread when it is live.
Statable Analytics
@anatolii_vasylenko @galdayan Thanks, will ping you here when it's up.
this looks really useful for teams that want analytic without adding more complexity the MCP support for connecting AI agents directly to analytics is especially interesting
Statable Analytics
@shivam_kushwaha16 Thanks! Curious which agent you'd plug in first, Claude, Cursor or something else?
@yevhen_skrypets I’d probably start with Claude for this use case but having the flexibility to switch between agents is what makes the setup really interesting
Statable Analytics
@shivam_kushwaha16 Claude is where I'd start too. It's what I use every day for this.
Web stats your coding agent can interrogate, no consent popup circus. Pretty practical.