Sixty-five tool definitions in every request is a real cost, and most vendors either ignore it or split into several servers. Amplitude offers a mode where the client starts small and asks for more — the correct fix, and rare. The other thing worth noting is that the taxonomy tools write: an agent here can rename events and change their official status, which is governance data other teams depend on. The admin-level org switch exists for exactly that reason.
Amplitude's endpoint, documented across 13 category tables. It has a progressive discovery mode that starts with a small tool list and lets the client find the rest, which matters when 65 definitions would otherwise ride in every request.
- search and get_from_url — find charts, dashboards, notebooks, experiments, events, cohorts, or resolve any Amplitude URL to its definition
- get_charts, get_dashboard, get_cohorts, get_experiments, get_flags, get_deployments — full definitions including configuration
- get_events, get_properties, get_users — project data with filtering and cursor pagination
- update_properties, update_event, update_custom_or_labeled_events — edit the taxonomy: names, descriptions, categories, official status
- get_agent_results — output from Amplitude's own AI agents over dashboards and session replays
- get_amplitude_context and get_workspace_context — who you are, which projects you can reach
OAuth against your Amplitude account, scoped by the organisation's RBAC. Free for every customer including the Free plan. Org admins can allow or block MCP org-wide under Settings → Content Access → MCP, and users cannot override that.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen