Amplitude is an anchor product-analytics platform because its first-party tenant MCP spans behavioral analysis, dashboards, experiments, feature flags, cohorts, session replay, feedback, and tracking-plan governance, with project-level read and write controls.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Organizations and projects; charts, dashboards, and notebooks; events, properties, transformations, group types, and tracking-plan branches; experiments and feature flags; cohorts and metrics; session replays; feedback and opportunities; Guides and Surveys content; and AI-agent analytics.
Search and inspect Amplitude content; run ad hoc segmentation, funnel, and retention queries; analyze experiments; inspect users, cohorts, metrics, taxonomy, session replays, feedback, Guides and Surveys, and AI-agent quality, cost, and error data within permitted projects.
Create and edit charts, dashboards, notebooks, experiments, cohorts, feature flags, and metrics; manage event and property taxonomy, transformations, group types, and tracking-plan branches; and modify supported Guides and Surveys content. `create_events` registers tracking-plan definitions and does not ingest production event traffic.
The remote server uses Amplitude OAuth 2.0 and inherits existing project access. Organization administrators control an all-clients MCP toggle that is enabled by default. Per-project RBAC actions `USE_MCP_READ` and `USE_MCP_WRITE` can be assigned through roles to users, groups, or MCP service accounts and override administrator status on every tool call.
Amplitude evaluates `USE_MCP_READ` and `USE_MCP_WRITE` per project on each call, even though disallowed tools remain visible in the client's tool list. Show the project and intended read or write action before invocation, and review the connected AI provider's handling of Amplitude data because that provider processes returned content.
The tenant MCP is not an event-ingestion endpoint and is distinct from Amplitude's unauthenticated read-only Docs MCP. US and EU-residency endpoints are separate. Some AI clients can truncate large charts or query dashboard charts with default settings instead of saved dashboard filters; progressive discovery is optional and must be enabled in the URL.
First-party access
Agent access
Support: Official MCP server
Read scope: Project-scoped analytics and content retrieval across segmentation, funnels, retention, experiments, dashboards, notebooks, cohorts, metrics, taxonomy, session replay, feedback, in-product content, and AI-agent performance.
Write scope: Project-authorized creation and editing of analytical content, experiments, feature flags, cohorts, metrics, taxonomy, and tracking-plan branches, plus supported Guides and Surveys operations. Production or high-volume event ingestion remains with Amplitude SDKs or HTTP V2, not MCP.
Authentication: OAuth 2.0 to Amplitude over remote Streaming HTTP. Use `https://mcp.amplitude.com/mcp` for US-resident data or `https://mcp.eu.amplitude.com/mcp` for EU-resident data; authenticate to one Amplitude organization during the OAuth flow.
Approval boundary: Amplitude documents permission checks but not a universal MCP confirmation dialog. BYO-UI should confirm persistent writes to dashboards, notebooks, experiments, flags, cohorts, metrics, taxonomy, tracking-plan branches, and in-product content, displaying the target project and object before the tool call.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Amplitude ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Tenant MCP product surfaces, read/write boundary, remote Streaming HTTP deployment, US/EU residency endpoints, OAuth, organization switch, project RBAC, progressive discovery, and client caveats
Full first-party tenant-MCP scope, region, auth, RBAC, and limitation review completed 2026-07-22
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Amplitude SQL supports custom analysis against an Amplitude-managed Snowflake database. The feature is package and region dependent and is documented as unavailable in the EU environment.
Targeted first-party access review
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
