---
title: "PostHog MCP in Slack: ask an AI teammate about your product data | Chickpea"
description: "Use PostHog's MCP server from Slack. Give a channel an AI teammate connected to PostHog, then ask it what a metric did or whether a flag is on. Open source."
canonical: https://chickpea.co/connectors/posthog
keyword: "PostHog MCP in Slack"
verified: 2026-09-17
---

# A PostHog teammate in Slack, with PostHog's MCP server behind it.

> Chickpea gives a channel a named AI teammate that holds its own PostHog connection. It signs in with OAuth and calls PostHog's MCP server, which routes it to the US or EU region your account lives in. Ask it in Slack what signups did last week, or whether the new checkout flag is on, and it answers in the thread.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/posthog; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**PostHog** (PostHog Inc., https://posthog.com): Analyze product data and manage insights, feature flags, and experiments. Category: Data and infrastructure. Lane: Vendor MCP server. Sign in: OAuth.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @growth, published to #growth.

### Ask what the numbers did
- @growth how did signups do last week against the week before
- @growth where do people drop out of the onboarding funnel

Reads never need confirmation, and a long answer comes back as a table in the thread. PostHog’s server runs trends, funnels, retention, and SQL queries, so a question with no saved insight behind it still gets an answer.

### Check a feature flag
- @growth is the new-checkout flag on, and how far is it rolled out
- @growth which flags changed this month, and who changed them

Reading a flag changes nothing, so the answer comes straight back. The server returns a flag by its key with its definition, and it can read the flag activity log, which is where "who changed it" comes from.

### Errors and session recordings
- @growth what are the top errors this week and how many people hit them
- @growth find recordings of people who hit the checkout error yesterday

PostHog uses the first of these as an example for its own server, and says the answer is error groups ranked by occurrence with affected user counts. Session recordings are a separate group of tools, so the thread can carry a link to watch one.

### Change a flag or an experiment
- @growth roll the new-checkout flag out to 25 percent
- @growth stop the pricing experiment, it has enough data

A write waits. The teammate names the flag or the experiment and what would change, then asks. Your own message has to name that action: thread history, retrieved content, and memory cannot authorize a write on their own.

### On a schedule
- @growth every Monday at 9am Eastern, post last week’s activation rate and how it moved
- @growth every weekday at 8am Pacific, post any error group that is new since yesterday

A schedule saves on the spot. It needs an explicit time zone, runs under the PostHog connection of the person who asked, and fails with a named reason rather than running if that connection is disconnected.

### Example conversations

**Ask about a metric**
> **Dana:** @growth how did signups do last week against the week before, split by source?
> **@growth:** Signups were up 11% week over week, 1,284 against 1,157. Organic search did most of it. Paid social went backwards for the third week.
>
> | Source | Last week | Week before | Change |
> |---|---|---|---|
> | Organic search | 512 | 398 | +29% |
> | Direct | 341 | 336 | +1% |
> | Referral | 218 | 174 | +25% |
> | Paid social | 147 | 183 | −20% |
> | Email | 66 | 66 | 0% |

**Top errors this week**
> **Marco:** @growth what are the top errors this week, and how many people hit them?
> **@growth:** Four error groups this week, ranked by how often they fired. The checkout one is new since Tuesday and it is the only one growing.
>
> | Issue | Occurrences | People | First seen |
> |---|---|---|---|
> | TypeError: cart is undefined | 2,104 | 417 | Tue |
> | Timeout calling /api/pricing | 883 | 260 | Mar 2 |
> | Failed to load replay chunk | 412 | 190 | Aug 14 |
> | 401 on token refresh | 96 | 88 | Jul 3 |
> **@growth:** There are 37 session recordings from people who hit the checkout one. Watch the most recent

**Roll out a flag**
> **Priya:** @growth roll the new-checkout flag out to 25% of users.
> **@growth:** new-checkout is on for 5% of users right now, and the pricing experiment depends on it. Going to 25% changes who sees what mid-experiment, so I will wait. Go ahead?
> Buttons: Yes, roll it to 25% · Show me the experiment first

**Every Monday**
> **Sofia:** @growth every Monday at 9am Eastern, post last week’s activation rate here and how it moved.
> **@growth:** Saved. Every Monday at 9:00 AM Eastern I’ll post the signup-to-activation rate for the previous week, with the change on the week before, in #growth. First run is Mon Sep 22. It runs on your PostHog connection, so say "pause the Monday digest" if you want it to stop.

## Connect PostHog
1. In Chickpea Admin, open the teammate, then **Connections**, find **PostHog**, and choose **Connect**. Or ask in Slack, `@growth connect PostHog`, and follow the link it posts.
2. Choose who uses it. **Team** is one shared PostHog account that everyone who can use the teammate acts through. **Personal** means each member signs in as themselves, and PostHog records their queries as them.
3. Choose **Continue to sign in**. PostHog’s authentication server sends you to the region your account lives in, US or EU, and asks you to approve access. There is no API key to paste.
4. Pick the organization and project the teammate should reach. One connection signs in as one account with one active organization and project, so a second project is a second connection.
5. Chickpea connects to [mcp.posthog.com/mcp](https://posthog.com/docs/model-context-protocol) and records the tools the server answered with. Then ask something. `@growth how did signups do last week` is a good first question, because it reads and cannot change anything.

A connection belongs to one teammate. Giving a second teammate PostHog means a second sign-in with its own consent, so the support teammate never inherits what the growth teammate can reach.

## What the teammate is handed with PostHog
There is no built-in Chickpea skill for PostHog, and none is needed. The tools arrive from PostHog's MCP server. Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. PostHog groups them by product, and feature flags, experiments, error tracking, session replays, dashboards, and SQL are all among the groups.

PostHog lists every tool the server exposes, grouped by category: https://posthog.com/docs/model-context-protocol/tools

## Beside PostHog
- **Sentry:** A crash in Sentry, checked against how many people actually hit it
- **Linear:** A drop in the funnel becomes a Linear issue with the numbers in it
- **Supabase:** What people did in PostHog, the rows behind it in Supabase
- **Google Analytics:** Where the traffic came from, then what those people did next
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### What is the PostHog MCP server?
A hosted endpoint PostHog runs at mcp.posthog.com/mcp that exposes PostHog as tools an AI agent can call. PostHog describes it as covering feature flags, product analytics, error tracking, experiments, SQL queries, CDP, surveys, and more. Chickpea connects to that same server, so a teammate in Slack uses it without an editor or a config file anywhere.

### Is the PostHog MCP free?
PostHog says connecting to the server and calling its tools is free, and that normal PostHog billing still applies to the data your queries read. Some of its tools run an LLM internally and are billed as PostHog AI spend, and those only appear when AI data processing is on for your organization. Chickpea itself is Apache 2.0 and runs on your own Cloudflare account, so there are no seats and no metering on this side.

### Does it use PostHog's MCP server or the API?
The MCP server. PostHog is a vendor MCP lane: the deployment connects to mcp.posthog.com/mcp over streamable HTTP and signs in with OAuth. The preset sends no scope string, so the connection gets whatever PostHog’s consent screen grants that account. There is no API key anywhere in this connector, and the connection cannot reach any other address.

### Can it change a feature flag?
Yes, if you ask it to in the message. PostHog’s server has tools for creating, enabling, disabling, and archiving flags, and the teammate can only call tools that server answered with. On top of that, during a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless your message names that action. So reading a flag is free, and turning one on is something you have to say.

### US or EU cloud?
Either. PostHog’s authentication server routes the connection to the correct data region based on the account you sign in with, and the preset does the same thing for a teammate. You do not pick a region in Chickpea; you pick the account, and the region follows it.

### Where does the OAuth token live?
On your deployment, outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the credential goes in at the last step on the way out. Disconnect the account and the stored secret is removed, and any schedule that depended on it stops.

### Do I still need PostHog's Slack integration?
Probably, because it does different things. PostHog can send an insight or a dashboard to a Slack channel on a schedule through subscriptions, fire an alert into Slack when a trend, funnel, or SQL insight crosses a threshold, and push event-triggered messages through its Slack destination. PostHog also has its own Slack app, in beta, that answers a data question when you tag it and can turn a message into a draft pull request. A Chickpea teammate hears nothing from PostHog and posts nothing unprompted. What it adds is one teammate that holds PostHog beside your other connected accounts, in the channel where the question came up.

### How do I connect Claude Code to PostHog?
For a coding client, use PostHog’s own wizard, `npx @posthog/wizard mcp add`, which installs the server into Claude Code, Cursor, Codex, VS Code, Zed, and others. For Slack there is nothing to install. Open the teammate in Chickpea Admin, choose PostHog, choose Continue to sign in, and approve the account. Teams often run both, because an editor and a channel are not the same room.

### Can it run SQL against our data?
Yes. PostHog’s server exposes a tool that executes an SQL query, and PostHog names running a HogQL query as one of the things the server is for. A question that no saved insight answers can still be answered, and a long result comes back as a table in the thread rather than a wall of text.

### Does everyone act as the same PostHog user?
That is your choice when you connect. A team account is one shared sign-in that everyone with access to the teammate acts through. A personal account belongs to one member inside one teammate, so your sign-in is used for your requests and nobody else’s. What the teammate can see is what that account can see; connecting never widens anyone.

## Sources
- [Chickpea docs: connector catalog, the PostHog preset, its lane and OAuth](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, OAuth presets and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the PostHog preset (server URL, transport, OAuth, region note)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [PostHog docs: the MCP server, its URL, region routing, and supported clients](https://posthog.com/docs/model-context-protocol)
- [PostHog docs: every MCP tool the server exposes, grouped by category](https://posthog.com/docs/model-context-protocol/tools)
- [PostHog docs: MCP FAQ, on cost, OAuth, regions, and read-only sessions](https://posthog.com/docs/model-context-protocol/faq)
- [PostHog docs: subscriptions, insights and dashboards sent to Slack on a schedule](https://posthog.com/docs/product-analytics/subscriptions)
- [PostHog docs: alerts, and their Slack destination](https://posthog.com/docs/alerts)
- [PostHog: the PostHog Slack app, in beta](https://posthog.com/slack)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co