AgentsReady
Verified deep dive · Comms & data

PostHog

Run the agent liveReport a change
2 minTime to key
YesNo-human path
0Gates to a test key
10/10Onboarding score
Live keys only:Email verification

Fastest path to a key

  1. `npx @posthog/wizard@latest --signup --email you@example.com --region us` - creates account + project via provisioning API (OAuth 2.0 + PKCE), writes project API key + host into the codebase, installs SDK
  2. First events flow immediately (project key phc_ is client-safe)
  3. `npx @posthog/wizard mcp add` installs remote MCP (https://mcp.posthog.com/mcp, OAuth) into Claude Code/Cursor/VS Code/etc.
  4. Later: human sets password from welcome email to use web app; personal API key (scoped, 'MCP Server' preset) only if needed for REST scripts
  5. Working API key

Biggest gap

Signup wizard cannot run headless (--ci disabled) and the signup path does not mint a personal API key for REST use.

Worth copying

Machine-discoverable auth: an unauthenticated 401 points to protected-resource metadata, which leads to an auth.md manifest describing how to sign up and authenticate - no hardcoded endpoints.

Sources (8) · checked 2026-10-11
90Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context17/20
Interfaces32/32
Onboarding19/19
Trust2/9
llms.txt · root
MCP · https://mcp.posthog.com/mcp
OpenAPI · https://posthog.com/openapi.json

Biggest gains

  1. +4 Agent manifests. Publish an MCP server card (/.well-known/mcp.json) or A2A agent card.
  2. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
  3. +3 Public status page. Link a status page so agents can tell outages from bugs.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 4 changes, up to +10 points

Each change is ready to paste, filled in for posthog.com, with a command to check it worked. Or hand the whole list to your coding agent.

A server card lets agents discover your MCP server from your domain alone.

Where: https://posthog.com/.well-known/mcp.json
{
  "name": "Posthog",
  "description": "<What an agent can do with Posthog, in one sentence>",
  "url": "https://mcp.posthog.com/mcp",
  "transport": "streamable-http",
  "authentication": { "type": "oauth2", "resource_metadata": "https://mcp.posthog.com/.well-known/oauth-protected-resource" },
  "documentation": "https://docs.posthog.com",
  "tools": ["<tool_one>", "<tool_two>"]
}
Check it worked:curl -s https://posthog.com/.well-known/mcp.json

Add the badge to your README

AgentsReady badge for posthog.com
[![AgentsReady](https://agentsready.dev/badge/posthog.com)](https://agentsready.dev/c/posthog.com)