Amami MCP docs

Other agents

Amami MCP works with any client that can launch a local stdio MCP server. Use browser setup first, then add the same command and args to the client's MCP configuration.

Run browser setup

npx -y amami-analytics-mcp setup --write

After you log in or register and click Authorize MCP, credentials are saved locally. Most clients then only need this server command:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Windsurf

Add Amami to Windsurf's MCP server configuration:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Then ask Windsurf:

Use Amami to list my websites, connect this project if needed, and analyze the top pages.

Cline

Add the same server entry to Cline's MCP settings:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Then ask:

Use Amami MCP to verify tracking and explain what changed in traffic this week.

Continue

Use the standard stdio command in Continue's MCP configuration:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Zed

Add an Amami MCP server entry using the same command and args:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

VS Code compatible clients

Some VS Code MCP clients use a servers top-level key instead of mcpServers:

{
  "servers": {
    "amami": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

OpenCode

Use Amami as a local stdio MCP server:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Kimi CLI and other command-line agents

For command-line agents that support MCP server configuration, use the same local stdio command:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"]
    }
  }
}

Then ask:

Use Amami to summarize yesterday's traffic, top pages, top sources, and conversion events.

Manual API key config

Use this only when browser setup is not practical:

{
  "mcpServers": {
    "amami": {
      "command": "npx",
      "args": ["-y", "amami-analytics-mcp@latest"],
      "env": {
        "AMAMI_API_KEY": "your_api_key_here",
        "AMAMI_ENABLE_WRITE": "1"
      }
    }
  }
}

Keep keys in the client environment or a secret store. Do not paste API keys into chat.

For clients that use a different config shape, keep the same command, args, and environment variables. See MCP config for the canonical server entry.