How to connect Antigravity to PostHog

Save a PostHog key in Ryze AI once, add one MCP URL to Google Antigravity, then ask the agent for pageview counts, funnel steps or the list of feature flags in your project.

Your MCP URL
https://connector.get-ryze.ai/mcp

Copies the link. Paste it as the serverUrl of the ryze entry in Antigravity mcp_config.json. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Connector tested November 15, 2026

Quick answer

The main way to connect Antigravity to PostHog is the Ryze AI connector. Save a PostHog personal API key and host in Ryze AI, pick the project, then add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json and finish the Ryze AI sign-in. The agent then has 3 PostHog tools: one that reads and runs HogQL queries, one that writes and one that deletes. What they can change depends on the scopes on your key.

  1. In PostHog create a personal API key with read access and the Query and Insight scopes
  2. In Ryze AI open Integrations, click Connect on the PostHog card, paste the key and host, then pick the project
  3. In Antigravity open MCP Servers, Manage MCP Servers, View raw config and add the ryze entry
  4. Complete the Ryze AI sign-in, start a new agent chat and ask for last week's pageviews by day

Antigravity to PostHog at a glance

FactDetail
Main way to connectThe Ryze AI connector: a hosted MCP server that Antigravity reaches through one serverUrl entry. The PostHog key stays in Ryze AI and nothing runs on your machine
Server addresshttps://connector.get-ryze.ai/mcp
Where the entry goesmcp_config.json, either ~/.gemini/config/mcp_config.json for all projects or .agents/mcp_config.json in one workspace. The IDE, the App and the CLI share the format
Sign-inTwo separate steps. PostHog is joined with a personal API key and a host inside Ryze AI. Antigravity then signs in to the connector with OAuth 2.0 and PKCE, which needs no client ID because the connector offers dynamic client registration
PostHog tools3 in all: posthog__read, posthog__write and posthog__delete
Which projectOne PostHog project per connection, picked in Ryze AI after the key is saved. Works with US Cloud, EU Cloud or a self-hosted address
Can it change thingsOnly as far as the key allows. It can create or update insights, dashboards, feature flags and cohorts and delete them when asked. A key with read scopes only makes PostHog reject every change. Antigravity also holds MCP tools without a rule in Ask mode
Other data in the same chatTools for the other platforms you connect in the same Ryze AI workspace appear under the same address. This guide covers PostHog only
Antigravity plan neededNone is named. Google's MCP page lists no plan
Ryze AI priceConnecting costs nothing, and the tools need an active plan or trial: Paid Ads is $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial, Agency $279 per month
PostHog's own optionA hosted MCP server at https://mcp.posthog.com/mcp with OAuth sign-in. PostHog's setup pages name other clients than Antigravity, and the pairing was not tested here
Last testedNo call to PostHog was run for this guide. The connector's sign-in data was compared with Antigravity's OAuth order on November 15, 2026. Nothing was run inside Antigravity

Before you start

  • Google Antigravity. Google's MCP page for Antigravity names no plan. It covers three surfaces, the standalone IDE, the desktop App and the CLI, and all three read one mcp_config.json format. Enterprise accounts cannot use the standalone IDE and may need an admin to allow MCP servers in Gemini Enterprise first.
  • A PostHog account and a personal API key. The key starts with phx_ and acts as the user who made it. Give it read access to the project you want, including the Query and Insight scopes, and add write scopes only for objects the agent should change. You also need the host: https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud, or your own address when self-hosted.
  • A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Connecting is free; the PostHog tools need an active plan or trial. Annual billing takes 30% off the first year.

How to connect Antigravity to PostHog

These steps are for the Antigravity IDE. Two happen in PostHog and Ryze AI, four in the editor. The App and the CLI use the same config entry and are covered below.

  1. Create a personal API key in PostHog

    In PostHog go to Settings, then Personal API keys, and click Create key. Grant read access to the project you want with the Query and Insight scopes. Add write scopes only for objects the agent should change. Copy the phx_ key, because PostHog shows it once.

  2. Connect PostHog in Ryze AI

    In the Ryze AI app open Integrations, click Connect on the PostHog card, paste the key, enter the host (US Cloud, EU Cloud or your self-hosted address) and click Continue. Pick the project and click Save.

  3. Open the raw MCP config in the Antigravity IDE

    In the agent side panel of the editor, click the ... menu at the top and choose MCP Servers. Click Manage MCP Servers, then View raw config. This opens mcp_config.json: ~/.gemini/config/mcp_config.json applies everywhere and .agents/mcp_config.json applies to one workspace.

  4. Add the ryze entry

    Under mcpServers add an entry named ryze with the serverUrl https://connector.get-ryze.ai/mcp and save. No client ID or secret goes in the file. Antigravity registers itself with servers that offer dynamic client registration, which the Ryze AI connector does.

  5. Sign in to Ryze AI

    Antigravity starts the browser sign-in for the server, and Google's MCP page does not describe how it begins in the IDE. On the Ryze AI page choose the workspace that holds your PostHog connection and click Allow connection. If the connector was added before PostHog was connected, remove the entry, add it again and open a new chat.

  6. Ask your first question

    Open a new agent chat and ask: Count pageviews per day for the last 7 days with a HogQL query. Antigravity asks for approval before an MCP tool runs until you allow it, so approve the first call.

The Ryze AI help article for PostHog covers the PostHog key, the host and the project picker. There is no Ryze AI help page for Antigravity, and Ryze AI was not tested in it for this page.

Sources: Google's Antigravity MCP documentation, checked November 15, 2026, and the Ryze AI PostHog guide.

Antigravity App

The Antigravity App lists its MCP servers on the Customizations page and has its own Authenticate button, so the sign-in works differently from the IDE. One layout setting matters: in the Knowledge Work layout, the Installed tab shows plugins only and hides the MCP Servers section. Switch to Software Engineering under Settings > General > Interface Layout first. Business and enterprise accounts always get Software Engineering.

  1. Click Customizations in the sidebar, then Installed, and scroll down to MCP Servers.
  2. Click Copy Config File Path and add the ryze entry shown below to that mcp_config.json.
  3. Go back to Customizations, Installed, MCP Servers and click Authenticate next to ryze.
  4. Sign in to Ryze AI in the browser, copy the authorization code, paste it into Enter authorization code and click Submit. The server then reconnects by itself.

The entry to add is the same in the IDE, the App and the CLI:

{ "mcpServers": { "ryze": { "serverUrl": "https://connector.get-ryze.ai/mcp" } } }

The App's Add MCP Server (+) button opens a searchable catalog and has no address field, so a custom server goes into mcp_config.json by hand. Remote servers must use Streamable HTTP: Google's docs reject the older HTTP+SSE transport and the httpUrl key, and accept url as an alias of serverUrl. The OAuth redirect URI Antigravity uses is https://antigravity.google/oauth-callback.

Antigravity CLI

The Antigravity CLI (agy) reads the same two files. Put the ryze entry in ~/.gemini/config/mcp_config.json or in <workspace>/.agents/mcp_config.json, then type /mcp in the prompt panel. That opens the MCP Manager, with a status line per server and a reload for the configuration. Name a workspace entry differently from a global one, because when two files share a name the server that is already running wins. The CLI took over from Gemini CLI for personal accounts.

Google documents the Authenticate steps for the App only. The CLI changelog mentions a sign-in link for OAuth servers (version 1.5.2, November 6, 2026), but no Google page lists CLI sign-in steps, so none are given here. The changelog also names mcp add, remove, list, enable and disable subcommands without their syntax, so none is shown. Antigravity keeps OAuth tokens in ~/.gemini/antigravity/mcp_oauth_tokens.json and refreshes them on its own.

Sources: Google's Antigravity MCP documentation, the Gemini CLI to Antigravity CLI update, the Gemini CLI migration page, the Antigravity changelog and the connector checks on this page. Checked November 15, 2026.

Antigravity and MCP: the facts in one table

TopicWhat Google's Antigravity pages say
Where MCP worksThe MCP page covers the Antigravity App, the CLI and the standalone IDE. The Visual Studio extension page describes the same two mcp_config.json files
Config formatAn mcpServers map keyed by server name, the same on every surface. An enabled plugin can ship servers in its own <plugin-root>/mcp_config.json
Local or remotecommand starts a local stdio process. serverUrl (or url) points at a remote Streamable HTTP server
Extra headersA headers object on a remote entry sends custom HTTP headers such as an Authorization bearer token
OAuth orderoauth.clientId from the file first, then a Client ID Metadata Document, then dynamic client registration. The Ryze AI connector lists a registration endpoint and no metadata document, so the third route applies
ApprovalsAn MCP tool with no rule waits in Ask mode. Rules look like mcp(server/tool), mcp(server/*) or mcp(*), and Deny beats Ask beats Allow
Skipping the promptTurbo in the App on a personal account runs MCP tools without asking. In the CLI, request-review is the default and always-proceed skips the prompt unless an ask or deny rule matches
Trimming a serverenabledTools keeps only the listed tools, disabledTools hides listed ones, and disabled: true pauses a server but keeps its entry
Tool loadingTools load lazily by default and their schemas are cached on disk
TimeoutsUp to 5 minutes for a server to connect and list tools and up to 3 minutes per tool call, both changed by timeoutSeconds
Plan and enterpriseNo plan is named for MCP. The standalone IDE is unsupported for enterprise deployments, and admins can set MCP allowlists
Bringing servers overOn first launch with the Software Engineering role, the App offers to import MCP servers from Claude Code, Codex, Cursor and Gemini CLI

Sources: MCP, permissions, settings, plans, enterprise, getting started, Visual Studio extension and changelog pages of Google Antigravity. Checked November 15, 2026.

Other AI clients

The same URL works in other MCP clients. PostHog is connected once in Ryze AI with one key, so nothing changes on the PostHog side.

Gemini

Google's other assistant takes the same URL with different steps. See How to connect Gemini to PostHog. For the Antigravity client in general, see Ryze AI in Antigravity.

Claude Code, Codex and Cursor

Each coding client has its own guide: Claude Code, Codex and Cursor.

Claude and ChatGPT

Both add the URL as a custom connector. See How to connect Claude to PostHog and How to connect ChatGPT to PostHog.

PostHog access and permissions

Access comes from the PostHog key you save in Ryze AI. Antigravity only signs in to the connector, so the key decides what the agent can read and change. Four points cover it.

A personal API key
The connection uses a PostHog personal API key (phx_ prefix) plus a host. PostHog says private endpoints give the same access as being logged in, within the scopes and projects set on the key. There is no OAuth sign-in to PostHog in this connection.
Which project
One project per connection, picked after the key is saved. Another project needs another Ryze AI workspace, or a disconnect and reconnect on the PostHog card.
Read or write
Read scopes keep the agent read-only, because PostHog rejects any change. Add write scopes, such as insight:write, dashboard:write, feature_flag:write or cohort:write, only for objects the agent should change.
Who the key acts as
The key carries the access of the PostHog user who created it. Organization admins and owners can see every member's keys that reach the organization, with scopes and last use.

The PostHog scopes on the key

Antigravity signs in to the connector, and the connector's discovery data names two scopes for that sign-in, mcp:read and mcp:write. The scopes below belong to the PostHog key. Ryze AI names the Query and Insight scopes plus read access to the wanted project. The rest are PostHog's other scopes, with PostHog's own description of each.

PostHog scopeHow PostHog describes itIn the Ryze AI connection
query:read"Running SQL and insight queries on your project's data, plus event, session, and web vitals lookups." Read level onlyNamed by Ryze AI as needed
insight:read, insight:write"Insights, including their queries, results, and explanations, plus anomaly rates for trends insights."Read named by Ryze AI. Write only if the agent should change insights
dashboard:read, dashboard:write"Dashboards, including their tiles, text cards, widgets, and layout, and running the insights on them."Not named by Ryze AI. Needed in practice if you ask for dashboards, and write only for changes
feature_flag:read, feature_flag:write"Feature flags, including their release conditions, variants, payloads, and rollout history."Not named by Ryze AI. Write only for flag changes
cohort:read, cohort:write"Cohorts, including their filters, static member lists, calculation history, and where they are used."Not named by Ryze AI. Write needed to create or delete cohorts
person:read, person:write"Persons and their properties, including updating, splitting, and deleting persons and their data."Not named by Ryze AI. Leave write off
event_definition:read"Event definitions, schemas, and property groups, including tags, verification, and generated type definitions."Not named by Ryze AI

PostHog's scopes page says each scope has a read level and a write level, that write "lets it view, create, change, and delete the data", and that a request lacking a needed scope fails with a 403 that names the missing scope. Ryze AI's help center asks only for the Query and Insight scopes, so whether a dashboard, flag, cohort or person listing needs its own scope on the key is not stated there. If a call returns a 403, add the scope it names.

What the default connection does not include: any write scope, a second project in the same workspace, and the MCP Server key preset, which PostHog made for its own MCP server and CLI. Ryze AI's facts do not cover session recordings, experiments, surveys or error tracking, so ask for insights, dashboards, flags, cohorts, persons, event definitions, projects and HogQL queries.

Sources: PostHog API scopes, personal API keys and API overview, checked November 14, 2026. Ryze AI's connection details from the Ryze AI PostHog guide.

Limits that shape the answers

These limits shape what comes back. The first four come from Ryze AI's connection facts, and the last three from Google's Antigravity MCP page.

AreaLimit
One projectA connection holds one PostHog project. To switch, click View on the PostHog card, disconnect with the trash icon and connect again.
HogQL boundsQueries need a time window and a row limit of 1,000 at most, because PostHog stops unbounded HogQL queries.
ScopesWhat the agent can change is limited by the scopes on the personal API key.
Active planWithout an active Ryze AI plan or trial the connector can only list workspaces and connect platforms.
TimeoutsAntigravity waits up to 5 minutes for a server to connect and list its tools and up to 3 minutes for each tool call.
Tool loadingMCP tools load lazily and their schemas are cached on disk, so the agent reads them when needed.
Tool approvalAn MCP tool without a configured rule runs in Ask mode, and each call needs your approval until a policy allows it.

Sources: the Ryze AI PostHog guide, the Ryze AI connection facts and Google's Antigravity MCP documentation, checked November 15, 2026.

Removing access

To remove access, disconnect PostHog on its card in Ryze AI, or delete the personal API key in PostHog under Settings, Personal API keys. In Antigravity delete the ryze entry from mcp_config.json, or set disabled: true to pause it and keep the entry. In the App, More actions (⋮) next to the server offers Disable and Delete. Stored OAuth tokens are in ~/.gemini/antigravity/mcp_oauth_tokens.json.

What Antigravity can do in PostHog

The Ryze AI connector exposes 3 PostHog tools. The names come from the Ryze AI app source, and the tool list was not seen on a live connection, so treat the table as the documented design.

ToolTypeWhat it does
posthog__readReadReads PostHog data for the connected project (projects, insights, dashboards, feature flags, cohorts, persons, event definitions) and runs HogQL analytics queries.
posthog__writeWriteCreates or updates PostHog objects such as insights, dashboards, feature flags and cohorts.
posthog__deleteDeleteDeletes a PostHog object by path, for example a cohort. The deletion is irreversible.

In Antigravity an MCP tool with no rule waits in Ask mode, so each call needs a click. Google's rule forms are mcp(server/tool) and mcp(server/*). Allow posthog__read if you want reads to run freely and keep posthog__write and posthog__delete in Ask mode. In the Ryze AI chat the Tool approvals picker starts on Skip all approvals, and Approve write & delete or Manual approve can be chosen there. Scheduled tasks run without an approval step. A key with read scopes only keeps the agent read-only whatever the approval mode.

PostHog limits in numbers

PostHog meters its API by personal API key and by project. Ryze AI's facts do not say how its connection maps onto these quotas, so the figures are PostHog's published limits and this guide does not claim they all apply to the connector. They apply directly if you use PostHog's own server or call the API yourself.

LimitFigure or ruleWho sets it
PostHog's own MCP server480 requests per minute and 4,800 per hour per credential. Opening a session and listing tools count. Over the limit the answer is 429 with a Retry-After headerPostHog
Analytics endpoints240 per minute and 1,200 per hour per personal API key, for calculating insights, retrieving persons and session recordingsPostHog
Query endpointAt project level 2,400 requests per hour, 240 per minute, 3 queries running at once and 10 seconds of maximum execution time. A queued query may wait up to 30 seconds. Some older accounts are on 120 queries per hourPostHog
Hourly read budgetQueries made with a personal API key draw from an hourly read budget per project, counted in bytes read. When it runs out the answer is 429 with code api_queries_budget_exceeded. Cached results still work. PostHog publishes no byte figurePostHog
Other create, read, update and delete calls480 per minute and 4,800 per hour per personal API keyPostHog
Query rows100 rows by default and up to 50k with your own LIMIT. OFFSET returns HTTP 400 for personal API keys, so page with a timestamp filterPostHog
Personal API keysUp to 10 per user, and the key value is shown once at creationPostHog
Query cacheAPI queries are cached by default, and a response reports is_cached and last_refreshPostHog
Dynamic cohortsRecalculated once every 24 hoursPostHog
Rows per HogQL queryA time window and at most 1,000 rows through the Ryze AI connectionRyze AI
Tool wait in AntigravityUp to 3 minutes per tool call and 5 minutes to connect, adjustable with timeoutSecondsAntigravity

Sources: PostHog's API overview, query limits, MCP FAQ, personal API keys and cohorts, checked November 14, 2026. The Ryze AI row from its connection facts. The Antigravity figure from the Antigravity MCP documentation, checked November 15, 2026.

First 3 prompts to run

1. Count pageviews by day

Count pageviews per day for the last 7 days with a HogQL query, limited to 1,000 rows.

Tools used: posthog__read

What comes back: A table of days and counts from your own project. The query carries a time window and a row limit, as the connection requires.

2. Break down sessions by UTM source

Break down last month's sessions by UTM source with a HogQL query over sessions, so I can see which campaigns sent traffic.

Tools used: posthog__read

What comes back: Session counts grouped by the UTM source values your site recorded. Sources that were never recorded cannot appear.

3. Read a saved funnel

Read my saved signup funnel insight and tell me how many people reach each step.

Tools used: posthog__read

What comes back: The step counts of that insight as PostHog calculates them. It needs the Insight and Query scopes on the key.

Each answer comes from your own project, so this page describes what comes back instead of showing sample numbers. No PostHog call was run for this guide.

10 jobs to hand to Antigravity

Ten jobs to hand to the Antigravity agent, each with the Ryze AI tool that does the work. The last column follows the pack's reading of the default connection: read access with the Query and Insight scopes and no write scope. Every job needs an active Ryze AI plan or trial, and none was run against a project.

JobAsk the agentToolWorks on the default connection
Daily pageviewsCount pageviews per day for the last 7 days.posthog__readYes, as a HogQL query with a time window and a row limit
Traffic by campaignBreak down last month's sessions by UTM source.posthog__readYes, as a HogQL query over sessions
Funnel step countsRead my saved signup funnel and report each step.posthog__readYes, with the Insight and Query scopes
Dashboard listList the dashboards in the project by name.posthog__readConditional: needs read access to dashboards on the key, and PostHog answers 403 with the missing scope if it is absent
Flag review before a launchList the feature flags with their rollout settings.posthog__readConditional: needs read access to feature flags on the key
Cohort definitionsList the cohorts and what defines each one.posthog__readConditional: needs read access to cohorts on the key
Event checkList the event definitions so I know which events exist.posthog__readConditional: needs read access to event definitions on the key
Campaign dashboardCreate a trends insight for landing page signups and add it to a new campaign dashboard.posthog__writeNo: needs a key with insight:write and dashboard:write
Campaign cohortCreate a cohort of people who arrived from one campaign.posthog__writeNo: needs a key with cohort:write
Remove a test cohortDelete the old test cohort. I confirm it cannot be undone.posthog__deleteNo: needs a key with cohort:write, and the deletion is irreversible

Jobs the connection does not cover in Ryze AI's facts: more than one project at a time, session recordings, experiments, surveys and error tracking, and any change when the key holds read scopes only.

5 ways to connect Antigravity to PostHog

Five ways can give the Antigravity agent your PostHog data. This guide treats the first, the Ryze AI connector, as the main way: Antigravity stores one serverUrl entry, the PostHog key sits in Ryze AI and no OAuth app is involved. The others were read on their own pages on November 14, 2026 and none was installed for this guide, so the setup column describes what each page says and how it would fit Antigravity's mcp_config.json.

WayRuns whereSetupWhat it reaches in PostHogPrice
Ryze AI connector (the main way)Hosted by Ryze AI, one address for Antigravity, Claude, ChatGPT and other MCP clientsSave a personal API key and host in Ryze AI, pick the project, then add a ryze entry with serverUrl https://connector.get-ryze.ai/mcp and sign in3 tools: read (projects, insights, dashboards, flags, cohorts, persons, event definitions, HogQL queries), write and delete. One project per connection, limited by the key's scopesFree to connect. The tools need an active plan or trial: Paid Ads $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial, Agency $279 per month
PostHog MCP server, hosted by PostHogPostHog hosts it at https://mcp.posthog.com/mcp over streamable HTTP and routes sign-in to your US or EU regionPostHog recommends OAuth sign-in in the client. For clients without OAuth it describes a personal API key with the MCP Server preset sent as an Authorization: Bearer header. Antigravity's headers object can carry such a header. PostHog's setup pages name other clients than Antigravity, and the pairing was not tested1,284 tools in 78 categories on PostHog's tools page of November 14, 2026, read and write, covering product analytics, session replay, feature flags, experiments, error tracking, surveys and more. ?readonly=true removes tools that create, update or deleteFree to connect and call. PostHog says some tools use LLMs internally and may bill as PostHog AI spend. Usual PostHog usage pricing applies to data
ComposioHosted by Composio at https://connect.composio.dev/mcpAdd the address as a serverUrl entry and authenticate. PostHog itself is joined with your own API key. Composio's toolkit page lists Antigravity among its assistantsThe PostHog toolkit lists 686 tools and 11 triggersFree plan $0 with app tool calls stopping at 10,000 per month, Standard $18 per seat per month, extra calls $0.005 each. The toolkit FAQ quotes a different free allowance, so check both pages
Pipedream MCPHosted by Pipedream at https://mcp.pipedream.net/v2PostHog is joined with an API key. Pipedream's page does not name Antigravity, and its setup for Antigravity was not read10 actions: List Project Insights, Get Project Insight, Create Query (a HogQL query), List Organization ID Options, Update Project Insight, Get Surveys, Get Persons, Get Cohorts, Create Project Insight and Capture EventNo price on the page
AnythingMCP (open source)AnythingMCP Cloud in Frankfurt, or self-hosted with DockerMake a phx_ key, set POSTHOG_HOST and POSTHOG_PERSONAL_API_KEY, then add your AnythingMCP server URL in the client with OAuth. Its guide names ChatGPT, Claude, Gemini, Cursor and Copilot, not Antigravity28 tools, including HogQL and insight queries, dashboards, flags, cohorts, annotations and persons. Three delete tools are off at install. The guide says it does not create or edit dashboards, cohorts or experimentsCloud Starter 19 euros per month and Team 49 euros per month with a 7-day trial. The self-hosted Community edition is free under AGPL-3.0 for up to 3 active users

PostHog's server is far wider than the Ryze AI one, and it runs in CLI mode (a single exec tool) or tools mode depending on the client. PostHog says most clients default to CLI mode, including Claude, Claude Code and Codex, while Cursor defaults to tools mode, and it does not say which mode an Antigravity connection would get. Its limit of 480 requests per minute and 4,800 per hour counts per credential. Zapier lists one PostHog action, Capture Event, so it fits event capture and not reading insights.

Options that do not fit Antigravity

  • Claude connector directory and the PostHog plugin in ChatGPT. PostHog's connector for Claude and its plugin in ChatGPT's directory install inside those assistants and do not run in Antigravity.
  • PostHog AI plugin. The plugin adds PostHog's MCP server with skills and slash commands to AI coding tools. PostHog names Claude Code, Cursor, Gemini and Codex for it, and Antigravity is not named. It points at the same hosted server.
  • PostHog CLI and wizard. posthog-cli runs queries and calls from a terminal. npx @posthog/wizard mcp add writes the hosted server into supported clients, and PostHog does not list Antigravity as one.
  • Zapier MCP, Windsor.ai and Coupler.io. Zapier's PostHog page lists one action, Capture Event. Windsor.ai and Coupler.io export PostHog entities such as events, insights, cohorts and flags to AI destinations on their own schedules, and their pages leave out how the PostHog access works.
  • Retired PostHog packages. The PostHog/mcp repository is archived and its README says the server moved into the PostHog monorepo. The npm package @posthog/agent-toolkit is deprecated in favour of the MCP server.
  • Antigravity's MCP Store and Plugin Marketplace. The IDE installs catalog servers from its MCP Store and the App and CLI from the Plugin Marketplace, open since October 29, 2026. Ryze AI is not one of the 77 servers on Google's MCP page, and no catalog was searched for a PostHog entry.

Which one to pick

Ryze AI is the best way to connect Antigravity to PostHog for read-only analytics questions on one project with a key you scope yourself, with three caveats: it has only 3 tools and one project per connection, its facts do not cover session replay, experiments, surveys or error tracking, and the tools need a Ryze AI plan once the trial ends. Pick PostHog's own server when you need its full tool list and are ready to test sign-in with Antigravity yourself. Pick Composio when a long tool list from a third party fits, Pipedream for its 10 listed actions, and AnythingMCP for a self-hosted server. The Ryze AI connector and PostHog's server can sit in one mcp_config.json under different names.

Sources: PostHog MCP docs, MCP FAQ, posthog.com/mcp, PostHog AI plugin, archived PostHog/mcp, Composio PostHog toolkit, Composio pricing, Pipedream MCP for PostHog, AnythingMCP guide, AnythingMCP on GitHub, AnythingMCP pricing, Zapier MCP for PostHog, Windsor.ai PostHog and Coupler.io PostHog, checked November 14, 2026. Antigravity setup and catalogs from the Antigravity MCP documentation, checked November 15, 2026.

PostHog, Antigravity and MCP: dates that matter

DateEvent
May 14, 2025The PostHog/mcp repository was created as the Official PostHog MCP Server. It is now archived, and its README says the server moved into the PostHog monorepo.
November 13, 2025@posthog/agent-toolkit 0.2.4 was published, its last version. The package is deprecated in favour of the MCP server.
November 18, 2025Google Antigravity shipped as an AI-powered IDE. The launch entry does not mention MCP.
December 16, 2025A Google Cloud blog post showed installing Google Cloud MCP servers from the Antigravity MCP Store, the oldest dated Google page on Antigravity and MCP that the research found.
February 18, 2026The PostHog/ai-plugin repository was created, a plugin for AI coding tools.
February 27, 2026PostHog's changelog announced a PostHog connector for Claude and, the same day, cohort management through its MCP server.
May 4, 2026PostHog added explicit MCP mode selection, tools or cli, by header or query parameter.
May 19, 2026Google released the Antigravity App and the Antigravity CLI and began moving Gemini CLI users to the CLI.
October 1, 2026PostHog extended MCP connections so clients with non-rotating refresh tokens stop asking for a new authorization after roughly 67 days.
October 22, 2026PostHog's wizard started to detect Claude Code and Codex and install the MCP connection, with a separate flow for browser clients such as ChatGPT and Claude.
October 29, 2026The Plugin Marketplace opened in the Antigravity App and CLI.
November 6, 2026Antigravity CLI 1.5.2 fixed MCP OAuth sign-ins that failed with Invalid PKCE code_verifier when a server reconnected mid sign-in.
November 9, 2026Antigravity App 2.30.0 added the Knowledge Work layout that hides the MCP Servers list, and an import of MCP servers from other coding tools.
November 14, 2026PostHog's own page counted 1,284 MCP tools in 78 categories.

Sources: PostHog changelog, PostHog/mcp repository data, PostHog/ai-plugin repository data, npm registry and posthog.com/mcp, checked November 14, 2026; Antigravity changelog, Google Cloud blog, December 2025, Google Developers Blog, May 2026 and Antigravity blog, October 2026, checked November 15, 2026.

How this guide was tested

Two sets of checks stand behind this guide. On November 14, 2026 the PostHog sources named on this page were opened, and no PostHog call was run, because no PostHog account was connected during the research. On November 15 the connector's sign-in data was compared with the OAuth order in Google's Antigravity docs.

CheckResult
Connector address without a sign-in, November 15A request to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header that points to the sign-in details.
The connector's discovery files, November 15Both protected resource files list one authorization server and the scopes mcp:read and mcp:write. The file for the /mcp path names https://connector.get-ryze.ai/mcp, which is the match Antigravity requires. The root file names the host without /mcp, and Google does not say which one Antigravity reads.
Sign-in data against Antigravity's client order, November 15A registration endpoint is listed, Client ID Metadata Documents are marked unsupported, PKCE with S256 is supported and clients without a secret are accepted. Antigravity's third route, dynamic client registration, is the one that applies.
PostHog sources, November 14Scopes, key rules, limits, own MCP server, third-party servers and dates were read on PostHog's documentation, changelog, registry and vendor pages named in the Sources lines.
PostHog calls through the connectorNone were run, so no tool output, project data or PostHog error from the connector is shown on this page.

Not run for this guide: anything inside Google Antigravity and any PostHog call. The IDE, the App and the CLI were not opened, and no Ryze AI sign-in was completed from them, so the setup, sign-in and approval steps follow Google's Antigravity documentation as read on November 15, 2026. The PostHog tool names come from the Ryze AI app source and were not seen on a live connection.

Antigravity and PostHog errors and fixes

Responses PostHog documents

These responses are documented by PostHog. None was produced by a test for this guide, and the Ryze AI connector may word them differently when it passes them on.

Message or codeWhat it meansWhat to do
401 invalid_personal_api_key (Invalid Personal API key.)The personal API key is not valid for the host you entered.Create a new key, check that you copied the whole phx_ value and that the host matches your region, then reconnect PostHog in Ryze AI.
403 that names the missing scopeThe key lacks a scope the request needs, such as dashboard:read or cohort:write.Add the scope the message names to the key in PostHog, then ask again.
429 api_queries_budget_exceeded, with Retry-AfterThe project's hourly read budget for personal API key queries is used up. Cached results still work.Wait for the Retry-After time and ask for narrower queries with a shorter time window.
400 on OFFSETOFFSET paging on the query endpoint is rejected for personal API keys.Ask for the next page with a timestamp filter instead of an offset.

Other problems

The server never finishes connecting
Antigravity waits up to 5 minutes for a server to connect. Check that mcp_config.json is valid JSON, that the entry uses serverUrl (or url) and not httpUrl, then reload the configuration.
Authenticate does nothing in the App
Finish the Ryze AI sign-in in the browser, copy the authorization code it shows, paste it into Enter authorization code and click Submit.
The MCP Servers section is missing in the App
The App is in the Knowledge Work layout. Open Settings > General > Interface Layout and choose Software Engineering.
The PostHog tools do not appear
A tool list can be cached from before PostHog was connected. Remove the ryze entry, add it again, then open a new chat. Check that the PostHog card in Ryze AI shows Connected.
A query is refused or returns too little
HogQL queries need a time window and at most 1,000 rows. Ask for a date range and a limit, then narrow the question if PostHog's read budget runs out.
A listing fails with a 403
The key lacks the scope for that object. Add the scope the message names to the personal API key in PostHog.
The agent cannot change anything
That is expected with a read-only key, because PostHog rejects changes. Add write scopes to the key for the objects the agent should edit.
Another project is needed
A connection holds one project. Click View on the PostHog card, disconnect with the trash icon and connect again, or use another Ryze AI workspace.
The one-time connection link is refused
Ryze AI refuses the link while PostHog is already connected in the workspace. Switch keys or projects in the Ryze AI app.
Every tool call asks for approval
That is Antigravity's Ask mode for MCP tools without a rule. Allow chosen tools with the mcp(server/tool) form.
The tools say a subscription is required
The PostHog tools need an active Ryze AI plan or free trial. Start the trial, then retry.

Terms on this page

MCP
The Model Context Protocol, an open standard through which an assistant such as Antigravity calls tools on outside servers.
Personal API key
A PostHog key that starts with phx_ and authenticates private endpoints as your own user. You choose its scopes, and a user can have up to 10.
Scope
A permission for one part of PostHog, such as feature flags or insights, with a read level and a write level.
HogQL
PostHog's SQL, a wrapper around ClickHouse SQL, used to query events, persons and sessions.
Insight
A saved analysis in PostHog such as a trends chart, a funnel or a retention table.
Host
The address your PostHog account lives on: https://us.posthog.com, https://eu.posthog.com or your own domain when self-hosted.
Ask mode
Antigravity's default for an MCP tool that has no rule: each call waits until you approve it.

Sources: personal API keys, scopes, SQL and HogQL, insights and API overview, checked November 14, 2026; Antigravity MCP documentation, checked November 15, 2026.

Frequently asked questions

How do I connect Antigravity to PostHog?

Save a PostHog personal API key and host in Ryze AI and pick the project, then add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json and complete the Ryze AI sign-in.

Is there a PostHog connector for Antigravity?

Yes, a few. The Ryze AI connector at https://connector.get-ryze.ai/mcp goes in as one serverUrl entry. PostHog hosts its own MCP server at https://mcp.posthog.com/mcp, and Composio lists Antigravity among its assistants for its PostHog toolkit.

Is there a PostHog MCP server for Antigravity?

PostHog runs a hosted MCP server at https://mcp.posthog.com/mcp, but its setup pages name Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed and do not name Antigravity. Whether it works with Antigravity's OAuth sign-in was not tested here.

What is a PostHog MCP server?

A server that lets an AI client such as Antigravity call PostHog tools over the Model Context Protocol. The Ryze AI one has 3 tools that read data and run HogQL queries, write objects and delete them.

Where is the Antigravity MCP config file?

The global file is ~/.gemini/config/mcp_config.json and a workspace file is .agents/mcp_config.json. In the IDE, open the ... menu in the agent panel, then MCP Servers, Manage MCP Servers and View raw config.

Which Antigravity plan do I need for MCP?

No particular plan: Google's Antigravity MCP documentation names none. The setup is the same in the IDE, the App and the CLI, apart from how the sign-in starts.

Does Antigravity need a client ID for the Ryze AI connector?

No. Antigravity runs OAuth 2.0 with PKCE and registers itself with servers that support dynamic client registration, which the Ryze AI connector does. The PostHog key is separate and lives in Ryze AI.

Which PostHog key scopes does it need?

Read access to the project you want, including the Query and Insight scopes. Add write scopes only for objects the agent should change. If a call returns a 403, PostHog names the missing scope.

Can Antigravity change my PostHog project?

Yes, if the key allows it. The write tool creates or updates insights, dashboards, feature flags and cohorts. With read scopes only, PostHog rejects every change.

Can Antigravity delete things in PostHog?

Yes, when the key has the write scope and you ask explicitly. The delete tool removes a PostHog object by path, such as a cohort, and the deletion is irreversible.

Can I use several PostHog projects?

One per connection. To switch, disconnect on the PostHog card in Ryze AI and connect again. Another project can live in another Ryze AI workspace.

Does the Antigravity CLI work with the connector?

The CLI reads the same mcp_config.json files, and /mcp opens the MCP Manager to check status and reload. Google lists no CLI sign-in steps, so this guide gives none, and the connector was not tested inside Antigravity.

How much does it cost?

Connecting costs nothing, but the tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.

How do I disconnect?

Delete the ryze entry from mcp_config.json, disconnect PostHog on its card in Ryze AI, or delete the personal API key in PostHog.

Connect PostHog to Antigravity

Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month; annual billing takes 30% off the first year. Connecting is free, and the tools need an active plan or trial.

PostHog with Ryze AI

Need help? Read the Ryze AI PostHog guide or email Ryze AI support.