> "Add analytics to this project."
"Created a tracked website, generated the script, and wired it into your app. Tracking starts now."
Ask Cursor, Claude, or your coding agent about traffic, referrers, pages, and conversions. Get answers and recommendations without opening a dashboard.
> Amami connects your AI assistant to website analytics in one step. Natural questions. Instant insights. No context switching.
Connect this website to Amami and analyze what is happening.
> Installing Amami MCP
> Creating tracked website
> Reading traffic and referrer data
Amami connected. I found your site, analyzed traffic and referrers, and surfaced three recommendations:
- Improve the docs CTA placement
- Optimize the GitHub landing path
- Track signup events on the install page
// Your AI discovers your sites, reads the data, and tells you what to fix.
"Created a tracked website, generated the script, and wired it into your app. Tracking starts now."
"GitHub, docs, and X are your top sources. GitHub visitors stay 42% longer. Double down there."
"Move the signup CTA above the fold on /install. Track pricing clicks. Create a clearer path for GitHub traffic."
// Copy one sentence. Your AI handles installation, browser auth, and setup.
Copy this prompt and send it to your AI:
Install the Amami MCP server, then guide me through browser login and authorization.
https://dashboard.amami.dev/install/mcp-install.mdYour AI assistant can create analytics projects, inject tracking, analyze traffic, and suggest improvements. Sensitive steps like login, registration, and authorization stay in your browser, under your control.
// Turn your AI assistant into a website data analyst.
Find every analytics project your account can access.
Spin up a new tracked website for any app you are building.
Pull visitors, pageviews, bounce rate, and session time for any date range.
View traffic patterns by minute, hour, day, or month.
Rank pages, referrers, countries, devices, events, and UTM campaigns.
Send test or server-side events to confirm your data pipeline is healthy.
// Agents can analyze, but you control the keys.
Login, registration, and MCP authorization happen in your browser. You operate them, not your AI.
Your API key is stored in your local environment, never pasted into chat.
Your AI can inspect data safely. Write access is only enabled when you explicitly request setup.
Every insight is based on your actual traffic, pages, referrers, and events. No generic advice.