On this page

How to connect Amplitude MCP to other MCP clients

The Amplitude MCP server works with any MCP-compatible client, not just the ones listed in this section. If your client supports remote MCP servers over HTTP with OAuth, you can connect it to Amplitude in a few steps. Use this guide when your client isn't listed in the sidebar.

You need an active Amplitude account with project access and an MCP client that supports remote HTTP servers and OAuth authentication.

How do I connect Amplitude MCP to an unlisted client?

  1. Configure your client to connect to the Amplitude MCP server URL:

    • US (default): https://mcp.amplitude.com/mcp
    • EU residency: https://mcp.eu.amplitude.com/mcp

  2. Ensure your client supports OAuth authentication for remote MCP servers.

  3. Set up the connection according to your client's MCP documentation.

  4. Authenticate with your Amplitude account when prompted using OAuth.

  5. Select which Amplitude tools to enable based on your needs.

How do I verify the connection works?

Ask your MCP client: "What Amplitude projects can I access?" If you see a list of your projects, MCP is connected and authenticated.

What transport protocol does the Amplitude MCP server use?

The Amplitude MCP server uses Streaming HTTP (remote) transport. Your client must support this transport type to connect. Clients that only support stdio-based local servers aren't compatible.

Does my client need to support OAuth specifically?

Yes. The Amplitude MCP server uses OAuth 2.0 for authentication. Clients that support only API key authentication or no authentication can't connect.

How do I report a connection issue with an unlisted client?

Was this helpful?