MCP Gateway · Claude Cowork
Connect PostHog to Claude Cowork
Building a weekly metrics dashboard, setting alerts on the numbers that matter, or writing up a quarter of survey feedback takes many PostHog steps. Cowork can take each of these on as one longer task. PostHog reaches Cowork through the organization's synced plugin marketplace, and Speakeasy's agent hooks check every prompt before a step runs.
- Category
- Data & analytics
- Tools
- 172
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
Behind the MCP Gateway
Run PostHog MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every PostHog call inspected and logged.
Set up
Add PostHog to Claude Cowork in 4 steps
- 01
Add PostHog from the catalog
An admin finds PostHog in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
PostHog authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use PostHog
Give teams the
mcp:connectscope on the PostHog server through team access or a role. Claude Cowork connects to the PostHog server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use PostHog from Claude Cowork
The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, PostHog's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with PostHog
Build a weekly metrics dashboard
Cowork writes and tests a query for each metric, saves each one as an insight, and gathers them on a new dashboard for the weekly review.
Set alerts on key insights
Cowork goes through the team's saved insights and creates a threshold or anomaly alert on each one that tracks a number the team watches.
Write up survey feedback for the quarter
Cowork reads response statistics across all surveys and writes the findings into a PostHog notebook the product team can comment on.
Tools
172 tools
Each PostHog tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.
docs-search
Use this tool to search the PostHog documentation for information that can help the user with their request. Use it as a fallback when you cannot answer the user's request using other tools in this MCP. Only use this tool for PostHog related questions.
experiment-get-all
Get all experiments in the project.
experiment-create
Create a comprehensive A/B test experiment. , ['product_view', 'add_to_cart', 'purchase']) and use funnel_steps parameter 6) Configure variants (default 50/50 control/test unless they specify otherwise) 7) Set targeting criteria if needed.
experiment-delete
Delete an experiment by ID.
experiment-update
Update an existing experiment by ID. Can update name, description, lifecycle state, variants, metrics, and other properties. RESTART WORKFLOW: To restart a concluded experiment, set end_date=null, conclusion=null, conclusion_comment=null, and optionally set a new start_date.
experiment-get
Get details of a specific experiment by ID.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.
Tool logs
Gateway
Every PostHog call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the PostHog tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to PostHog can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does the device agent set up PostHog in Cowork?
How are Cowork sessions with PostHog tied to people?
How do Claude Cowork users get PostHog?
Are PostHog calls from Claude Cowork logged?
Connect more