Think inside your AI world.

How do I connect Amplitude to Claude?

Amplitude's MCP server hands Claude the charts, dashboards, experiments, flags and metrics — the read layer of a mature analytics practice.

Direct answer: connect Amplitude's MCP server from Claude's Settings → Connectors and authorise ('claude mcp add' in Claude Code). Claude then reads charts, dashboards, experiments, feature flags and metrics from your project — the questions you would normally answer by assembling views, answered in conversation.

Metrics without the dashboard shuffle

How the chart moved since the release, what the experiment's arms show, which flags are live in production, whether the dashboard's north-star panel actually shifted — read from the project directly. Analysts save clicks; founders skip the interface entirely.

One metric, two honest definitions

Worked case: your team ratified a retention definition — day-30 return, not day-7, is the number decisions cite, because day-7 once flattered a cohort that had evaporated by the month mark. Amplitude computes both flawlessly. Which one is decision-grade in your company is a ruling about the metrics, invisible to the metrics.

Charts read under your definition

Through Unl the retention read arrives pre-framed: day-30 for the March cohort, the figure your ruling makes citable — with day-7 labelled as the flattering cousin your team retired for decisions. Metric disputes end at read time rather than mid-meeting.

Amplitude to Claude reads the metrics; Amplitude through Unl reads the metrics under the definitions you ratified — so the number that arrives is the one your decisions are allowed to cite.

Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Read further

Questions people ask

What is on Amplitude's MCP read surface?

Charts, dashboards, experiments, feature flags and metrics — the observational layer of the product-analytics stack, readable in conversation.

Does the server work beyond Claude?

Yes; 'amplitude mcp' connects identically from ChatGPT or any MCP client. The protocol is shared, the steps near-identical.

Why ratify a metric definition rather than document it?

Documentation waits to be consulted; a ratified definition arrives at read time, applied. When the wrong cousin of the metric shows up in a conversation, the ruling — and the cohort story behind it — shows up with it.

What this is

Think inside your AI world — you stay in command

Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.

It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.

Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:

Alpha is invite-only · free at launch.