Skip to content

PostHog MCP connector

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

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Create a cohort of users who signed up last month

Working in PostHog with Elaichi

  • Action get
  • Actions get all
  • Alert get
Ask anything…
Governance / Audit log Last 24 hours
PostHog Alert get Emily Carter · ChatGPT · 9:41 AM Done
PostHog Actions get all Emily Carter · ChatGPT · 9:41 AM Done
PostHog Action get Emily Carter · ChatGPT · 9:41 AM Done
PostHog Action create Megan Brooks · Claude · 9:38 AM Done
PostHog Action update Ryan Hayes · Cursor · 9:35 AM Done

How to connect PostHog to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

PostHog MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

PostHog MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

PostHog MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

PostHog MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect PostHog to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with PostHog through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in PostHog is logged.

  • 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”

See all 482 PostHog tools →

What connecting PostHog gets you

6 screens from Elaichi, each doing one job for your PostHog account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask PostHog questions in plain language.

Cohorts, actions and alerts answered from live PostHog records, no filter builder required.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One governed endpoint for every client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach PostHog through one org endpoint, no SDK and no shared key.

ElaichiTools
Tool Action Description
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

Tool catalog

482 PostHog tools, no code to write.

Actions, cohorts, alerts and annotations covered, every method listed and ready to call.

ElaichiToolboxes
Name Source template Tools Created

Product toolbox

PostHog · actions and release annotations

PostHog starter 18 Mar 4, 2026

Growth toolbox

PostHog · cohorts and audiences

— 9 Mar 2, 2026

Engineering toolbox

PostHog · alerts and notifications

— 24 Feb 27, 2026

Marketing toolbox

PostHog · campaign cohorts

PostHog starter 6 Feb 19, 2026

Data toolbox

PostHog · action definitions and cleanup

— 31 Jan 30, 2026

Customer success toolbox

PostHog · static cohorts of key accounts

— 12 Jan 22, 2026

Toolboxes

Every team gets its own PostHog toolbox.

Product, growth and engineering each see only the PostHog tools their work needs.

ElaichiConnections
Connection Scope Status Access
PO

PostHog (Product)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PO

PostHog (Growth)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PO

PostHog (Engineering)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PO

PostHog (Marketing)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PO

PostHog (Data)

Connected by Ryan Hayes

Personal • Active Not shared
PO

PostHog (Customer success)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share PostHog access without sharing a credential.

One person connects PostHog, teammates work through it, and nobody else sees a key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

PostHog Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

PostHog Actions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

PostHog Actions List Toolbox

Audit log

Every PostHog change answers who did it.

When, who, what happened, type and resource, logged for every cohort, alert and annotation.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

PostHog digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch actions

    PostHog

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    PostHog

    Queued

Workflows

A schedule starts the work, not a question.

Alerts are fetched, grouped, drafted into a digest, approved by a person, posted to PostHog.

PostHog health

Refreshed 4 minutes ago · every 15 minutes · from the actions collection

Live

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%

Collections and dashboards

PostHog health, computed without a model.

Four metrics, cohorts created over 14 days and a breakdown by team, refreshed on schedule.

Why connect PostHog's MCP server through Elaichi

PostHog builds and runs this MCP server. Elaichi sits in front of it, so PostHog's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to PostHog's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach PostHog's tools at the same Elaichi address as every other connected app. Nobody adds PostHog's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own PostHog sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches PostHog's server. By default, a tool PostHog does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to PostHog

    PostHog builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the PostHog team.

    posthog.com/support

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for PostHog, by what to check
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 Free for one person; $15 per user per month on Gold. 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.

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.

Questions, answered

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, Microsoft Copilot 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 restricting deleting a cohort, an alert or an annotation in PostHog. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot