Data & Analytics · Posthog + Claude
PostHog MCP with Claude: Faster Product Analytics and Retention Insights
The short answer
Claude works with PostHog through the Model Context Protocol (MCP), an open standard that acts as a secure adapter between the two. Once connected with an API key, Claude can read product metrics, analyse funnels and retention, and help teams act on what the data shows, with permissions the organisation controls.
What is Posthog?
PostHog is an open-source analytics platform that tracks how people use a website, app or product. It records user interactions and product metrics, so teams can see where users drop off, which features get used, and why customers leave. Product managers, growth teams, data analysts and engineers use it to decide what to build next and where to improve the experience.
How Claude connects to Posthog through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool. The organisation decides what Claude can access, and the connection can be switched off at any time.
Once PostHog is connected, Claude can read product data. For example, it can review a signup funnel, compare retention between two user groups, or summarise how a new feature is being used. Users can ask questions in plain English instead of building queries by hand.
Permissions and approvals keep people in charge. Access is limited to the scope the team sets, typically read-only for analysis. Any action that changes settings or triggers a notification can require a named person to approve it first, and activity is logged for review.
What you can automate
Weekly funnel review for product managers
Each week, Claude can pull the signup-to-activation funnel from PostHog and summarise where users are dropping off. It can compare this week with the previous period and highlight the steps that changed most. Product managers receive a short written briefing instead of spending an hour building charts.
Churn investigation for customer success
When retention falls, Claude can analyse which user groups are leaving and what they had or had not done before leaving. Customer success leads get a plain-language list of likely causes and suggested follow-up accounts. This helps teams focus outreach on the customers most at risk.
Feature adoption reports for leadership
Claude can generate regular reports on how new features are being used, including adoption rates and repeat use over time. Leaders receive a concise summary they can read in minutes. Analysts keep control of the final figures and wording before anything is shared.
Behaviour alerts for growth teams
Claude can watch for unusual changes, such as a sudden drop in sign-ups on a key page or a spike in errors during checkout. When a threshold is crossed, it can prepare an alert for the right person. A named team member reviews the alert before any follow-up action is taken.
Retention reporting for finance and operations
Operations teams often need retention figures for planning and budgeting. Claude can assemble monthly retention summaries from PostHog data and format them to match the existing report template. Finance staff can check the numbers against their own records before the report is released.
An end-to-end workflow: Monthly retention review with CRM follow-up
TriggerThe first working day of each month
Claude pulls the monthly retention and funnel data from PostHog through the connected API key.
Claude compares the results with the previous three months and identifies the user segments with the largest changes.
Claude drafts a short retention summary and a list of accounts showing reduced activity.
The growth lead reviews the summary and approves which accounts should be passed on.
Approved accounts are added as follow-up tasks in the company CRM, such as Salesforce or HubSpot, for the customer success team.
The summary is filed in Microsoft 365 for leadership review.
OutcomeLeadership receives a consistent monthly retention review, and customer success teams start follow-up work on at-risk accounts sooner. Typical teams report less time spent compiling reports, though results vary by business.
How we set it up
Free automation audit
We review your current PostHog use and identify the reports, funnels and alerts that take the most time. We agree which workflows are worth automating first.
Secure connection with an API key
We connect Claude to PostHog using an API key, with the narrowest access that supports your workflows. Keys are stored securely and can be rotated or revoked at any time.
Workflow design
We design the end-to-end workflow across PostHog and your other systems, such as Microsoft 365, your CRM or your ticketing tool. We define which actions need human approval.
Testing against real cases
We test the workflow using past data and real questions from your team. We check outputs for accuracy and adjust prompts and permissions until the results are reliable.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on asking questions, reviewing outputs and approving actions.
Who benefits
- Product managers
- Get fast answers about funnels and feature use without waiting for analyst time.
- Growth and marketing leads
- Spot changes in sign-ups and conversion early, with alerts that reach the right person.
- Customer success teams
- Identify at-risk accounts sooner and focus outreach where it matters most.
- Data and IT leaders
- Keep control of access, approvals and logs while giving teams easier access to insight.
Security and control
- Least-privilege API keys, scoped to the data each workflow actually needs.
- Human approval required for any action that changes settings or notifies customers.
- Audit logs of every question asked and every action taken through the connection.
- Regular key rotation and immediate revocation if a team member or system changes.
- Testing against past data before launch to check that outputs are accurate.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the workflow in regions that suit their data protection requirements. Indian organisations are supported with設計 aligned to the Digital Personal Data Protection Act, 2023. Businesses in the UAE and Saudi Arabia receive setups that respect local data protection laws. The hosting region for Claude is chosen during design to meet each client's requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the PostHog MCP server do?
The PostHog MCP server acts as a secure bridge between PostHog and AI tools such as Claude. It allows Claude to request analytics data, such as funnels, retention and user behaviour, using natural language. The server only exposes the data and actions that the connection is set up to allow.
Is connecting PostHog to Claude secure?
Security depends on how the connection is set up. We use API keys with the narrowest access needed, store them securely, and rotate them regularly. Actions that change settings or notify people require human approval, and all activity is logged for review.
What can Claude do with PostHog once connected?
Typically Claude can answer questions about funnels, retention, feature use and user behaviour, and produce written summaries and reports. With approval, it can also prepare alerts or follow-up tasks. Its access is limited to the scope your team sets during design.
How long does setup take?
A focused setup for a small number of workflows often takes a few weeks. This includes the audit, secure connection, testing against real cases and team training. Larger, multi-system workflows take longer, and we confirm timelines after the free audit.
Which plan or permissions do I need?
You need a PostHog account with an API key that has permission to read the data your workflows use. Requirements depend on your PostHog setup and the actions you want to automate, so we confirm exactly what is needed during the free audit.