Support EU region (app.eu.amplitude.com) in MCP configuration

[misterbridge]

Problem

The plugin's .mcp.json hardcodes the US MCP endpoint:

{
  "mcpServers": {
    "amplitude": {
      "type": "http",
      "url": "https://mcp.amplitude.com/mcp"
    }
  }
}

Users on Amplitude's EU instance (app.eu.amplitude.com) cannot use the plugin out of the box — the MCP server connects to the wrong region and returns no data.

Workaround

Manually editing the .mcp.json to point to the EU endpoint works:

"url": "https://mcp.eu.amplitude.com/mcp"

Suggestion

• Environment variable (e.g. AMPLITUDE_REGION=EU or AMPLITUDE_MCP_URL) to configure the region without patching plugin files
• Auto-detect region from the user's Amplitude org during the OAuth flow — this would make it seamless
• For now, documenting the EU endpoint in the README would already help EU users get started

[ekim-amplitude]

Unfortunately the .mcp.json only supports one endpoint; we have communicated to the protocol maintainers that this is a support issue.

The env var idea is not particularly helpful bc if people knew well enough to set those vars, its actually easier to just modify the endpoint. And the Oauth flow detecting the endpoint doesn't really make sense either since the endpoint is the destination.

Will be simmering on how to improve this. For now, only way is to modify the url :/

[misterbridge]

Thanks for the quick response!

My concern is that every time the plugin updates, the cache is regenerated and the .mcp.json is overwritten — so EU users have to re-apply the change after each update. That's the main pain point.

There are probably several ways to address this (local override, env var, plugin settings, etc.) — I'm sure there's a good solution to avoid EU users having to patch files after every update.

Happy to help test any approach you come up with.