Amplitude

Connecting Amplitude lets an agent check event volume and feature adoption after a change ships, instead of assuming the release landed well.

Before you start

You need an Amplitude account with the Use MCP (read) permission. Every role grants it by default, though an admin can restrict it per project or per role. Amplitude's own guide is MCP.

There is no key to create. You authorize the connection by signing in to Amplitude in your browser.

Connect it

1. In SetForth, open your project, then Integrations.
2. Choose Amplitude.
3. Leave the server URL as https://mcp.amplitude.com/mcp, or use https://mcp.eu.amplitude.com/mcp if your Amplitude data is in the EU region.
4. Choose Connect. You go to Amplitude, sign in, and approve the access.
5. Amplitude sends you back to SetForth and the integration is connected.

Sign in to one Amplitude organization at a time while you do this. Being signed in to several is the usual reason the authorization fails.

What agents can check

Connecting a product analytics tool adds three follow-ups:

• Verify event tracking confirms the events a task promised to emit actually fire in production. You name the events and how long to watch for.
• Measure feature adoption reports how many people touched the new surface, and fails when unique users stay below the minimum you set. A feature nobody uses is a result worth knowing, and the agent gets it back rather than closing the task.
• No metric regression flags a task when a funnel step drops against its pre-release baseline by more than the tolerance you allow.

You set the window, the thresholds, and which events or funnel to watch when you add the follow-up during planning.

Who the connection belongs to

The connection carries the access of whoever authorized it. Its page in SetForth shows who that was. If they leave or lose access in Amplitude, the integration stops working and Reconnect hands it to someone else.