amplitude

name: Amplitude description: > Amplitude analytics via MCP (Model Context Protocol). Query product data, create/edit charts and dashboards, manage cohorts and experiments, search session replays, and analyze feedback. Use when: (1) querying analytics data (events, funnels, retention, segmentation), (2) creating or editing charts, (3) building dashboards, (4) managing cohorts or experiments, (5) searching Amplitude content, (6) any task involving Amplitude analytics. Requires amplitude-cli (amp command) and AMPLITUDE_ACCESS_TOKEN (OAuth via Nango). integration_dependencies: - amplitude metadata: {"openclaw": {"emoji": "📊", "requires": {"env": ["AMPLITUDE_ACCESS_TOKEN"], "bin": ["amp"]}, "primaryEnv": "AMPLITUDE_ACCESS_TOKEN", "install": [{"id": "node", "kind": "node", "package": "amplitude-cli", "global": true, "bins": ["amp"], "label": "Install Amplitude CLI (npm)"}]}}

Amplitude

Full Amplitude analytics via the amp CLI (amplitude-cli package). All commands go through Amplitude's MCP server using OAuth. Auth is handled automatically — AMPLITUDE_ACCESS_TOKEN is injected via Nango.

Architecture

amp CLI → Amplitude MCP server (OAuth)

Single transport, single auth method. No API keys needed.

CLI: amp

amp auth status         # verify connection
amp charts search "DAU" # search charts
amp tools list          # see all MCP tools
amp --help              # full command list

Commands

Auth

amp auth status                          # show auth status
amp auth login [--region us|eu]          # OAuth login (interactive, for humans)
amp auth logout                          # revoke tokens

Tool Discovery

amp tools list                           # list all available MCP tools
amp tools describe <tool-name>           # show input schema for a tool

Use amp tools describe query_dataset to see the exact schema the server expects. This is the source of truth — it returns live schemas from the MCP server.

Events

amp events list                          # list all event types
amp events list -s "purchase"            # search events by name
amp events props <event-type>            # get properties for an event type

Analytics Queries

amp query segment -e <event> --from <date> --to <date> [options]
amp query funnel -e <e1> <e2> ... --from <date> --to <date>
amp query retention --start-event <e> --return-event <e> --from <date> --to <date>
amp query revenue --from <date> --to <date> [options]
amp query sessions --from <date> --to <date>
amp query chart <chart-id>               # get data from a saved chart

Segment options: -m metric (uniques|totals|avg|pctdau), -i interval (1|7|30), -g group-by (user:prop), --filters JSON array

Charts

amp charts search <query>                # search charts
amp charts get <chartId>                 # get chart definition
amp charts query <chartId>               # query chart data
amp charts create --definition '<json>'  # create chart via create_chart tool
amp charts create --definition '<json>' --name 'Name'  # create and save
amp charts discover <query>              # discover events and properties
amp charts event-props <event-type>      # get properties for an event type

Dashboards

amp dashboards search <query>            # search dashboards
amp dashboards get <dashboardId>         # get dashboard with all charts
amp dashboards create --name 'name' --definition '<json>'  # create dashboard

Users

amp users search <query>                 # search users
amp users activity <amplitudeId>         # user activity stream

Cohorts

amp cohorts list                         # list all cohorts
amp cohorts get <cohortId>               # get cohort definition
amp cohorts create --name 'name' --definition '<json>'  # create cohort

Experiments

amp experiments search <query>           # search experiments
amp experiments get <experimentId>       # get experiment details
amp experiments results <experimentId>   # query results with stats

Direct MCP Tool Calls

amp call <tool-name> '<json-args>'       # call any MCP tool directly

For tools the CLI doesn't have a dedicated command for (session replays, feedback, notebooks, etc.), use amp call:

amp call get_session_replays '{"filters": {...}}'
amp call get_feedback_insights '{"projectId": "..."}'
amp call get_from_url '{"url": "https://app.amplitude.com/..."}'

Available MCP Tools

The CLI wraps these MCP server tools. Use amp tools list for the live list, or amp tools describe <name> to see a tool's input schema.

Discovery & Navigation

Charts

Dashboards & Notebooks

Analytics

Cohorts & Experiments

Users & Sessions

Feedback

Key Patterns

Chart Creation Workflow

1. amp charts create --definition '<json>' --name "My Chart" — creates and saves in one step
2. Or for dashboards: create charts first, then amp dashboards create with the saved chart IDs

Dashboards require SAVED chart IDs. Create and name charts before adding them to dashboards.

Multi-Project

If your account has multiple projects, specify which one:

amp --project-id <id> query segment -e _active --from 2024-01-01 --to 2024-03-01

Or set AMPLITUDE_PROJECT_ID in the environment. If not set, the CLI auto-discovers from your token context.

Amplitude Meta Events (for queries)

• _active — Any active event (DAU, MAU)
• _all — Any tracked event
• _new — New user events
• _any_revenue_event — Revenue events

Property Types

• Amplitude core: source: "AMPLITUDE" — platform, country, device_type, os
• Custom: source: "CUSTOMER" — prefixed gp: (e.g., gp:email, gp:plan)

Schema Discovery

If a command returns unexpected errors, verify the expected schema:

amp tools describe query_dataset

This returns the live input schema from the MCP server.

Environment