Model Context Protocol (MCP)

The PostHog Model Context Protocol (MCP) server enables your AI agents and tools to directly interact with PostHog's products.

Quick install using the PostHog wizard

Besides being able to quickly set up your project using AI, the PostHog Wizard can also install the MCP server directly into Cursor, Claude Code, Claude Desktop, VS Code and Zed.

Terminal

npx @posthog/wizard mcp add

We're working on adding more supported tools to the wizard. If you're using another option, you can manually install our MCP server with the instructions below.

Manual install

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

EU region users

If your PostHog project is on EU Cloud, use https://mcp-eu.posthog.com/mcp instead.

Run the following command in your shell. The next time you run Claude Code, it will have access to the PostHog MCP.

Terminal
claude mcp add --transport http posthog https://mcp.posthog.com/mcp -s user

Open Claude Desktop and navigate to Settings > Developer
Click Edit Config to open the configuration file
Update claude_desktop_config.json with the following configuration:

JSON
{
  "mcpServers": {
    "posthog": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.posthog.com/sse"
      ]
    }
  }
}

Save the configuration file and restart Claude Desktop
The MCP server should show as PostHog in your list of Connectors found in Settings > Connectors

Open Cursor and navigate to Cursor Settings > Tools & Integrations
Click New MCP Server
Update mcp.json with the following configuration:

JSON
{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp"
    }
  }
}

Save the configuration file
You should see posthog under MCP Tools with a green status

Open Windsurf and navigate to Windsurf Settings > Cascade > MCP Servers
Click Manage MCP Servers
Click View raw config
Update mcp_config.json with the following configuration:

JSON
{
  "mcpServers": {
    "posthog": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.posthog.com/sse"
      ]
    }
  }
}

Open Visual Studio Code. In the command palette, run: MCP: Open User Configuration to open the configuration file
Update mcp.json with the following configuration:

JSON
{
  "servers": {
    "posthog": {
      "type": "http",
      "url": "https://mcp.posthog.com/mcp"
    }
  }
}

Save the configuration file
The MCP server will now be available the next time you chat with Copilot

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

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

Save the configuration file
The PostHog MCP server will be available

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

Using an API key instead of OAuth?

If your MCP client doesn't support OAuth, you can authenticate manually:

Create a personal API key using the MCP Server preset (this scopes access to a specific project)
Add the Authorization: Bearer YOUR_API_KEY header to your MCP configuration

Example for Cursor (add to .cursor/mcp.json):

JSON
{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp",
      "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. PostHog tools are also available in our agent toolkit which can be integrated with AI agent frameworks like Vercel's AI SDK and LangChain.

Here's a list of tools we provide:

Actions

Tool	Purpose
`action-create`	Create a new action in the project.
`action-delete`	Delete an action by ID.
`action-get`	Get a specific action by ID.
`action-update`	Update an existing action.
`actions-get-all`	Get all actions in the project.

Dashboards

Tool	Purpose
`add-insight-to-dashboard`	Add an existing insight to a dashboard.
`dashboard-create`	Create a new dashboard in the project.
`dashboard-delete`	Delete a dashboard by ID.
`dashboard-get`	Get a specific dashboard by ID, including insights that are on the dashboard.
`dashboard-reorder-tiles`	Reorder tiles on a dashboard.
`dashboard-update`	Update an existing dashboard by ID.
`dashboards-get-all`	Get all dashboards in the project with optional filtering.

Documentation

Tool	Purpose
`docs-search`	Search the PostHog documentation for information.

Error tracking

Tool	Purpose
`error-details`	Get the details of an error in the project.
`list-errors`	List errors in the project.

Events & properties

Tool	Purpose
`event-definitions-list`	List all event definitions in the project with optional filtering.
`properties-list`	Get properties for events or persons.

Experiments

Tool	Purpose
`experiment-create`	Create A/B test experiment with guided metric and feature flag setup
`experiment-delete`	Delete an experiment by ID.
`experiment-get`	Get details of a specific experiment.
`experiment-get-all`	Get all experiments in the project.
`experiment-results-get`	Get comprehensive experiment results including metrics and exposure data.
`experiment-update`	Update an existing experiment with lifecycle management and restart capability.

Feature flags

Tool	Purpose
`create-feature-flag`	Creates a new feature flag in the project.
`delete-feature-flag`	Delete a feature flag in the project.
`feature-flag-get-all`	Get all feature flags in the project.
`feature-flag-get-definition`	Get the definition of a feature flag.
`update-feature-flag`	Update a feature flag in the project.

Insights & analytics

Tool	Purpose
`insight-create-from-query`	Save a query as an insight.
`insight-delete`	Delete an insight by ID.
`insight-get`	Get a specific insight by ID.
`insight-query`	Execute a query on an existing insight to get its results/data.
`insight-update`	Update an existing insight by ID.
`insights-get-all`	Get all insights in the project with optional filtering.
`query-generate-hogql-from-question`	Queries project's PostHog data based on a provided natural language question.
`query-run`	Run a trend, funnel or HogQL query.

LLM analytics

Tool	Purpose
`get-llm-total-costs-for-project`	Fetches the total LLM daily costs for each model for a project over a given number of days.

Logs

Tool	Purpose
`logs-list-attribute-values`	Get values for a log attribute.
`logs-list-attributes`	List available log attributes.
`logs-query`	Search and query logs in the project.

Organization & project management

Tool	Purpose
`organization-details-get`	Get the details of the active organization.
`organizations-get`	Get the organizations the user has access to.
`projects-get`	Fetches projects that the user has access to in the current organization.
`property-definitions`	Get event and property definitions for the project.
`switch-organization`	Change the active organization from the default organization.
`switch-project`	Change the active project from the default project.

Search

Tool	Purpose
`entity-search`	Search for entities by name or description.

Surveys

Tool	Purpose
`survey-create`	Creates a new survey in the project.
`survey-delete`	Delete a survey by ID.
`survey-get`	Get a specific survey by ID.
`survey-stats`	Get response statistics for a specific survey.
`survey-update`	Update an existing survey by ID.
`surveys-get-all`	Get all surveys in the project with optional filtering.
`surveys-global-stats`	Get aggregated response statistics across all surveys.

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.

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.

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.

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 email support@posthog.com

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.

Next steps

PostHog MCP server: Check out GitHub repository for the MCP server
Model Context Protocol: Learn more about the Model Context Protocol specification
MCP: machine/copy paste: What exactly is MCP again?