PostHog Experiments (BYOK) — connector documentation
- MCP endpoint:
https://byok-posthog-experiments.connectorbay.com/mcp - REST API:
POST https://byok-posthog-experiments.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-posthog-experiments.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own PostHog Experiments personal API key (with experiment:read and activity_log:read scopes), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-posthog-experiments.connectorbay.com/health· Tool schemas:https://byok-posthog-experiments.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-posthog-experiments · agent@connectorbay.com
What PostHog Experiments (BYOK) is for
PostHog Experiments (BYOK) lets an AI assistant read your own PostHog Experiments data through the PostHog Experiments API with a key you supply (personal API key (with experiment:read and activity_log:read scopes)). Read-only: 5 tools (list_experiments, get_experiment, get_experiment_health, get_experiment_session_exposure, list_experiment_activity). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to us.posthog.com, eu.posthog.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PostHog Experiments. PostHog Experiments and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which A/B experiments are running in my PostHog project?"
- "Show the details of PostHog experiment 7"
- "Is PostHog experiment 7 healthy?"
- "Can I scope PostHog recordings to experiment 7 exposure?"
- "What changes were made to PostHog experiment 7?"
What it does
list_experiments: List the A/B experiments of a project with name, status, start and end dates, linked feature flag key, conclusion and tags. Filter by status, archive state or text.get_experiment: Get one experiment with its name, description, status, dates, linked feature flag key, conclusion, tags and legacy flag.get_experiment_health: Get the health findings PostHog reports for an experiment, such as a flag turned off while running or a rollout of zero, each with code, severity, title and detail.get_experiment_session_exposure: Show whether the in-session exposure scope of the recordings tab is available for an experiment, and whether it falls back to the stamped flag property.list_experiment_activity: List the change history of one experiment: what happened (created, updated, launched), when, and the item name; people are left out.
BYOK key
You bring your own PostHog Experiments personal API key (with experiment:read and activity_log:read scopes) (https://us.posthog.com/settings/user-api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to us.posthog.com, eu.posthog.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://posthog.com/docs/api/experiments (the API this connector calls, with a BYOK key)
Live from the PostHog Experiments API (us.posthog.com, eu.posthog.com) with a BYOK key; documentation: https://posthog.com/docs/api/experiments. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PostHog Experiments. PostHog Experiments and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your PostHog Experiments account.
Built for: Worldwide. Languages: English.