Integration · Research and analyze

Amplitude and Meteor AI agents

Connect Amplitude to a Met: query funnels, retention, charts, cohorts and experiments for your product with the official MCP.

Book a demo See every integration

How does Amplitude connect to Meteor?

With the Amplitude ready connector, your Met queries your Amplitude project with the permissions of the account the admin authorizes. It searches charts, dashboards, cohorts and experiments, runs segmentation, funnel and retention queries, reads an experiment's result and the customer feedback Amplitude has already grouped by theme. It also creates experiments and metrics, edits dashboards and registers events in the tracking plan, if the admin leaves those actions on in Connections. Amplitude is not a channel to send production events: its SDKs and API remain the way to do that.

What it automates

What a Meteor Met does with Amplitude

Answer how a funnel is doing

You ask the Met how many people completed sign up this week. The Met runs the funnel query and replies with the conversion of each step.

Read an experiment's result

The Met brings the experiment, queries each variant's performance and tells you whether the difference is significant or more traffic is needed to decide.

Listen to what your customers ask for

If you connected feedback sources in Amplitude, the Met summarizes the most repeated themes: feature requests, bugs and complaints, with sample comments.

Review a user's case

When support needs context, the Met brings that user's profile and recent activity, and looks for their session replays if you have Session Replay.

22 tools

Everything your Met can ask Amplitude for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`search`	Searches charts, dashboards, notebooks, experiments, events, properties and cohorts in Amplitude.
`get_from_url`	Returns the full definition of an object from its Amplitude link.
`query_amplitude_data`	Runs segmentation, funnel and retention queries, or queries an existing chart by its ID.
`render_amplitude_chart`	Builds a chart from a query and returns the link to edit it in Amplitude.
`use_amplitude_chart_monitors`	Creates, reads and manages a chart's alerts and monitors, with their history.
`use_amp_dashboards`	Gets, creates and edits dashboards, including title, description and chart order.
`use_amp_notebooks`	Gets, creates and edits notebooks with charts and text.
`use_amp_comments`	Reads and adds comments on Amplitude content.
`share_amp_entities`	Manages who charts, dashboards and notebooks are shared with, and with which role.
`use_amplitude_cohorts`	Gets, creates and syncs cohorts, checks whether someone belongs to one and exports its CSV.
`get_amp_user_data`	Returns a project user's profile, properties and activity timeline.
`get_experiments`	Returns experiments by ID with their state, variants and decision.
`query_experiment`	Queries an experiment's analysis, with each variant's performance and its significance.
`create_experiment`	Creates A/B experiments with their own variants and metrics.
`create_metric`	Creates reusable metrics for experiments or dashboards.
`get_flags`	Returns a feature flag's definition by ID, with its variants and configuration.
`get_amp_taxonomy`	Reads a project's tracking plan, with its events, properties and change history.
`manage_amp_events`	Creates, updates, deletes and restores events in the tracking plan. Needs the MCP write permission.
`get_session_replays`	Searches session replays from the last 30 days, filtered by user properties or events.
`get_session_replay_events`	Returns the interaction timeline of a session replay.
`use_amplitude_ai_feedback`	Analyzes customer feedback from connected sources, grouped into requests, bugs, complaints and praise.
`get_data_ingestion_sources`	Lists the sources that send data to the project, such as SDKs, imports and integrations.

The limits

What the Amplitude integration does NOT do

We would rather say it here than have you find out during rollout.

It does not receive production events. Amplitude states that its MCP is not an ingestion channel: events are still sent with its SDKs or its API.
It does not write to the tracking plan without permission. Creating, changing, deleting or restoring events needs the MCP write permission in Amplitude, besides the action being on in Met.
It does not use the Europe server. The connector points to Amplitude's standard server; accounts with data in the Europe region use another server.
It does not ask you for confirmation in the chat before writing. The admin decides in Connections which actions stay on.
It does not pay your Amplitude plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Amplitude

1

An Amplitude account

Any Amplitude customer can use its MCP. The Met sees what the permissions of the account that authorizes the connection allow.
2

Connect it in Met

In Met, open Connections → Amplitude → Connect. An Amplitude window opens so you sign in and authorize Met.
3

Write permission for the tracking plan

Only if you want the Met to create or change events: the account needs the "Use MCP (write)" action in Amplitude and permission to update the tracking plan.

Frequently asked questions

Questions about Amplitude and Meteor

Yes. The Met builds the chart from a query and returns the link to open and edit it in Amplitude.

Yes, if the action is on in Met and the account has the MCP write permission in Amplitude. The same tool restores deleted events, except planned ones that never received data and custom or labeled events: Amplitude cannot restore those.

Yes, if your account has Session Replay. The Met searches replays from the last 30 days and brings a session's interaction timeline.

You do, with your Amplitude account and plan. Met does not charge for the queries your Met makes to Amplitude.

Step by step