# Amplitude — how to use (mcp.ai)

Connect your Amplitude account and use 54 tools for analytics straight from your AI agent. Connect with your own API key. Amplitude gives you the self-serve tools and real-time data to make products and experiences that win no matter what.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_amplitude?ms=1787295960000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `amplitude_assign_annotations_to_category`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/amplitude`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/amplitude/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/amplitude/assign/annotations/to/category` — Tool to bulk assign multiple annotations to a category in Amplitude. Use when you need to organize annotations by assigning them to a specific category.
  - body: { category_id: integer, annotation_ids: integer[] }
- `POST https://api.mcp.ai/api/amplitude/cancel/deletion` — Cancel a pending user deletion request in Amplitude. Use this to remove a user from a scheduled deletion job before it completes. Only works on deletion jobs in 'Staging' status (not yet submitted).
  - body: { amplitude_id: string, job_start_day: string }
- `POST https://api.mcp.ai/api/amplitude/check/cohort/status` — Check the status of a cohort export request. This action allows you to: - Poll the status of an in-progress cohort download request - Determine if a cohort is ready for download
  - body: { request_id: string }
- `POST https://api.mcp.ai/api/amplitude/create/annotation` — Create a chart annotation in Amplitude to mark important dates. Use to highlight key events like feature releases, marketing campaigns, or product updates on analytics charts.
  - body: { end?: string, label: string, start: string, details?: string, category?: string, chart_id?: string }
- `POST https://api.mcp.ai/api/amplitude/create/annotation/category` — Tool to create an annotation category in Amplitude to organize annotations. Use when you need to create a new category for grouping related annotations.
  - body: { category: string }
- `POST https://api.mcp.ai/api/amplitude/create/event/category` — Create a new event category in Amplitude. This action allows you to: - Create a new event category to organize event types - Validate category name before creation Key features: - Creates event catego
  - body: { category_name: string }
- `POST https://api.mcp.ai/api/amplitude/create/event/type` — Create a new event type in Amplitude. This action allows you to: - Define a new event type with various properties - Associate the event with a category - Add metadata like description, tags, and owne
  - body: { tags?: string, owner?: string, category?: string, is_active?: boolean, event_type: string, description?: string, is_hidden_from_timeline?: boolean, is_hidden_from_dropdowns?: boolean, is_hidden_from_pathfinder?: boolean, is_hidden_from_persona_results?: boolean }
- `POST https://api.mcp.ai/api/amplitude/create/release` — Create a release to document product changes. Use when you want to track app version releases and their impact on metrics. Can be integrated into deployment workflows to automatically log releases in 
  - body: { title?: string, version: string, platforms?: string[], description?: string, release_start: string }
- `POST https://api.mcp.ai/api/amplitude/delete/annotation` — Delete a chart annotation from Amplitude. Use to remove existing annotations from charts.
  - body: { annotation_id: string }
- `POST https://api.mcp.ai/api/amplitude/delete/annotation/category` — Delete an annotation category from Amplitude. Use when you need to remove an annotation category that is no longer needed.
  - body: { category_id: integer }
- `POST https://api.mcp.ai/api/amplitude/delete/event/category` — Delete an event category from Amplitude. This action allows you to: - Delete an existing event category - Remove category organization from events Key features: - Permanently removes event categories 
  - body: { category_id: integer }
- `POST https://api.mcp.ai/api/amplitude/delete/event/type` — Delete an event type from Amplitude. This action allows you to: - Remove an event type from your project - Mark live events as deleted - Remove planned events from the tracking plan Key features: - Di
  - body: { event_type: string }
- `POST https://api.mcp.ai/api/amplitude/delete/users` — Submit user deletion requests for GDPR/CCPA compliance. Supports up to 100 users per request. Use when you need to delete user data from Amplitude in compliance with privacy regulations. Either amplit
  - body: { user_ids?: string[], requester: string, amplitude_ids?: integer[], delete_from_org?: boolean, ignore_invalid_id?: string, include_mapped_user_ids?: boolean }
- `POST https://api.mcp.ai/api/amplitude/download/cohort/file` — Download the cohort file after request is complete. Use this action after checking that the cohort status is 'JOB COMPLETED'. The download link is valid for 7 days, but the S3 link is valid for only 1
  - body: { request_id: string }
- `POST https://api.mcp.ai/api/amplitude/find/user` — Search for users in Amplitude by canonical identifier (Amplitude ID, device ID, user ID, or user ID prefix). Use this to find matching Amplitude IDs for deterministic user mapping. Important: This sea
  - body: { user: string }
- `POST https://api.mcp.ai/api/amplitude/get/active/users` — Get the number of active or new users for a date range with optional segmentation. Use when you need user count metrics aggregated by day, week, or month, optionally grouped by user properties.
  - body: { g?: string, i?: integer, m?: string, s?: string, end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/annotation` — Get a single chart annotation by ID from Amplitude. Use when you need to retrieve detailed information about a specific annotation including its label, timestamps, category, and associated chart.
  - body: { annotation_id: string }
- `POST https://api.mcp.ai/api/amplitude/get/annotation/category` — Get a single annotation category by ID from Amplitude. Use when you need to retrieve details about a specific annotation category.
  - body: { category_id: string }
- `POST https://api.mcp.ai/api/amplitude/get/cohort` — Get a single cohort by ID and initiate download. This action allows you to: - Request a specific cohort from Amplitude - Optionally include user properties in the response - Start the asynchronous dow
  - body: { cohort_id: string, property_keys?: string[], include_properties?: boolean }
- `POST https://api.mcp.ai/api/amplitude/get/deletion/requests` — Get the status of user deletion requests within a date range. Use this to track GDPR/CCPA deletion compliance and monitor deletion job progress.
  - body: { end_day: string, start_day: string }
- `POST https://api.mcp.ai/api/amplitude/get/event/categories` — Get event categories from Amplitude. This action allows you to: - Get all event categories in your project - Get a specific category by name
  - body: { category_name?: string }
- `POST https://api.mcp.ai/api/amplitude/get/event/property` — Get a specific event property from Amplitude taxonomy. Use when you need to retrieve details about a specific event property including its type, validation rules, and metadata.
  - body: { property: string, event_type?: string }
- `POST https://api.mcp.ai/api/amplitude/get/event/segmentation` — Get event segmentation data from Amplitude Analytics API. Use this to analyze event metrics over time with optional grouping by properties. Supports multiple metrics (uniques, totals, percentage of DA
  - body: { e: string, g?: string, i?: string, m?: string, end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/event/type` — Get a specific event type from Amplitude by name. This action allows you to: - Retrieve detailed information about a single event type - Get all properties and metadata for the event Key features: - R
  - body: { event_type: string }
- `POST https://api.mcp.ai/api/amplitude/get/event/types` — Get all event types from Amplitude. This action allows you to: - Retrieve all event types in your project - Optionally include deleted events
  - body: { show_deleted?: boolean }
- `POST https://api.mcp.ai/api/amplitude/get/funnel/data` — Get funnel analysis data showing user conversion through a sequence of events. Use this to analyze user drop-off rates and conversion times across multiple steps in a user journey.
  - body: { g?: string, i?: integer, n?: string, cs?: integer, end: string, mode?: string, limit?: integer, start: string, events: object[] }
- `POST https://api.mcp.ai/api/amplitude/get/realtime/active/users` — Get real-time active users count from Amplitude. Returns active user counts with 5-minute granularity (configurable) for today and yesterday. Use this to monitor current user activity and compare with
  - body: { i?: integer }
- `POST https://api.mcp.ai/api/amplitude/get/retention` — Get user retention analysis showing how users return over time after a starting action. Use when analyzing user engagement patterns, measuring feature stickiness, or understanding long-term user behav
  - body: { g?: string, i?: integer, s?: string, rb?: string, re: string, rm?: string, se: string, end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/revenue/ltv` — Get revenue lifetime value (LTV) metrics including ARPU, ARPPU, and total revenue. Use when you need to analyze revenue trends over time for user cohorts.
  - body: { i?: integer, m?: integer, end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/session/average` — Get average session length (in seconds) for a specified date range from Amplitude. Use when you need to analyze user engagement patterns and session duration trends over time.
  - body: { end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/session/length` — Tool to retrieve session length distribution data for a specified date range from Amplitude. Use when you need to analyze how long users' sessions typically last or visualize session duration patterns
  - body: { end: string, start: string, timeHistogramConfigBinMax?: integer, timeHistogramConfigBinMin?: integer, timeHistogramConfigBinSize?: integer, timeHistogramConfigBinTimeUnit?: string }
- `POST https://api.mcp.ai/api/amplitude/get/sessions/per/user` — Tool to get average number of sessions per user for each day in a date range from Amplitude. Use when analyzing user engagement patterns or session frequency over time.
  - body: { end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/user/activity` — Fetch a single user's profile summary and event stream by Amplitude ID. Use when you need to extract attribution data (UTM parameters, referrers) from early events or user properties, or when analyzin
  - body: { user: string, limit?: integer, offset?: integer, direction?: string }
- `POST https://api.mcp.ai/api/amplitude/get/user/composition` — Tool to get user composition breakdown by property (platform, version, country, etc.). Use when analyzing user distribution across property values during a date range.
  - body: { p: string, end: string, start: string }
- `POST https://api.mcp.ai/api/amplitude/get/user/mappings` — Get the list of user mappings for provided user IDs. Use when you need to retrieve aliasing relationships between user identifiers in Amplitude. Returns mapping data showing which users map into and o
  - body: { user_ids: string[] }
- `POST https://api.mcp.ai/api/amplitude/get/user/property` — Get a specific user property from Amplitude taxonomy. Use when you need to retrieve details about a specific user property including its type, validation rules, and classifications.
  - body: { user_property: string }
- `POST https://api.mcp.ai/api/amplitude/identify` — Update user properties using Amplitude's Identify API. This action allows you to: - Set or update the User ID for a Device ID - Update user properties without sending an event - Perform operations on 
  - body: { api_key?: string, identification: object|object[] }
- `POST https://api.mcp.ai/api/amplitude/list/annotation/categories` — List all annotation categories from Amplitude. Use to retrieve available categories for chart annotations.
  - body: { category?: string }
- `POST https://api.mcp.ai/api/amplitude/list/annotations` — Tool to get all chart annotations with optional filtering by category, chart, and date range. Use when you need to retrieve annotations that mark important events or milestones on Amplitude charts.
  - body: { end?: string, start?: string, category?: string, chart_id?: string }
- `POST https://api.mcp.ai/api/amplitude/list/cohorts` — List all discoverable cohorts for an Amplitude project. This action allows you to: - Get a list of all cohorts in your Amplitude project - Optionally include sync information for each cohort Key featu
  - body: { include_sync_info?: boolean }
- `POST https://api.mcp.ai/api/amplitude/list/event/properties` — Get all event properties from Amplitude, optionally filtered by event type or property name. Use when you need to retrieve property definitions, data types, or validation rules for events.
  - body: { event_type?: string, event_property?: string }
- `POST https://api.mcp.ai/api/amplitude/list/events` — Tool to get a list of all event types in your Amplitude project with current week's statistics. Use when you need to see all events and their recent activity metrics including totals, uniques, and DAU
- `POST https://api.mcp.ai/api/amplitude/list/user/properties` — Tool to get all user properties in your Amplitude project. Use when you need to retrieve the complete list of user properties including both default and custom properties.
- `POST https://api.mcp.ai/api/amplitude/map/user` — Map users with different user IDs together (alias/merge users) in Amplitude. Use this to merge user identities across different identifiers or unmap previously merged users. Supports up to 2000 mappin
  - body: { api_key?: string, mappings: object|object[] }
- `POST https://api.mcp.ai/api/amplitude/restore/event/type` — Restore a deleted event type in Amplitude. This action allows you to: - Restore a previously deleted event type - Make the event available again in the UI and API Key features: - Undoes the deletion o
  - body: { event_type: string }
- `POST https://api.mcp.ai/api/amplitude/send/events` — Send events to Amplitude using the HTTP V2 API. This action allows you to send events to Amplitude for tracking user behavior and analytics. It supports all Amplitude event fields, handles proper vali
  - body: { events: object[], api_key?: string, options?: object }
- `POST https://api.mcp.ai/api/amplitude/set/group/properties` — Set group properties for account-level reporting without sending an event. Use this action to update group attributes like company name, industry, or plan type. Requires Enterprise plan with Accounts 
  - body: { api_key?: string, identification: object|object[] }
- `POST https://api.mcp.ai/api/amplitude/update/annotation` — Tool to update an existing chart annotation in Amplitude. Use when you need to modify annotation properties such as label, timestamps, category, or chart association. Supports partial updates - only i
  - body: { end?: string, label?: string, start?: string, details?: string, category?: string, chart_id?: string, annotation_id: string }
- `POST https://api.mcp.ai/api/amplitude/update/annotation/category` — Tool to update an annotation category in Amplitude. Use when you need to rename or modify an existing annotation category for organizing chart annotations.
  - body: { category: string, category_id: string }
- `POST https://api.mcp.ai/api/amplitude/update/cohort/membership` — Incrementally update cohort membership by adding or removing IDs. This action allows you to: - Add new IDs to an existing cohort - Remove IDs from an existing cohort - Perform multiple operations in a
  - body: { cohort_id: string, count_group?: string, memberships: object[], skip_invalid_ids?: boolean }
- `POST https://api.mcp.ai/api/amplitude/update/event/category` — Update an existing event category in Amplitude. This action allows you to: - Update the name of an existing event category - Validate the new category name Key features: - Updates category names - Ret
  - body: { category_id: integer, category_name: string }
- `POST https://api.mcp.ai/api/amplitude/update/event/type` — Update an existing event type in Amplitude. This action allows you to: - Change event type properties - Update event name, category, metadata, and settings - Modify display name for ingested events Ke
  - body: { tags?: string, owner?: string, category?: string, is_active?: boolean, event_type: string, description?: string, display_name?: string, new_event_type?: string, is_hidden_from_timeline?: boolean, is_hidden_from_dropdowns?: boolean, is_hidden_from_pathfinder?: boolean, is_hidden_from_persona_results?: boolean }
- `POST https://api.mcp.ai/api/amplitude/upload/batch/events` — Bulk upload events to Amplitude using the Batch Event Upload API. Supports larger payloads (20MB) and higher throttling limits than HTTP V2 API. Use when you need to send large batches of events effic
  - body: { events: object[], api_key?: string, options?: object }
- `POST https://api.mcp.ai/api/amplitude/upload/cohort` — Generate a new cohort or update an existing cohort by uploading user IDs or Amplitude IDs. Use when you need to create cohorts from a specific list of users.
  - body: { ids: string[], name: string, owner: string, app_id: integer, id_type: string, published: boolean, existing_cohort_id?: string }

## Example prompts
- "What can I do in Amplitude?"
- "Show me a summary of my Amplitude account"

## More
- Page: https://mcp.ai/amplitude
- Agent spec (llms.txt): https://mcp.ai/amplitude/llms.txt
- Postman collection: https://mcp.ai/amplitude/postman.json