Countly vs PostHog

Countly

Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card.

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.

Countly

1. Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the countly-token header, not the URL
2. Set COUNTLY_TOOLS_ALL=R unless the task needs writes. The token's own permissions still apply and the stricter of the two wins
3. Call apps_list first. Most tools need app_id or an exact app_name
4. Check get_version for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins
5. Set ENABLE_ANALYTICS=false to stop usage reports to stats.count.ly, and prefer the stdio server to mcp.count.ly so the server URL and token stay local

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