> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rippit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amplitude MCP server

> Let the Rippit agent query Amplitude product analytics alongside your conversation data.

Amplitude tells Rippit what customers do in your product: the funnel step where they drop off, the feature they stopped using, the experiment variant they saw. Joined to conversation analysis, "these 40 tickets are about the new editor" becomes "these 40 tickets are about the new editor, and those customers' weekly editor usage fell by half after the release."

## What the agent gets

* **Analytics queries**: ad hoc queries over events, users, and properties, and results from charts you already saved.
* **Charts, dashboards, notebooks, and cohorts** to search and read.
* **User and session context**: user profiles and session replay details.
* **Your data taxonomy**: events, properties, and group types, so the agent picks the right names without being told.
* **Experiments and feature flags** to read and analyze.
* **Writes**, only if you enable them: create and edit dashboards, notebooks, cohorts, experiments, feature flags, and tracking-plan events and properties.

## Setup

In Rippit, open **Connections → MCP Servers**, choose **Amplitude**, and sign in to Amplitude. There is no Amplitude app or API key to set up first.

Rippit connects to Amplitude's US server. If your Amplitude data is in the EU region, sign-in fails or no projects appear; add `https://mcp.eu.amplitude.com/mcp` as a [custom server](https://docs.rippit.com/agentic-chat/connectors/custom-server.md) instead.

If sign-in is refused, check that an Amplitude admin has not blocked MCP under **Settings → Content Access → Model Context Protocol (MCP)**.

## Identity and scope

The connection acts as the Amplitude user who signed in, with that user's role in each project. A project the user cannot see is a project the agent cannot see, and Amplitude grants no extra access.

Write tools also need the **Use MCP (write)** permission on the user's Amplitude role.

## Write access

The connection starts read-only: tools that create or change Amplitude content stay off until you enable them under **Tool permissions**.

Some write tools change more than reports. `use_amp_flags` creates and updates feature flags and their deployments, and `use_amp_experiments` creates and updates experiments, so enabling them lets the agent change what your users see. `use_amplitude_cohorts` can sync cohorts to other tools.

## Tools

You choose which tools the agent can use under **Tool permissions** on the server's page, one at a time or a whole group at once. See [Setting one up](https://docs.rippit.com/agentic-chat/overview.md#setting-one-up).

Amplitude adds tools over time, so **Tool permissions** shows the exact list for your connection.

| Tool | Access | What it does |
| - | - | - |
| `query_amplitude_data` | Read | Run ad hoc analytics queries, or query a saved chart by ID |
| `get_amplitude_charts` | Read | Search, list, and inspect saved charts |
| `search_amp_entities` | Read | Search charts, dashboards, notebooks, cohorts, and other content |
| `search_amp_data_taxonomy` | Read | Search events, properties, and other taxonomy |
| `get_amplitude_context` | Read | The organization and project context Amplitude keeps for AI tools |
| `get_from_url` | Read | Open the Amplitude content a URL points to |
| `get_amp_user_data` | Read | Look up users and their activity |
| `get_amp_session_replay_info` | Read | Search and inspect session replays |
| `get_group_types` | Read | List group types, such as accounts |
| `get_transformations` | Read | List data transformations |
| `render_amplitude_chart` | Read | Render an interactive chart and return a link to edit it |
| `use_amp_dashboards` | Write | Read, create, and edit dashboards |
| `use_amp_notebooks` | Write | Read, create, and edit notebooks |
| `use_amp_comments` | Write | Read and add comments |
| `use_amplitude_cohorts` | Write | Read, create, and sync cohorts |
| `use_amplitude_chart_monitors` | Write | Read, create, and manage chart alerts and monitors |
| `use_amplitude_metrics` | Write | Read, create, update, and delete metric definitions |
| `use_amp_experiments` | Write | Read, analyze, create, and update experiments |
| `use_amp_flags` | Write | Read, create, and update feature flags and deployments |
| `share_amp_entities` | Write | Manage sharing and access roles |
| `manage_amp_entities` | Write | Create spaces and move content between them. Amplitude asks you to confirm each change |
| `manage_amp_events`, `manage_amp_properties`, `manage_amp_branches` | Write | Create, update, delete, and restore tracking-plan events, properties, and branches |
| `manage_amp_context` | Write | Replace the organization or project AI context text |
| `run_amp` | Write | Call Amplitude's Developer API for guides, surveys, heatmaps, and more |

Which tools start enabled depends on how Amplitude marks each one, so check **Tool permissions** after connecting and turn off anything you don't want the agent to use.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.