---
name: amplitude-analytics
description: Use Amplitude to instrument applications, verify event ingestion, analyze product usage and experiments, create charts and cohorts, or look up SDK and API documentation.
---

# Amplitude analytics

## When to use this skill

Use this skill when a user wants to:

- Install Amplitude in an application and verify its first event.
- Analyze user behavior, conversion funnels, retention, or experiment results in an Amplitude project.
- Create charts, dashboards, or behavioral cohorts from existing Amplitude data.
- Send events, export raw data, or automate analytics queries through a REST API.
- Find Amplitude SDK configuration, API parameters, or product documentation.

## Choose the connection for the job

### Install Amplitude

Fetch https://amplitude.com/install.md and follow its maintained setup journey in the target application's repository. Establish the intended project, public ingestion API key, and data region. Follow the stack-specific instructions and verify first-event ingestion before reporting success.

### Analyze or manage project data

1. Connect an MCP-compatible client to https://mcp.amplitude.com/mcp for US projects or https://mcp.eu.amplitude.com/mcp for EU projects.
2. Authenticate with OAuth 2.0 as the user. Tools inherit that user's Amplitude permissions. See https://amplitude.com/docs/amplitude-ai/amplitude-mcp for connection instructions.
3. Discover the tools exposed by the server. Identify the intended organization and project, and read its available events and properties before building a query.
4. Call the matching analytics, chart, experiment, dashboard, or cohort tool with the user's date range, metrics, and filters. Ask for missing project or metric definitions rather than inventing them.
5. Report the result with its project, date range, filters, and returned Amplitude links. Keep writes within the user's requested scope; report permission or data gaps explicitly.

### Call a REST API

Fetch https://amplitude.com/openapi.json and select the operation, regional server, request schema, and authentication scheme for the task. Ingestion uses the public project API key in the request body. Project analytics and export use HTTP Basic authentication with a project API key and secret key; keep secrets on the server and out of source control and responses. Follow the operation's documented errors and rate limits. Do not infer a path's version from another API family.

### Read documentation

Connect to https://amplitude.com/docs/api/mcp for public, read-only documentation without authentication. Discover its tools and use them to find the relevant SDK, API, or product guide. This endpoint does not provide account data. Documentation is also available at https://amplitude.com/docs.

## Additional resources

- Full MCP, API, and skill-library catalog: https://amplitude.com/.well-known/ai-catalog.json
- Developer resource index: https://amplitude.com/developers/llms.txt
- Official MCP skills and plugins: https://github.com/amplitude/mcp-marketplace
- Builder Skills library: https://amplitude.com/builder-skills
- Product and pricing context: https://amplitude.com/llms.txt