PostHog vs Statsig

PostHog

PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,096 tools. The status page shows 31 incidents in 90 days, four on analytics queries, and three security incidents were disclosed in the last year.

Statsig

Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.

PostHog

1. Add ?readonly=true or the x-posthog-read-only header to the MCP URL unless the task needs writes
2. Pin the session with x-posthog-project-id, which also removes the switch-project and switch-organization tools
3. In CLI mode run info <tool> once before call, and send one exec command per request
4. On a 429 with code api_queries_budget_exceeded, wait for Retry-After and read X-PostHog-Query-Budget-Remaining-Bytes
5. Page SQL results by keyset on timestamp. OFFSET returns 400 for personal API keys, and results cap at 50,000 rows

Statsig

1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
2. Call get_context first to learn the project, your permissions and the review settings
3. Read the resource before gate_update, experiment_update or dynamic_config_update. They replace the whole resource, so resend every field you want kept
4. Use discover_tools for partial edits, and fetch a fresh operationHandle when one expires
5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes