# PostHog MCP connector

The PostHog connector brings actions, cohorts, alerts and annotations into Claude, ChatGPT, Cursor and any MCP client, so each person asks questions and makes changes inside their own PostHog access, with every call logged.

Source: https://elaichi.ai/connectors/posthog/

## Facts

| | |
| --- | --- |
| Application | PostHog |
| Category | Analytics |
| AI tools | 482 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. PostHog builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | posthog.com/support |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once PostHog is connected

- Create a cohort of users who signed up last month
- Annotate today with the pricing page release
- Set an alert if the checkout action drops 20 percent

## Connect PostHog in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick PostHog.
2. Optionally set Share with, then press Connect.
3. Approve it in PostHog. PostHog's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which PostHog tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## PostHog MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## PostHog MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## PostHog MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect PostHog to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a PostHog tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with PostHog through Elaichi

### Mark a release on the chart

Product. Ask for an annotation on the day a feature shipped, so everyone reading the chart next month knows why the line moved.

### Build a cohort without the filter builder

Growth. Describe the group you mean in plain words, such as users who signed up last quarter and never invited a teammate, and get a cohort you can reuse.

### Set an alert before the pager does

Engineering. Ask for an alert on a drop in a key action, pick where it should notify, and simulate it once to check it would have fired.

### Check which campaign cohorts grew this week

Marketing. List the cohorts tied to campaigns, compare them against last week, and get a plain summary of which audiences moved.

### Add an account to a static cohort

Customer success. After a renewal call, add or remove the people from the static cohort that tracks the accounts you are watching.

### Tidy up actions nobody owns anymore

Data. Pull every action, find duplicates and stale definitions, and update or delete them with a clear note of what changed.

## Elaichi vs Zapier MCP vs Composio for PostHog

All three can connect PostHog to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over PostHog tools | Allow or restrict single PostHog tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per PostHog call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect PostHog to Claude?

Connect PostHog in Elaichi first. PostHog connects over OAuth, so you sign in to PostHog, approve the access, and you are done, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and PostHog is available in your next conversation.

### Does PostHog work with ChatGPT and Cursor as well as Claude?

Yes. PostHog is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor or any other MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up per client.

### What can an AI agent actually do with my PostHog data?

It can list and create actions, build or edit cohorts, add and remove people from a static cohort, set up alerts and where they notify, simulate an alert, and add annotations to mark releases and campaigns in PostHog. In practice that means asking in plain words for a cohort, an alert or an annotation and getting it made. Short concrete asks, such as annotate today with the pricing change, work better than long sentences.

### Does connecting PostHog give the AI my whole project?

No. Every call runs as the person who signed in to PostHog, so the agent sees only the projects, cohorts and actions that person can already see. Elaichi can narrow that further with restrictions per action, and it never widens access beyond what PostHog itself allows.

### Can my team share one PostHog connection?

Yes. One person connects PostHog in Elaichi and shares it with a team, and nobody else ever handles a key or password. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who made each change in PostHog, not the person who connected it.

### Can I stop an agent from deleting or changing things in PostHog?

Yes. Restrictions in Elaichi work per action, so you can allow reading cohorts and actions while blocking deleting a cohort, an alert or an annotation in PostHog. A restricted action is never shown to the AI client at all, so no prompt, however it is worded, can reach it.

### What happens to a PostHog connection when someone leaves?

Offboarding the person in Elaichi ends their access to PostHog through every client at once. A shared PostHog connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting PostHog once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the PostHog MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. PostHog is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for PostHog?

Yes. Both let Claude, ChatGPT or Cursor use PostHog. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every PostHog call.

### How is Elaichi different from Composio for PostHog?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to PostHog: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 482 PostHog tools

Every tool below is callable through https://api.elaichi.ai/mcp once PostHog is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Action create** (Create). Create action
- **Action delete** (Delete). Delete action
- **Action get** (Get). Get action
- **Action update** (Update). Update action
- **Actions get all** (Get). Get all actions
- **Alert create** (Create). Create alert
- **Alert delete** (Delete). Delete alert
- **Alert destinations create** (Create). Send an alert to Slack
- **Alert destinations delete** (Delete). Stop sending an alert to Slack
- **Alert get** (Get). Get alert
- **Alert simulate** (Action). Simulate detector on insight
- **Alert update** (Update). Update alert
- **Alerts list** (List). List alerts
- **Annotation create** (Create). Create annotation
- **Annotation delete** (Delete). Delete annotation
- **Annotation retrieve** (Action). Retrieve annotation
- **Annotations list** (List). List annotations
- **Annotations partial update** (Update). Update annotation
- **Cohorts add persons to static cohort partial update** (Add). Add persons to static cohort
- **Cohorts create** (Create). Create cohort
- **Cohorts list** (List). List all cohorts
- **Cohorts partial update** (Update). Update cohort
- **Cohorts retrieve** (Action). Get cohort
- **Cohorts rm person from static cohort partial update** (Update). Remove person from static cohort
- **Conversations tickets list** (List). List support tickets
- **Conversations tickets messages retrieve** (Action). Read support ticket messages
- **Conversations tickets notes destroy** (Action). Delete private note
- **Conversations tickets notes partial update** (Update). Update private note
- **Conversations tickets reply create** (Reply). Reply to support ticket
- **Conversations tickets retrieve** (Action). Get support ticket
- **Conversations tickets update** (Update). Update support ticket
- **Conversations views create** (Create). Create saved ticket view
- **Conversations views list** (List). List saved ticket views
- **Conversations views retrieve** (Action). Get saved ticket view
- **Conversations views update** (Update). Update saved ticket view
- **Domains list** (List). List organization authentication domains
- **Identity provider configs create execute** (Create). Create an identity provider configuration (execute)
- **Identity provider configs create prepare** (Create). Create an identity provider configuration (prepare)
- **Identity provider configs destroy execute** (Execute). Delete an identity provider configuration (execute)
- **Identity provider configs destroy prepare** (Action). Delete an identity provider configuration (prepare)
- **Identity provider configs list** (List). List identity provider configurations
- **Identity provider configs partial update execute** (Update). Update an identity provider configuration (execute)
- **Identity provider configs partial update prepare** (Update). Update an identity provider configuration (prepare)
- **Identity provider configs retrieve** (Action). Get an identity provider configuration
- **Identity provider configs SCIM token create execute** (Create). Regenerate an identity provider SCIM token (execute)
- **Identity provider configs SCIM token create prepare** (Create). Regenerate an identity provider SCIM token (prepare)
- **Media image upload complete** (Upload). Complete image upload
- **Media image upload start** (Upload). Start an image upload
- **Media images list** (List). List media library images
- **Products enable** (Enable). Enable PostHog products
- ...and 432 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.