# Amplitude

Amplitude organizations hosted in the US or the EU can use Amplitude's MCP server. There is nothing to create in Amplitude: each person who uses the server signs in with their own Amplitude account and keeps the project access and permissions that account already has. The access check below needs an Amplitude organization admin.

### Identify your data region
1. Sign in to Amplitude and open the intended organization.
2. Check the hostname in the browser address bar.
3. Record the server URL that matches it.

   For `app.amplitude.com` (US):

   ```
   https://mcp.amplitude.com/mcp
   ```

   For `app.eu.amplitude.com` (EU):

   ```
   https://mcp.eu.amplitude.com/mcp
   ```

The data region is chosen when the organization is created, and the two URLs are not interchangeable: an EU organization must use the EU URL.

<!-- screenshot: the Amplitude address bar showing the app.amplitude.com or app.eu.amplitude.com hostname, with organization and project details obscured -->

### Confirm MCP access
Amplitude allows its MCP server for every user by default. These steps confirm that nobody has turned it off.

1. As an Amplitude organization admin, click the gear icon to open **Settings**, then go to **Content Access > MCP** in your organization settings. Only organization admins can change this setting.
2. Confirm that the content access controls allow the Amplitude MCP server.
3. If they block it, allow it. This setting applies to every MCP client and every user in the organization.
4. If your organization uses custom roles, go to **Role Management** in the same organization settings and open a role that Speakeasy users hold.
5. In the **AI Features** category, confirm that **Use MCP (read)** is enabled. Without it, MCP calls fail for that role, even for organization admins.
6. Enable **Use MCP (write)** only if users with that role should be able to change Amplitude data through the server.
7. Repeat steps 5 and 6 for each other custom role that Speakeasy users hold.

Amplitude's built-in roles already grant **Use MCP (read)**, and its Member, Manager, and Admin roles also grant **Use MCP (write)**.

<!-- screenshot: Content Access > MCP in the organization settings with the Amplitude MCP server allowed, then Role Management > AI Features showing Use MCP (read) and Use MCP (write); organization details obscured -->

### Add the server in Speakeasy
1. In the Speakeasy AI Control Plane sidebar, under **MCP Gateway**, select **MCP**.
2. Click **Add new** to open **Add MCP server**.
3. Choose **Hosted remotely**. Use this path in both regions, because the server URL depends on your data region.
4. On **New remote MCP server**, paste the server URL from [Identify your data region](#identify-data-region) into **MCP server URL**.
5. Leave **User session issuer** at its default.
   - This setting controls how people sign in to Speakeasy when they connect to the server, not how they sign in to Amplitude, so Amplitude needs no particular choice.
   - It is separate from the Amplitude issuer under [Connect your credentials](#connect-speakeasy-credentials).
   - The default is your organization's issuer when it has exactly one, or **Create a project-specific issuer** when it has none.
   - If your organization has several issuers, none is preselected. Pick the one your Speakeasy admin uses for MCP servers.
6. Click **Verify connectivity**.
7. Under **Identity**, keep **User Identity** selected.
8. If **Guardrails** appears, leave it off.
9. Click **Save**.

On save, Speakeasy discovers the Amplitude identity provider for your region and registers a client automatically. When that works, the server is ready. When it cannot, the server is kept **Disabled** and the result says to finish setup in **Settings > Identity**. In that case, continue with [Connect your credentials](#connect-speakeasy-credentials) below.

<!-- screenshot: New remote MCP server after Verify connectivity, with an Amplitude server URL entered and User Identity selected -->

### Connect your credentials
Open the server's **Settings** and find the **Identity** section. If creation already configured the identity, **User Identity** is selected with the Amplitude provider and **Auto-Configure**. In that case, skip to step 6 and check **Server Availability**.

1. Select **User Identity**.
2. Confirm that the preselected provider uses the issuer for your region. A provider that does not exist yet shows **Will be created**.
   - US: `https://mcp.amplitude.com`
   - EU: `https://mcp.eu.amplitude.com`
3. If a provider for the other region is preselected, open the provider picker and choose the one for your region's issuer.
4. Keep **Auto-Configure** selected. There is no **Client ID** or secret to paste.
5. Click **Save**.
6. If the server shows **Disabled**, open **Settings > Danger Zone > Server Availability** and turn on **Enable MCP server** so it shows **Enabled**.

When a person first uses the server, Amplitude prompts them in the browser:

1. Sign in with the Amplitude account for the intended organization. Stay signed in to only one Amplitude organization during this step. Amplitude says being signed in to several can make authentication fail.
2. Approve the authorization request.
3. If the page keeps spinning after you approve, close the tab. Authentication is complete.

If tool calls fail after sign-in, recheck [Confirm MCP access](#confirm-mcp-access).

<!-- screenshot: Settings > Identity with User Identity selected, the Amplitude provider for the region, and Auto-Configure; values redacted -->

This guide covers setup only. For billing, tool behavior, limits and anything else beyond setup, see [Amplitude's MCP documentation](https://amplitude.com/docs/amplitude-ai/amplitude-mcp).

---

Index of every Speakeasy page for agents: [llms.txt](https://www.speakeasy.com/llms.txt). AI control plane and MCP gateway content in one file: [llms-full.txt](https://www.speakeasy.com/llms-full.txt). Any page is available as markdown by appending `.md` to its URL or by requesting it with `Accept: text/markdown`.
