Integrations · Analytics

Connect Amplitude to Well

Name: Amplitude entities in Well
Creator: Well

Bring your Amplitude product analytics into Well through its MCP server. Events and cohorts read across the connection sit beside the companies and people they describe, so behavioural signal lands in the same workspace as the rest of your stack.

Connect AmplitudeSee what Well does

What Well pulls from Amplitude

Amplitude feeds event, user, cohort into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Amplitude’s access.

From Amplitude	In Well	Relation
Event	Behavior signal	Feeds
User	Person	Resolves to
Cohort	Segment	Groups under

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Amplitude → Well

What Well does with your Amplitude connection

Connect

Connect Amplitude over OAuth (MCP DCR): Well registers a client through Amplitude's OAuth Dynamic Client Registration and you approve on Amplitude's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings event, user, and cohort in from Amplitude on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Amplitude entity into behavior signal, person, and segment, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Amplitude lands in the workspace as behavior signal, person, and segment you can search, chart, and automate.

Questions Amplitude unlocks

Ask in plain language. Well answers from your connected Amplitude connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Amplitude connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Amplitude connection…

Connect Amplitude in three steps

01
Authorise Amplitude over MCP
Open Amplitude in Well's Connections panel and begin. Well discovers the OAuth metadata at the Amplitude MCP server, registers itself through Dynamic Client Registration, and hands you to Amplitude to approve the read scopes. The selection of what Well may read stays yours.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.amplitude.com/mcp
02
Map your entities
Well reads events, cohorts, and the users behind them, resolving each user to a person and each account to a company through Well's data-views layer so behavioural signal lands against the right record.
- Mappingpreconfigured by Well
03
Use the data
Then rank cohorts by activation in conversation, surface the behaviour that precedes a paid conversion, or let an agent join product usage to the deal it affects. Amplitude is an INPUT connector, so the read runs one way and nothing is written back.
- First syncstarts as soon as connect completes

Connecting completes in about a minute. Recent activity is read on connect; the longer cohort and event history backfills in the background so questions answer while it fills in.

How Amplitude stays secure with Well

Amplitude connects through its MCP server at mcp.amplitude.com over the Model Context Protocol, and the OAuth Dynamic Client Registration handshake keeps the Amplitude credential with Amplitude rather than with Well. The token covers only the events and cohorts you put in scope and refreshes server-side. Well reads behavioural signal; it has no ability to send an event or alter a chart in Amplitude.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.amplitude.com/mcp

Read Amplitude records
Resources the Amplitude MCP server exposes, scoped by your OAuth approval.
granted
Resolve event, user, and cohort across your stack
Match identifiers in Amplitude against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Amplitude records
Not granted; Amplitude is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Amplitude passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Amplitude’s admin panel.

Frequently asked questions about Amplitude and Well

Choose Amplitude in Well's Connections panel and begin the handshake. Well discovers the OAuth metadata at the Amplitude MCP server, registers a client through Dynamic Client Registration, and routes you to authorise the read scopes on Amplitude's screen. Nothing to paste, and the consent step keeps the choice of what Well may read with you.

Amplitude is a product-analytics tool, so Well reads the events, cohorts, and the users behind them across the connection. The read is one-way: Well pulls behavioural signal in and never sends an event or edits a chart back in Amplitude. The data lands in your workspace context beside the customer and revenue records you already hold.

Amplitude maps to the people and company entities, so a tracked user resolves to a person in the workspace and an account to a company. The events and cohorts Well reads then feed signal against those records, which lets a question like which accounts hit an activation event this week answer from the same place that holds their deals and billing.

Yes. Because cohorts arrive as workspace signal joined to the people and companies they describe, an agent can rank cohorts by recent activation events or surface the behaviour that precedes a paid conversion, and answer from your workspace. Each cohort keeps its size and the event that defines it, so the answer carries the evidence behind it.

Well reads events and cohort state through the Amplitude MCP connection and folds new behavioural signal in as it is read, with the first connect pulling the available history in the background. Amplitude stays the system of record for your product analytics; Well keeps a queryable copy so behaviour sits next to the revenue and CRM data in your workspace.

Disconnecting Amplitude in Well revokes the token and ends the reads against your project at once; the connection only ever read, so there is nothing posted back to unwind. The events and cohorts already mirrored stay in your workspace for historical questions. To stop Amplitude sharing the underlying data entirely, remove Well's access from Amplitude as well.