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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
482 tools
How to connect
How to connect PostHog to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect PostHog once
-
Open Connections, choose Add connection, and pick PostHog.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in PostHog. PostHog's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
PostHog MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect PostHog to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with PostHog through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Mark a release on the chart
Ask for an annotation on the day a feature shipped, so everyone reading the chart next month knows why the line moved.
-
Growth
Build a cohort without the filter builder
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.
-
Engineering
Set an alert before the pager does
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.
-
Marketing
Check which campaign cohorts grew this week
List the cohorts tied to campaigns, compare them against last week, and get a plain summary of which audiences moved.
-
Customer success
Add an account to a static cohort
After a renewal call, add or remove the people from the static cohort that tracks the accounts you are watching.
-
Data
Tidy up actions nobody owns anymore
Pull every action, find duplicates and stale definitions, and update or delete them with a clear note of what changed.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
PostHog tools for your AI agents
482 tools are ready to call through Elaichi's MCP endpoint the moment you connect PostHog, governed by the same roles, restrictions, and audit log as everything else in Elaichi. PostHog builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting PostHog gets you
6 screens from the product, each doing one job for your PostHog account.
The agent
Ask PostHog questions in plain language.
Cohorts, actions and alerts answered from live PostHog records, no filter builder required.
- actions
- cohorts
- alerts
- annotations
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint for every client.
Claude, ChatGPT and Cursor reach PostHog through one org endpoint, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
482 PostHog tools, no code to write.
Actions, cohorts, alerts and annotations covered, every method listed and ready to call.
- Action create
- Action delete
- Action get
- Action update
ElaichiToolsToolboxes
Every team gets its own PostHog toolbox.
Product, growth and engineering each see only the PostHog tools their work needs.
- Product
- Growth
- Engineering
- Marketing
ElaichiToolboxesShared connections
Share PostHog access without sharing a credential.
One person connects PostHog, teammates work through it, and nobody else sees a key.
- Product
- Growth
- Engineering
- Marketing
ElaichiConnectionsAudit log
Every PostHog change answers who did it.
When, who, what happened, type and resource, logged for every cohort, alert and annotation.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, not a question.
Alerts are fetched, grouped, drafted into a digest, approved by a person, posted to PostHog.
PostHog digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch actions
PostHog
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
PostHog
Queued
Collections and dashboards
PostHog health, computed without a model.
Four metrics, cohorts created over 14 days and a breakdown by team, refreshed on schedule.
PostHog health
Refreshed 4 minutes ago · every 15 minutes · from the actions collection
Actions
1,284 ↓ 12%
Cohorts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Actions created
Last 14 days
By team
Share of activity
Product 34%
Growth 27%
Engineering 21%
Marketing 18%
Related connectors
More from the catalog
FAQ
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 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.
Put PostHog in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.