Countly vs Statsig

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.

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.

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

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