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.
I have built and grown websites for over 20 years, living inside analytics every day. GA4 kept growing, with more reports and more setup, most of which I never opened. :) At some point I found myself taking a Google Analytics course, and that is when it clicked: I am not the audience for this product. So I started building my own.
Building it myself meant I set the requirements, and from the start those were: collect as little as possible, no fingerprinting, and a product shaped around European regulation. Statable is cookieless, EU-hosted (NL) and needs no consent banner for analytics.
Then AI got good enough to take over my routine work, but agents had no way into analytics. That is what the MCP server fixed. Now the numbers live where I already work: I ask Claude what moved last week and get an answer from my own data, and when I need a funnel for the signup flow I describe it in a sentence instead of clicking through a builder.
Connecting is one OAuth sign-in, and you choose whether an assistant can configure anything or only read.
Free forever on .edu and GitHub or GitLab Pages.
Would you use this? If not, what stops you? I am here all day.
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.
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
How it handles sites with several domains or subdomains. Can one account keep those properties organized separately?
Does it still capture enough detail for meaningful conversion analysis without cookies?
About Statable Analytics on Product Hunt
“Web analytics built for you and your AI agents”
Statable Analytics launched on Product Hunt on September 28th, 2026 and earned 253 upvotes and 15 comments, earning #2 Product of the Day. 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.
Statable Analytics was featured in Analytics (173.9k followers) and Artificial Intelligence (479.7k followers) on Product Hunt. Together, these topics include over 141.4k products, making this a competitive space to launch in.
Who hunted Statable Analytics?
Statable Analytics was hunted by Ben Lang. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Statable Analytics stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Ben Lang
Hey Product Hunt. Yevhen here.
I have built and grown websites for over 20 years, living inside analytics every day. GA4 kept growing, with more reports and more setup, most of which I never opened. :) At some point I found myself taking a Google Analytics course, and that is when it clicked: I am not the audience for this product. So I started building my own.
Building it myself meant I set the requirements, and from the start those were: collect as little as possible, no fingerprinting, and a product shaped around European regulation. Statable is cookieless, EU-hosted (NL) and needs no consent banner for analytics.
Then AI got good enough to take over my routine work, but agents had no way into analytics. That is what the MCP server fixed. Now the numbers live where I already work: I ask Claude what moved last week and get an answer from my own data, and when I need a funnel for the signup flow I describe it in a sentence instead of clicking through a builder.
Connecting is one OAuth sign-in, and you choose whether an assistant can configure anything or only read.
Free forever on .edu and GitHub or GitLab Pages.
Would you use this? If not, what stops you? I am here all day.