Amplitude can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:
- Official — Agen.co connects through Amplitude's own hosted MCP server, so your AI agents use the same analytics, experimentation, and taxonomy tools available in the Amplitude product itself.
- In-house — Agen.co wraps Amplitude's Dashboard REST, Cohorts, and Taxonomy APIs directly through its own integration layer, authenticating with a project API Key and Secret Key pair.
Pick Official if Amplitude's MCP server covers what you need — it requires no API Key/Secret Key management and stays in sync with whatever tools Amplitude adds to its MCP server over time. Fall back to In-house if you need an API surface Amplitude's MCP server doesn't expose yet.
Prerequisites
Prerequisites
- An active Amplitude account with access to the project(s) you want your agents to query
- Knowledge of which data residency region your Amplitude organization uses (US or EU) — check with your Amplitude admin if you're not sure
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the search bar, type
Amplitudeand select it from the results. - Fill in the fields:
| Field | Required | Description |
|---|---|---|
| Instance Slug | No | Distinguishes multiple instances of this MCP connector — it prefixes each imported tool as slug__tool. Use lowercase kebab-case; leave empty for a single instance. This value is immutable after creation. |
| Amplitude region | Yes | Selects which of Amplitude's two regional MCP servers Agen.co connects to. Use mcp if your Amplitude organization stores data in the US (the default, connecting to mcp.amplitude.com). Use the EU option if your organization has EU data residency (connecting to mcp.eu.amplitude.com) — confirm with your Amplitude admin which region your organization is on before connecting. |
- Click Connect.
You're redirected to Amplitude to sign in and approve access — Amplitude's MCP server uses OAuth 2.0, so no Client ID, Client Secret, or API key needs to be entered manually.
Once connected, Amplitude appears under My connectors with tools spanning:
| Area | What it covers |
|---|---|
| Analytics & visualization | Querying charts and dashboards, creating charts from natural language, building dashboards, and working with notebooks |
| Data management | Searching events and properties, querying cohorts and segments, accessing and creating metrics, managing taxonomy (events, properties, transformations, group types) |
| Experimentation | Creating and monitoring A/B tests, analyzing experiment results, managing feature flags and guardrail metrics |
| User intelligence | Ad-hoc segmentation, funnel and retention analysis, comparing user journeys |
| Debugging & monitoring | Querying session replays, identifying friction patterns, auditing UX flows, tracking error data |
| Content & feedback | Guides, surveys, and customer feedback analysis |
| Governance | Tracking plan branches, event definitions, user properties, and data quality validation |
| AI agent analytics | Monitoring agent performance, user topics and questions, and session failure investigation |
Enabling the Amplitude connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.