SpritesWhat Sprites does on PostHog
Every door runs the PostHog specialist, which reads the account itself. You do not brief it on which account, campaign or page you mean.
Post-click, by campaign
Break a funnel or a trend down by the session’s entry UTM source, medium, campaign, term or content, its gclid or fbclid, or its channel type. That is the join an ad platform cannot make on its own.
It reads the project before it guesses
Every event name with its 30-day volume and reach, the property keys, saved insights, flags and cohorts. A misspelled event does not come back as a confident zero.
Figures that add up
Totals are queried separately from the rows and reconciled. When unique users cannot be summed across rows, the answer says so instead of reporting a gap that is not there.
Your internal users stay out
The project’s own internal and test-user filter is applied by default, and the answer always says whether one exists.
Read-only, by design
Sprites queries PostHog and changes nothing in it: no flags flipped, no dashboards rewritten, no experiments started.
The ad account is in the same thread
The Google Ads, Meta, LinkedIn, TikTok and Reddit specialists all read PostHog, so "which campaign brings users who activate" is one question, not two tools and a spreadsheet.
Official PostHog MCP vs open-source servers vs Sprites
Three ways to put PostHog behind Claude, ChatGPT or any other MCP client, and what each one can actually do.
Official PostHog MCP
PostHog hosts its own MCP server at mcp.posthog.com/mcp, free to call. It reaches most of PostHog (insights and SQL, dashboards, experiments, feature flags, surveys and error tracking) and it reads and writes.
Open-source servers
PostHog’s server is open source and lives in PostHog’s own repository, so the open-source route and the official one are the same code. Neither sees what the traffic cost.
Sprites MCP
Sprites reads PostHog trends, funnels, retention and session attribution (UTMs, gclid, fbclid) and sets them beside Google Ads, Meta, LinkedIn, TikTok and Reddit spend. It writes nothing in PostHog; the change the analysis leads to happens in the ad account, as an approval card.
The full comparison is further down: PostHog’s own server.
Connect PostHog to your agent
One endpoint, five clients. Each guide is the exact path through that host's settings, the URL to paste, and the first prompt to run.
Your AI agent
Your ad accounts
The only host that draws the Sprites approval card in the chat, so you edit a budget or a headline in place and approve it without leaving the thread.
Approval card in the threadPostHog MCP for ChatGPTDeveloper mode gives ChatGPT full read-and-write MCP tools rather than the search-and-fetch pair the built-in connectors are limited to, and the Apps SDK renders the Sprites card in the thread.
Approval card in the threadPostHog MCP for CodexMarketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
Results as text · approve in SpritesPostHog MCP for CursorThe campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
Results as text · approve in SpritesPostHog MCP for GrokGrok reads the live timeline, so the same thread that spots a trend can brief the campaign that rides it.
Results as text · approve in SpritesPostHog MCP for GeminiThe account and the analytics are already Google: Gemini reads Google Ads and GA4 alongside Search Console without leaving the family it belongs to.
Results as text · approve in SpritesPostHog MCP for GitHub CopilotMarketing data inside the editor where the tracking code lives, so a conversion event can be checked against what GA4 actually recorded before the pull request is opened.
Results as text · approve in SpritesPostHog MCP for Google AntigravityOne MCP configuration shared by the IDE, the CLI, the SDK and Antigravity 2.0, so the connector is added once and every surface has it.
Results as text · approve in SpritesOfficial PostHog MCP vs Sprites MCP
Yes, there is an official one: PostHog runs its own MCP server at https://mcp.posthog.com/mcp. Here is what each covers.
PostHog hosts its own MCP server, free to call, with a one-line installer (npx @posthog/wizard mcp add) for Claude, Cursor, VS Code, Windsurf, Zed and others. It reaches most of PostHog — insights and SQL, dashboards, experiments, feature flags, surveys and error tracking — and it reads and writes. Query parameters on the URL can narrow it to chosen features or named tools. Tools that use an LLM inside PostHog bill as PostHog AI.
| PostHog officialhttps://mcp.posthog.com/mcp | Sprites MCPapproval-gated | |
|---|---|---|
| Endpoint | mcp.posthog.com/mcp | mcp.sprites.ai/mcp |
| Scope | Most of PostHog: insights, SQL, flags, experiments, surveys, errors | Product analytics: config, trends, breakdowns, funnels, retention |
| Writes | Yes — flags, insights, dashboards, experiments, issues | None in PostHog; ad changes held as approval cards |
| Ad spend | Not in view | Google Ads, Meta, LinkedIn, TikTok and Reddit in the same thread |
| Figures | Returned for the model to read | Computed in code; totals reconciled against rows |
| Cost | Free; LLM-backed tools bill as PostHog AI | Runs on your Sprites plan credits |
If you work inside PostHog — shipping flags, running experiments, triaging errors — PostHog’s own server is the right one, and its URL filters keep it from flooding your client with tools. Use Sprites when the question starts with spend: which campaign, which ad set, which channel brings the users who stay — and when the answer should turn into a change in the ad account rather than in PostHog.
Why a connector like Sprites for PostHog ads
The agent is the interface; the connector decides what it can see and what it is allowed to do. Six things change when that connector is Sprites.
The click and its cost in one answer
PostHog sees what a visitor did; the ad account sees what the visit cost. Sprites reads both, so "cost per activated user by campaign" is one question.
Every channel on one connectorRead-only on PostHog
Nothing Sprites does can flip a flag, end an experiment or edit a dashboard. The only changes it proposes are in the ad account, one approval card at a time.
Numbers that are checked before they are said
Every figure is computed in code from a query you can see, and totals are reconciled against their rows. A figure that does not reconcile is withheld, not rounded into the answer.
Prompts that work verbatim
Paste any of these into a connected client. Naming Sprites matters: without it, an agent will happily answer a PostHog question from public data rather than from your account.
- Ask Sprites which utm_campaign brought the users who finished onboarding last month.
- With Sprites, show the signup-to-activation funnel for Google Ads visitors versus Meta visitors.
- Use Sprites to check what events our PostHog project actually tracks before we build the report.
- Have Sprites compare 4-week retention for users from paid search against organic.
- With Sprites, find the Meta ad sets whose visitors never reach the pricing page.
What it reads, and what it can change
Reads happen on request. Writes never happen unasked: every change to PostHog is proposed, editable, and applied only when you approve it.
What it reads
- Events, their 30-day volume and reach, and property keys
- Saved insights, feature flags, cohorts and actions — listed, not changed
- Trends, breakdowns, funnels and retention computed from your events
- Session attribution: entry UTM parameters, gclid, fbclid, referring domain and channel type
- The project timezone and its internal and test-user filter
What it can change
- Nothing in PostHog. Every PostHog tool is read-only.
- Changes the analysis leads to — a budget, a paused ad set — happen in the ad account, each as an approval card
The doors behind it
- analyze — trends, breakdowns, funnels and retention computed from your PostHog events
- optimize — ad spend judged by what those visitors did afterwards, with the fix as an approval
- research — what the project actually tracks: events, volumes, properties, flags and cohorts
- schedule_task — a weekly funnel or activation read, delivered on its own
PostHog MCP questions
Is there an official PostHog MCP server?
Yes. PostHog runs its own hosted server at https://mcp.posthog.com/mcp, signed in with PostHog OAuth or a personal API key, and installable with npx @posthog/wizard mcp add. It reads and writes across insights, dashboards, SQL, feature flags, experiments, surveys and error tracking. Calling it is free; tools that use an LLM inside PostHog bill as PostHog AI.
What is the difference between that and Sprites?
PostHog’s server is PostHog, all of it, including the ability to change flags and dashboards. Sprites reads PostHog only, and puts it beside your ad accounts: the same specialist that reads Google Ads or Meta reads the funnel, so it can say which campaign brings users who activate — and propose the budget change.
Can Sprites change anything in PostHog?
No. Both PostHog tools are read-only: Sprites queries events and reads configuration, and never creates, edits or deletes a flag, insight, dashboard or experiment.
How does Sprites connect to PostHog?
With a PostHog personal API key and the project you select, on the US or EU cloud. The key is held by Sprites, not by your AI client, so it never sits in a config file on your machine.
Can it break results down by UTM campaign?
Yes. Breakdowns can use the session’s entry UTM source, medium, campaign, term and content, its gclid or fbclid, the referring domain or the channel type — the fields that tie a session to the ad that bought it.
Does it exclude internal and test users?
It applies the project’s own internal and test-user filter by default, and every answer says whether that filter exists. If it does not, you are told rather than shown numbers that include your team.
Which agents can I use it from?
Claude, ChatGPT, Codex, Cursor, Gemini, Grok and any other client that speaks remote MCP. One endpoint, one sign-in, and PostHog is connected once inside Sprites.
The rest of the connector
One URL covers every channel. These are the ones most often used beside this page.
Live performance, search-term waste, campaign builds and budget moves — every write gated.
6 doors · 13 setup guidesMeta AdsCreative fatigue per ad, learning-phase checks, new hooks previewed in the real placement.
6 doors · 13 setup guidesLinkedIn AdsCost per lead by job function, ABM account lists, sponsored content that converts.
4 doors · 13 setup guidesTikTok AdsCPA and CTR for every ad, the next creative batch, and spend moved before the CPA drifts.
5 doors · 13 setup guidesReddit AdsCommunity targeting, subreddit-native copy, and the ad groups spending without converting.
5 doors · 13 setup guidesGoogle Analytics 4Ask GA4 a question and get the answer — including which channel actually caused it.
4 doors · 13 setup guidesSEO and Search ConsoleKeyword research, posts written into your CMS, and page edits that arrive as a diff.
4 doors · 13 setup guidesAI visibility (AEO)Who gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it.
4 doors · 13 setup guidesShopifySEO titles across the whole catalogue, collection pages, and product copy that ships on approval.
5 doors · 13 setup guidesGoogle Business ProfilePerformance per location, the listings missing fields, and posts that keep the map pack.
4 doors · 13 setup guidesWordPressResearched posts, page edits and metadata written into WordPress as drafts you approve.
6 doors · 13 setup guidesWebflowResearched CMS posts, page metadata and copy edits, each an approval before it applies.
6 doors · 13 setup guidesFramerResearched posts and SEO fields written into your Framer CMS, added after you approve.
6 doors · 13 setup guidesZoho CRMPipeline and lead-source reporting beside ad spend, with approved lead, deal and note writes.
4 doors · 13 setup guidesMore on PostHog and MCP
The guides written for this channel first, then the pages that answer what this one assumes: what the protocol is, how it differs from an API, and which servers are worth connecting at all.
- Mixpanel MCPWhat Mixpanel’s own server reaches, and the request limit that shapes how you use it.
- Amplitude MCPSetup, the tools it exposes, and where it stops.
- What is MCPThe protocol in plain English: what a server is, and what the latest revision changed.
- MCP vs APIThey are layers, not rivals. The one property that separates them.
- Best MCP servers for marketersTwelve that do marketing work, sorted by job — remote or local, read or write.
- Best Claude connectors for marketersEvery endpoint called rather than copied from a directory.
Point your agent at PostHog
One URL, one sign-in, and the next PostHog question you ask gets answered from the live account.