How to connect Amplitude to Codex

1. 1. Enable Amplitude in Metorial

   In your Metorial portal, enable the Amplitude MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

2. 2. Add the server and sign in

   The Codex CLI, IDE extension and ChatGPT desktop app share this config.

   Copy

   codex mcp add metorial --url <your-magic-mcp-url>
   codex mcp login metorial

3. 3. Check the connection

   Type /mcp in Codex to see Metorial and its Amplitude tools.

• Track Events: Send one or more events to Amplitude for analytics tracking with user properties, event properties, revenue data, and selected device metadata.
• Get Chart Results: Download results from a saved Amplitude chart by its chart ID.
• Manage Annotations: Manage chart annotations in Amplitude.
• Manage Cohorts: List, retrieve, create, or update behavioral cohorts in Amplitude.
• Get User Profile: Retrieve an Amplitude user profile including user properties, computed properties, and synced cohort memberships.
• Query Event Segmentation: Analyze event data with segmentation, filtering, and grouping.
• Query User Composition: Analyze the distribution of a user property across your active users.
• Query Sessions: Retrieve session metrics including session length distribution, average duration in seconds, and average sessions per user over a date range.
• Delete User Data: Request deletion of user data from Amplitude for privacy compliance (GDPR/CCPA).
• Query Active Users: Retrieve daily, weekly, or monthly active and new user counts for the project already selected by the API-key connection.
• Manage Taxonomy: Manage your Amplitude tracking plan (taxonomy).
• Identify User: Set or update user properties for a specific user without sending an event.
• Query Funnel: Analyze conversion funnels to understand how users progress through a sequence of events.
• Query Retention: Analyze user retention to understand how well users are retained over time after performing a starting event.
• Export Events: Export Amplitude raw event files for an uploaded-time range as a downloadable ZIP file.
• And 20 more on the Amplitude MCP server page.

• Limit which Amplitude tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
• Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
• Type /mcp in the composer to see the connected servers.
• Override the approval behavior for a single Amplitude tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Metorial times out at startup

Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.

Long tool calls fail after a minute

The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.