Integration · Research and analyze

PostHog and Meteor AI agents

Connect PostHog to a WhatsApp Met: query saved insights, dashboards, surveys and experiments of your website or app with the official MCP.

Book a demo See every integration

How does PostHog connect to Meteor?

With the PostHog ready connector, your Met queries the analytics of your website or app through PostHog's official MCP server, authorized once with OAuth. It runs the insights your team already saved, opens your dashboards, pulls an experiment's results and a survey's stats, and explores which events and properties you track. If you work with several clients, it switches organization and project to answer for each one. Running raw SQL and creating or changing feature flags start switched off, as do delete actions. Connecting is free; the data you query follows your PostHog account's normal billing.

What it automates

What a Meteor Met does with PostHog

Answer a number with a saved insight

You ask the Met on WhatsApp how many sign ups there were this week. It finds the insight your team saved for that, runs its query and replies with the result PostHog returns.

Check each client in its own project

For an agency, the Met lists organizations and projects, switches to the client you name and pulls their dashboards, without mixing one client's data with another's.

Report how a survey is going

The Met finds the survey on your website or app and pulls its response stats, so you know how many people answered and what they chose.

Read an experiment's result

The Met opens the experiment, pulls its metric and exposure results, and sums them up in the chat with what PostHog says.

38 tools

Everything your Met can ask PostHog for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`organizations_get`	Returns the PostHog organizations the connected account can access.
`switch_organization`	Switches the active organization for the following calls.
`projects_get`	Returns the projects the account can access in the current organization.
`switch_project`	Switches the active project for the following calls.
`read_data_schema`	Explores the events, actions, properties and values the project tracks.
`event_definition_update`	Updates the descriptive metadata of an event definition.
`insight_get`	Returns a saved insight.
`insight_query`	Runs a saved insight's query and returns its results.
`insight_update`	Updates a saved insight.
`insight_delete`	Deletes an insight. Starts switched off.
`dashboards_get_all`	Returns all of the project's dashboards.
`dashboard_get`	Returns the details of a project dashboard.
`dashboard_create`	Creates a new dashboard.
`dashboard_update`	Updates a dashboard.
`dashboard_reorder_tiles`	Changes the order of a dashboard's tiles.
`dashboard_delete`	Deletes a dashboard. Starts switched off.
`feature_flag_get_all`	Returns all of the project's feature flags.
`feature_flag_get_definition`	Returns a feature flag's definition.
`create_feature_flag`	Creates a feature flag. Starts switched off by the connector's setup.
`update_feature_flag`	Updates a feature flag. Starts switched off by the connector's setup.
`delete_feature_flag`	Deletes a feature flag. Starts switched off.
`experiment_get`	Returns an experiment's details.
`experiment_results_get`	Returns an experiment's metric and exposure results, with each metric's details.
`experiment_create`	Creates an experiment.
`experiment_update`	Updates an experiment.
`experiment_delete`	Deletes an experiment. Starts switched off.
`surveys_get_all`	Lists the project's surveys, with search and filters.
`survey_get`	Returns a survey by ID.
`survey_stats`	Returns a survey's response stats.
`surveys_global_stats`	Returns the response stats added up across all surveys.
`survey_create`	Creates a new survey in the project.
`survey_update`	Updates an existing survey.
`survey_delete`	Deletes a survey. Starts switched off.
`actions_get_all`	Returns all the actions defined in the project.
`action_get`	Returns an action defined in the project.
`action_create`	Creates an action, which groups events under a name.
`execute_sql`	Runs an SQL query on the project's data. Starts switched off by the connector's setup.
`docs_search`	Searches PostHog's documentation.

The limits

What the PostHog integration does NOT do

We would rather say it here than have you find out during rollout.

It does not run free form SQL with the initial setup. That action starts switched off, along with creating or changing feature flags; the admin decides whether to turn them on.
It does not ask you for confirmation in the chat before writing. The admin chooses in Connections which actions stay on; delete actions start switched off.
It does not install PostHog on your site. For there to be data, your website or app has to be sending events to PostHog.
It does not run thousands of queries in a row. The server allows 480 requests per minute and 4,800 per hour per connection.
It does not pay your PostHog account. Connecting is free, but the data you query follows your account's billing; Meteor does not resell the service.

Before you start

What you need to connect PostHog

1

A PostHog project with data

Your website or app sends events to a PostHog project. It helps to have the insights and dashboards your team checks often already saved.
2

Connect it in Met

In Met, open Connections → PostHog → Connect. A PostHog window opens so you can sign in and authorize access; PostHog picks your account's data region on its own.
3

Decide which actions stay on

The workspace admin reviews the list of actions. Raw SQL and feature flags start switched off, as do delete actions.