Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: Basic auth.
  • Connection: HTTP Basic auth with AMPLITUDE_API_KEY as the username and AMPLITUDE_SECRET_KEY as the password.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Find your project credentials: In Amplitude, go to Settings → Organization settings → Projects, pick your project, and copy the API Key and Secret Key. Free Starter plans include Dashboard REST API access for testing.
  2. Store the keys: Add them to your .env file as AMPLITUDE_API_KEY=… and AMPLITUDE_SECRET_KEY=… Both are required because the analytics APIs use HTTP basic auth (api_key:secret_key).
  3. Check your data residency: If your org uses EU data residency, set AMPLITUDE_HOST=analytics.eu.amplitude.com and AMPLITUDE_INGEST_HOST=api.eu.amplitude.com in your .env. US orgs can keep the defaults.
  4. Verify access: Run the List Events tool. A 401 means the key pair is wrong; a 403 can mean the keys belong to a different project or region.

​
Provider notes

  • Keys are per-project, so use a test project’s keys when experimenting, since Track Event writes real analytics data
  • The HTTP V2 ingestion API authenticates with the project API key inside the request body, so Track Event asks for api_key as a body field (same value as AMPLITUDE_API_KEY; the secret key is never sent)
  • Dashboard REST API endpoints are rate limited per project, so keep date ranges modest
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as amplitude__list_events with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.