Installation options

Amami has two separate installation ideas:

Product access: use Amami Cloud at https://dashboard.amami.dev or operate an Amami-compatible instance yourself.
Agent access: install the local MCP server so Codex, Claude, Cursor, or another assistant can work with your analytics.

Most users should start with Amami Cloud plus MCP browser setup. Self-hosting is for teams that need infrastructure control, custom retention, private network access, or internal compliance requirements.

Cloud

Cloud is the recommended path when you want analytics running quickly.

Hosted dashboard and API.
Browser login and registration.
Tracking script served from https://dashboard.amami.dev/script.js.
MCP authorization flow for AI assistants.
No server, database, upgrade, or backup work.

Start 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.

MCP server

The MCP server is a local stdio process. It lets an AI client call tools for setup, website management, analytics queries, events, and growth analysis.

For the canonical Node.js check, browser setup, client registration, manual configuration, and verification steps, use the guide above. It is the single source of truth for those steps.

Self-hosted compatible instance

Use self-hosting only if you are ready to operate the service stack yourself. A production deployment typically needs:

Node.js 20 or a container image compatible with your deployment.
PostgreSQL for analytics data.
A public HTTPS domain.
Backups and restore testing.
Upgrade and migration procedures.
Optional AI provider keys if you want AI features on the self-hosted instance.

For an MCP connection to a custom instance, use the manual configuration section of the canonical guide. Keep the instance URL and credentials in your client secret store.

Decision guide

Use Cloud when speed matters more than infrastructure control.
Use MCP setup when you want AI-assisted analytics, setup, and growth recommendations.
Use manual API keys when browser setup is not practical.
Use self-hosting when your team accepts operational responsibility.
Do not paste API keys or passwords into agent chat. Use browser authorization, environment variables, local env files, or client secret stores.