PostHog MCP for Zed

The PostHog MCP server enables Zed to directly interact with your PostHog data – managing feature flags, querying analytics, investigating errors, and more.

Server URL

Quick install

The PostHog Wizard can install the MCP server directly into Zed:

npx @posthog/wizard mcp add

Manual setup

1. Open Zed and update settings.json with the following configuration:

{
  "context_servers": {
    "posthog": {
      "enabled": true,
      "url": "https://mcp.posthog.com/mcp"
    }
  }
}

2. Save the configuration file
3. The PostHog MCP server will be available

When you first use the MCP server, you'll be prompted to log in to PostHog to authenticate.

Be mindful of prompt injection – LLMs can be tricked into following untrusted commands, so always review tool calls before executing them.

{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp",
      "headers": {
        "Authorization": "Bearer phx_your_api_key_here"
      }
    }
  }
}

{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp",
      "headers": {
        "Authorization": "Bearer phx_your_api_key_here",
        "x-posthog-organization-id": "your_org_id",
        "x-posthog-project-id": "your_project_id"
      }
    }
  }
}

https://mcp.posthog.com/mcp?features=flags,dashboards,insights

{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp?features=flags,experiments,insights",
      "headers": {
        "Authorization": "Bearer phx_your_api_key_here"
      }
    }
  }
}

Available tools

Tools trigger actions on behalf of the user based on the goals and information already in the context of the LLM.

Here's a list of tools we provide:

Example prompts

Here are some examples of what you can ask your AI agent to do with the PostHog MCP server:

Feature flag management

Prompt: "Create a feature flag called 'new-checkout-flow' that's enabled for 20% of users"

The agent will use the create-feature-flag tool to create the flag with a 20% rollout and return the configuration including the key, rollout percentage, and a link to the flag in PostHog.

Multivariate feature flags

Prompt: "Create a multivariate feature flag called 'homepage-hero-test' with three variants: control at 34%, variant_a at 33%, and variant_b at 33%"

The agent will use the create-feature-flag tool with a multivariate configuration to create the flag with multiple variants. Variant rollout percentages must be integers that sum to 100.

Analytics queries

Prompt: "How many unique users signed up in the last 7 days, broken down by day?"

The agent will use the query-run tool to execute a trends query and return daily signup counts.

Path analysis

Prompt: "What are the most common paths users take after signing up?"

The agent will use the query-run tool with a PathsQuery to analyze user journeys, returning the flow of events users follow after signup.

Prompt: "Show me the navigation paths from the pricing page to checkout"

The agent will execute a paths query with startPoint set to the pricing page and endPoint set to checkout, revealing the most common routes users take.

SQL and HogQL queries

Your AI agent can execute complex HogQL queries to analyze both system data and analytics data in PostHog.

Prompt: "Query my feature flags to find all flags that are rolled out to less than 50% of users"

The agent will use SQL to query the system.feature_flags table and return flags filtered by rollout percentage.

Prompt: "Write a HogQL query to find users who triggered the signup event but didn't complete onboarding in the last 30 days"

The agent will construct and execute a HogQL query against the events table, using subqueries to find users who signed up but are missing the onboarding completion event.

Prompt: "What cohorts contain users who made a purchase in the last week?"

The agent will query system.cohorts and cross-reference with purchase events to identify relevant cohorts.

A/B test creation

Prompt: "Create an A/B test for our pricing page that measures conversion to checkout"

The agent will use experiment-create to set up an experiment with control/test variants and configure a funnel metric measuring pricing page to checkout conversion.

Error investigation

Prompt: "What are the top 5 errors in my project this week?"

The agent will use the list-errors tool to fetch error groups sorted by occurrence count and return details including affected user counts.

Log investigation

Prompt: "Show me error logs from the payments service in the last hour"

The agent will use logs-query to search for logs filtered by severity level and service name, returning log entries with timestamps, messages, and trace information.

Prompt management

Prompt: "List all prompts stored in my project"

The agent will use the prompt-list tool to retrieve all team prompts and return a summary with names, versions, and timestamps.

Prompt: "Create a prompt called 'code-reviewer' with instructions for reviewing pull requests"

The agent will use the prompt-create tool to create a new prompt with the specified name and content, making it available for use across all MCP-connected agents in your team.

Prompt: "Get the latest version of my 'support-assistant' prompt"

The agent will use the prompt-get tool to retrieve the full prompt content by name. You can also request a specific version if needed.

Prompt: "Update the 'onboarding-guide' prompt to include a section about feature flags"

The agent will use the prompt-update tool to publish a new version of the prompt with the updated content. The update includes conflict detection to prevent overwriting changes made by others.

Prompts and resources

The MCP server provides resources, including framework-specific documentation and example code, to help agents build great PostHog integrations. You can try these yourself using the posthog:posthog-setup prompt, available via a slash command in your agent. Just hit the / key.

Currently we support Next.js, with more frameworks in progress.

Privacy and support

• Privacy Policy: posthog.com/privacy
• Terms of Service: posthog.com/terms
• Support: posthog.com/questions or in-app support

The MCP server acts as a proxy to your PostHog instance. It does not store your analytics data – all queries are executed against your PostHog project and results are returned directly to your AI client.