Does Codex support the Posthog MCP server?

Yes. Codex connects to the Posthog MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

Do I need an API key to connect Posthog to Codex?

No. You sign in to Posthog once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.

Which Posthog tools can Codex use?

All 56 Posthog tools your team allows, such as Create Experiment, List Session Recordings, List Insights. Admins can narrow that list per team.

Can I control which teammates use Posthog in Codex?

Yes. Role-based access control decides who can use Posthog and which of its tools appear in Codex, and every call is logged with the person's identity.

What if Codex doesn't show Posthog tools?

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

Connect Posthog to Codex (MCP setup guide)

Ask Codex to use the get dashboard tool in Posthog
Ask Codex to use the update survey tool in Posthog
Ask Codex to use the list feature flags tool in Posthog
Ask Codex to use the get session recording tool in Posthog
Ask Codex to use the create survey tool in Posthog

1. Enable Posthog in Metorial
In your Metorial portal, enable the Posthog MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Posthog tools.

Once Posthog is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Create Experiment: Create a new A/B test experiment.
List Session Recordings: List session recording metadata.
List Insights: List analytics insights (trends, funnels, retention, paths, stickiness, lifecycle).
List Property Definitions: List all property definitions in the project.
List Cohorts: List all cohorts in the project.
Capture Event: Send one or more events to PostHog.
Get Feature Flag: Retrieve detailed information about a specific feature flag by its ID.
Get Experiment: Retrieve detailed information about a specific A/B test experiment including its configuration, metrics, and results.
Delete Feature Flag: Permanently delete a feature flag.
Delete Survey: Permanently delete a survey.
Get Insight: Retrieve detailed information and results for a specific insight by its ID.
Create Dashboard: Create a new dashboard for organizing insights and analytics visualizations.
List Projects: List projects accessible with the current credentials.
List Event Definitions: List all event definitions in the project.
List Persons: Search and list person profiles in PostHog.
And 41 more on the Posthog MCP server page.

Limit which Posthog 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 Posthog 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.

Frequently asked questions

Common questions about connecting Posthog to AI agents with Metorial.

Does Codex support the Posthog MCP server?
Yes. Codex connects to the Posthog MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Posthog to Codex?
No. You sign in to Posthog once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Posthog tools can Codex use?
All 56 Posthog tools your team allows, such as Create Experiment, List Session Recordings, List Insights. Admins can narrow that list per team.
Can I control which teammates use Posthog in Codex?
Yes. Role-based access control decides who can use Posthog and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Posthog tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.