Quickstart

Use this path when you want an AI assistant to help you register or log in, authorize Amami MCP, connect a website, and start analyzing growth. If you are still choosing the deployment model, read Installation options first. If you are new to the product model, read Core analytics first.

Requirements

Node.js 20 or newer.
npm or another Node package runner.
A browser on your machine for Amami login, registration, and authorization.
An MCP-capable client such as Codex, Claude, Cursor, Windsurf, Cline, Continue, Zed, VS Code, OpenCode, or a custom script.

Check your local runtime:

node --version
npm --version

One prompt setup

Copy this prompt into your AI assistant. It loads the maintained installation source rather than duplicating setup steps here:

Read and follow the canonical Amami MCP and Skills installation guide at https://analytics.amami.dev/install/mcp-install.md. Use this guide as the only setup source. Do not use web search or another installation guide.

The guide specifies the Node.js check, browser setup, client registration, and safe verification scope.

Browser setup and client configuration

Follow the canonical MCP and Skills installation guide for the current browser authorization, client registration, credentials, and manual configuration. Do not copy individual commands from this page.

Client-specific setup pages:

Connect a website

After the MCP client loads, ask:

Connect this project to Amami. If its website already exists, call `get_tracking_script`; otherwise call `create_website`. Add the returned `trackingScript` to the shared application layout and verify the deployed page sends a pageview.

Both tools return a ready-to-embed trackingScript for the configured analytics instance. Use that exact result instead of copying a fixed host or placeholder website ID.

For a deeper explanation of pageviews, framework snippets, events, UTM parameters, and conversion tracking, read Tracking and events. For goals and multi-step conversion paths, read Goals and funnels.

First events to add

Do not wait until the dashboard looks empty. Add a few meaningful events early:

Signup CTA clicked.
Install command copied.
MCP config copied.
Website connected.
First event received.
Pricing CTA clicked.

These events make later AI analysis much more useful because the assistant can reason about intent, not just traffic volume.

Verify tracking

Ask:

Verify that Amami can see this website, send a test event if write tools are enabled, and summarize the first metrics I should monitor.

Useful verification tools include get_me, list_websites, get_tracking_script, create_website, send_event, get_stats, get_pageviews, get_metrics, and get_active_visitors.

Ask your first analytics question

After verification, ask a specific question:

Analyze the last 7 days for this website. Compare visitors, top pages, referrers, and conversion events. Tell me what changed and what I should improve first.

For more prompt patterns, read Natural language queries.