Amami
Analytics that lives inside your AI assistant
Start new thread

Amami - Analytics that lives inside your AI assistant

by•
I built Amami because I was tired of tab-switching between Cursor and a browser tab just to check how many people visited my site. Amami is privacy-first analytics with native MCP support — you literally ask Codex/Claude "how's my traffic?" and get answers + recommendations without leaving your editor. No cookies, no consent banners, <2KB script. Start to use it now !

Add a comment

Replies

Best
Maker
📌
Hey hunters! 👋 We built Amami because we kept asking ourselves: "Why do I need to open a browser to check analytics when I spend 90% of my day in Cursor?" The MCP integration means your AI assistant becomes your data analyst. Not just "here's your pageview count" — but "your pricing page got 3,240 visits last week, HN visitors stay 42% longer, and I recommend doubling down on your HN launch strategy." Happy to answer any questions about MCP, privacy-first analytics, or our tech stack! P.S. — Try the one-prompt setup. It genuinely feels like magic the first time your AI says "I've added analytics to your project."
Maker

Shoutout to everyone checking out on Product Hunt!

We’ve prepared an exclusive gift just for PH community members: 3 full months of Pro membership, 100% free — no hidden fees, no strings attached.

Grab your free trial right away!

Hit me up in the comments or shoot an email to if you’ve got any questions.

Exclusive PH promo code:

AMAMI-97F1E-70C61-C30E5-B87E8-1C048-171E1

From my experience: a dashboard sometimes shows something you weren't looking for - a spike you didn't think would happen. With a query-first setup, how do you surface the thing you didn't know to ask? 

Maker
Great question — and honestly, this is exactly why we didn't go "dashboard-only" or "query-only." **We have a full dashboard.** Clean, fast, all your data visualized. You can browse around, spot spikes you didn't expect, drill down. It's there when you want it. But here's the thing: we think the *default* should be AI-first, not dashboard-first. **What's coming: AI Inspection** We're launching an AI agent that automatically inspects your data on a regular basis. You connect via MCP and ask: > "What do you see in my data? Anything I should optimize for traffic or conversions?" And the AI actually answers based on your real data: > "I see three things: > 1. Your /pricing page bounce rate jumped 12% since last week — might be the new headline > 2. HN referral traffic is up 3x but conversion is flat — your landing page might not match their expectations > 3. Mobile visitors drop off hard on your signup form — consider shortening it" It's not "query instead of dashboard" — it's **having a data analyst who actually looks at your numbers and tells you what matters,** without you needing to know what to look for. The dashboard is for exploration. The AI is for insight. Both exist. We just think most people shouldn't have to stare at charts to know what to fix. Curious — what would you want an AI analyst to flag for you automatically?

 Thank you, that's a really solid answer! What I'd want flagged most: silent failures. A page that quietly stops converting, or a form that drops to zero. That's usually something breaking, and it's most likely the thing worth immediate attention

Finally, analytics I can actually query from my editor instead of alt-tabbing like it's 2009. The MCP angle feels genuinely useful for quick "is this page getting traction" checks.

Maker
Appreciate that — the alt-tab fatigue is real. Here's the fastest way to try it: tell your AI assistant: > "Add analytics to my website." That's it. The agent handles setup, opens your browser for auth, injects the tracking script, and confirms when it's live. Takes about 60 seconds. Then you can ask "is my landing page getting traction?" and get an actual answer. Give it a shot:

finally something that fixes the annoying back-and-forth between my editor and the browser tab just to check stats. the MCP integration works smoothly, asked claude about yesterday's traffic and got a clear breakdown with actual suggestions on what to fix.

Maker
Thanks ! This is exactly why we built it — that constant context-switching between editor and browser just kills flow. Really glad the MCP setup was smooth and Claude gave you actionable suggestions. That's the part we're most excited about: not just "here are your numbers" but "here's what to do about them." If anything felt missing or clunky during setup, my DMs are open — we ship fast.

The MCP integration is genuinely clever, that part hooked me. One thing though, I'd love a way to compare traffic windows right from my editor prompt, like asking how this week stacks up against last week without opening a dashboard. That would make the AI-driven angle even more useful day to day.

Maker
Thanks for sharing that — it's exactly the kind of workflow we had in mind. And here's the thing: **this already works.** You can ask those exact questions right now in Claude Code or Cursor: > "How does this week compare to last week?" > "Which pages dropped this month?" > "Why did our paid conversion rate change?" Amami will pull the data, compare the periods, and give you both the breakdown and the takeaway — what changed and what to do about it. No dashboard needed. Go ahead and try it out. Happy analyzing!

Love the MCP integration idea, this is exactly the kind of thing that makes analytics actually useful inside my workflow. One thing that would seal it for me is real-time visitor counts streaming live, so I can literally watch the impact of a post I just published without refreshing anything.