Skills

Turn Your Assistant into a Product Analyst in Your Editor

A good fit for viewing charts and understanding users in Claude Code, using only the official plugin installation command and completing authentication when prompted.

Official source · Amplitude AI Plugin

Install

claude plugin install amplitude

Who It's For

If you already build products in an editor and want the assistant to analyze directly instead of switching back and forth to the Amplitude dashboard, this plugin fits. Officially, it is described as the official Amplitude plugin that turns AI assistants into product analysts, lets them instrument analytics, view charts, run experiments, and understand users from the editor.

It is listed as usable with Claude Code, Cursor, Codex, Gemini CLI, and Claude. This is a list of explicitly named compatible environments, not an indication that each has a documented installation command. The only copyable installation command provided is in the Claude Code section.

It is best suited to people who already have an Amplitude account and want to start by viewing charts or understanding users in read-only mode, rather than changing instrumentation or launching an experiment right away. The official instructions are at

https://github.com/amplitude/mcp-marketplace

Complete Your First Try in 3 Minutes

Follow this one official installation path:

claude plugin install amplitude

Prerequisites: claude must already run on this machine, and you need access to an Amplitude account. After installation, authenticate when prompted. Authentication opens an authorization flow; confirm that the window comes from this installation before continuing. Do not put keys in the repository.

Make the first task read-only analysis. After authentication succeeds, ask the assistant to interpret an existing chart or explain what a certain type of user is doing. Do not start with instrumentation or an experiment. Viewing charts and understanding users are capabilities named on the page and are the easiest to verify.

Success signal: the plugin installs, you confirm and complete authorization after the authentication prompt, and the assistant returns an explanation that lines up with Amplitude charts or user behavior rather than saying it is uninstalled or unauthenticated. If Cursor, Codex, Gemini CLI, or Claude do not yet have parallel commands documented, do not adapt this claude plugin command on your own.

Use Cases

Case one: read charts and dashboards first.

The official page describes reusable skills covering charts, dashboards, and turning the assistant into a product analyst that can analyze charts. For the first attempt, open one existing chart and ask the assistant to explain the trend. The page does not specify a chart ID format or dashboard permission model; what can be confirmed is that these analysis skills exist and that you need to complete the authentication prompt first.

Case two: understand users or review sessions before discussing instrumentation.

The official page also names understand users, session replays, and AI agent analytics. For the first attempt, focus only on understanding: ask the assistant to explain behavior based on an existing replay or user data, without changing tracking code. Instrumentation and analytics tracking workflows can change product code, while experiments can change experiment configuration, so they require separate confirmation. The page does not provide an instrumentation API list or experiment creation fields.

Both cases rely on the same Claude Code plugin command and authentication prompt.

Usage Boundaries

The only copyable installation command is claude plugin install amplitude. The other named environments do not have their own installers written in the provided text; do not generalize this command to environments without documented installation steps.

Authentication is a required follow-up step. The page only says to authenticate when prompted; it does not say that this can be skipped, and it does not describe a no-account demo mode.

The capabilities also include experiments, reliability, and instrumentation workflows, but these can change data or code. For the first attempt, stop at reading charts and understanding users. The page does not specify quotas, project permissions, or a retention period for session replays.