# Amplitude setup for PopMCP You paste two values for one Amplitude project: its API Key and a Secret Key, which Amplitude shows only when you generate it. Optional extra keys under More options add saved charts, Experiment and Enterprise organization tools. - Auth: API credentials - Setup time: 5 min - API base URL: https://amplitude.com (EU projects: https://analytics.eu.amplitude.com); ingestion, Experiment and the Developer API use their own hosts - Credentials screen: https://app.amplitude.com/ - Provider docs: https://amplitude.com/docs/apis/authentication ## Before you begin - The Manager or Admin role in Amplitude, because only Managers and Admins can see and generate API keys and secret keys - The Amplitude project you want to connect. One PopMCP connection is one project. - No region to look up: PopMCP detects US or EU data residency itself - Optional extras only if you need them: Experiment for the Experiment keys, and an Enterprise plan for the SCIM and organization keys ## Get your credentials ### 1. Open API Keys in Organization settings In Amplitude, click Settings (the gear icon) and choose Organization settings, then select API Keys in the side navigation and pick the project you want to connect. Only Managers and Admins see this page. Screen: https://app.amplitude.com/ ### 2. Copy the project's API Key Copy the project's existing API key (32 characters), or click Generate API Key, name it `PopMCP` and copy the new one. The API Key identifies the project; on its own it can't read any data. Screen: https://app.amplitude.com/ ### 3. Generate a Secret Key and copy it once Click Generate Secret Key, name it `PopMCP` and copy it into a safe place straight away. Amplitude doesn't store secret keys, so this one can't be shown or retrieved again. Screen: https://app.amplitude.com/ ### 4. Optional: collect extra keys for the tools you need Skip this for charts, funnels, retention, users, cohorts, export, taxonomy, annotations and ingestion, which the two project keys already cover. A Personal Access Token (your profile settings, Personal access tokens) adds saved charts (`list_saved_charts`, `query_saved_chart`), the project list, destinations, heatmaps and the newer taxonomy and flag endpoints, acting with your own permissions. An Experiment Management API key (in Experiment, Management API at the bottom left of the sidebar) adds flags, experiments, deployments, mutex and holdout groups, and lets `evaluate_variants` pick a deployment. An Experiment deployment key (Experiment, Deployments; starts `server-` or `client-`) only evaluates flags against that one deployment. A SCIM key (Enterprise: Organization settings, Access and SSO settings, Provisioning, Generate SCIM key) adds user and group provisioning. The Organization API key and Organization secret key (Enterprise, issued by Amplitude Support) add data access requests, audit logs and role management; the organization secret key alone adds org-wide user deletion. ### 5. Paste the keys into PopMCP Paste into API Key and Secret Key. If you collected extras, open More options and fill the matching fields: Personal Access Token (optional), Experiment Management API key (optional), Experiment deployment key (optional), SCIM key (optional, Enterprise), Organization API key (optional, Enterprise) and Organization secret key (optional, Enterprise). Leave Organization ID (optional) and Project ID (optional) blank unless a tool asks for them. ## Fields PopMCP asks for - API Key (apiKey) [required]: In Amplitude: Settings (gear icon) > Organization settings > Projects > pick the project > General > API Key. Only Admins and Managers can see it. One connection is one project. - Secret Key (secretKey) [required]: On the same General tab: Secret Key (Manage > copy). Newer projects show it only once, under Organization settings > API Keys. Stored encrypted. - Personal Access Token (optional) (personalAccessToken): Unlocks saved charts (find by name, run), the project list, destinations, heatmaps and the newer taxonomy and flag endpoints. Create it in Amplitude under your profile settings > Personal access tokens. It acts with your own permissions. - Experiment Management API key (optional) (managementApiKey): Unlocks feature flags, experiments, deployments, mutex and holdout groups, and lets the evaluation tools pick a deployment for you. In Amplitude: Experiment > Management API (bottom of the left sidebar) > Create API key. - Experiment deployment key (optional) (deploymentKey): Only for evaluating flags against one specific deployment without a management key. Experiment > Deployments > copy the key. - SCIM key (optional, Enterprise) (scimKey): Unlocks SCIM user and group provisioning. Organization settings > Access and SSO settings > Provisioning > Generate SCIM key (shown once). - Organization API key (optional, Enterprise) (orgApiKey): With the organization secret key, unlocks data access requests (DSAR), audit logs and role management. Issued by Amplitude Support. - Organization secret key (optional, Enterprise) (orgSecretKey): Pairs with the organization API key. On its own it also unlocks org-wide user deletion (Settings > API Keys > Org-level Secret Keys). - Organization ID (optional) (orgId): Needed by the organization-level tools. Found automatically when you add a Personal Access Token; otherwise copy it from Organization settings. - Project ID (optional) (projectId): Usually found automatically. Set it if tools ask for a project id: Settings > Organization settings > Projects > General > Project ID. ## Verify PopMCP shows Amplitude as Verified with a label such as `project 123456 (US)`, or the organization and project names when a Personal Access Token supplied them. Ask which events were tracked last week: amplitude_list_events returns your event names instead of an Invalid API Key error. ## Troubleshooting ### "Amplitude rejected this API Key and Secret Key on both its US and EU data centers" Cause: One of the keys was mis-copied or revoked, or the Secret Key belongs to a different project than the API Key. Fix: Copy the API Key again and generate a fresh Secret Key on the same project under Organization settings, API Keys, then reconnect. ### "The API Key and Secret Key are the same value" Cause: The API Key was pasted into both fields. Fix: Generate a Secret Key for the project and paste it into Secret Key. The two are always different strings. ### "Amplitude rejected the Personal Access Token" (or another optional key) Cause: The extra key was revoked, mis-copied, or belongs to another organization or region than the project. Fix: Create a new one where the field's help says, or leave that field blank: the connection works without it. ### A tool says it needs an Experiment Management API key, a SCIM key or organization keys Cause: That tool belongs to an API the two project keys can't reach. Fix: Add the named key under More options on the connection. The error message says where to create it in Amplitude. ### 429 from chart, funnel or user tools Cause: Amplitude allows 5 concurrent REST requests per project and a cost budget per hour and per five minutes; User Activity and User Search are capped at 360 queries an hour. Fix: Wait a few minutes, then ask for fewer charts at once or a shorter date range. ### get_user_profile fails on an EU project Cause: Amplitude offers the User Profile API for US projects only. Fix: Use search_users and get_user_activity instead, which work in both regions. ### Event export says the file is larger than 50 MB Cause: The requested hours hold more raw event data than PopMCP downloads in one call. Fix: Ask for a narrower UTC hour range, or filter by event type or user. --- Source: https://www.docs.popmcp.com/docs/integrations/amplitude/