{ "data": { "a": { "slug": "countly", "name": "Countly", "vendor": "Countly Ltd", "vendorUrl": "https://countly.com", "kind": "http-api", "category": "product-analytics", "summary": "Countly is a product analytics platform sold as a managed private-cloud server (Flex), a self-hosted Enterprise edition and the open-source Countly Lite. Agents reach a Countly server through its HTTP API or the official `countly-mcp-server`.", "url": "https://www.anchorterminal.com/tools/countly", "markdownUrl": "https://www.anchorterminal.com/tools/countly.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/countly.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/countly.json", "repo": "https://github.com/Countly/countly-server", "license": "Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://mcp.count.ly/mcp", "packages": [ { "registry": "npm", "name": "countly-mcp-server" }, { "registry": "npm", "name": "countly-sdk-web" }, { "registry": "npm", "name": "countly-sdk-nodejs" } ], "auth": "api-key", "authNotes": "Self-serve once a server exists. A dashboard user copies an `api_key`, which has that user's full read and write access, or creates an auth token in the Token Manager or with `/i/token/create`, limited by app, endpoint pattern and lifetime. Tokens go in the `countly-token` header or the `auth_token` query parameter. The MCP server takes `COUNTLY_SERVER_URL` and `COUNTLY_AUTH_TOKEN`, or `X-Countly-Server-Url` and `X-Countly-Auth-Token` headers over HTTP. SDKs send the write-only `app_key`.", "pricing": "paid", "pricingNotes": "Flex starts at $175 a month, billed by tier on monthly active users and data points, with a 14-day trial that needs a credit card. Tier prices appear during signup. Funnels, retention and flows sit in the Intelligence add-on. Enterprise is on quotation. Countly Lite is free to self-host. API and MCP calls are not billed (https://countly.com/pricing, checked 2026-10-08).", "priceSummary": "$175 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the MCP server README or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 209, "popularity": { "githubStars": null, "npmWeekly": 27579, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://api.count.ly/", "llmsTxt": "https://countly.com/llms.txt", "capabilities": [ "analytics.query", "analytics.events", "analytics.funnels", "analytics.experiments", "analytics.flags", "observability.errors" ], "tags": [ "official", "hosted", "self-hosted", "open-source", "mcp", "api-key", "llms-txt", "paid", "trial", "typescript" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 54.8, "grade": "C", "agentReady": false, "rank": 607, "ranked": true, "rankOf": 842, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 80, "payments": 17, "reliability": 28, "schema": 75, "security": 63, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "An agent whose owner runs Countly on its own infrastructure or a dedicated Flex server and wants analytics, crash and remote-config data through MCP with per-category permissions.", "strengths": [ "Official MIT MCP server, `countly-mcp-server` 1.7.0 of 7 October 2026, with read-only, destructive and idempotent annotations on its tools", "`COUNTLY_TOOLS_ALL=R` makes every MCP tool read-only, and per-category settings take None, R, CR, CRU or CRUD", "Auth tokens can be limited to named apps and endpoint patterns, carry a lifetime in seconds and are revocable", "API reference at api.count.ly is versioned (24.05, 25.03, 26.01) with parameters, examples and error responses per endpoint", "Sub-processor list with locations and a public DPA, both updated 25 September 2026, with 30 days' notice of sub-processor changes" ], "weaknesses": [ "No public status page or incident history was found for Flex servers or for mcp.count.ly", "No OpenAPI document was found, and the server's API rate limit is a setting that ships switched off with no published value for Flex", "The API accepts `api_key` and `auth_token` in the URL query string, and the `api_key` has its user's full read and write access", "Flex starts at $175 a month, its 14-day trial needs a credit card, and tier prices appear only during signup", "Funnels, retention, flows, cohorts and Drill need Enterprise or a paid Flex capability, and are absent from Countly Lite", "The MCP server reports usage to stats.count.ly by default until `ENABLE_ANALYTICS=false` is set" ], "agentNotes": [ "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", "Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins", "Call `apps_list` first. Most tools need `app_id` or an exact `app_name`", "Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.8 } ], "editorialScores": { "ergonomics": 66, "maintenance": 80, "payments": 17, "reliability": 28, "schema": 75, "security": 63, "transparency": 64 }, "provenanceScore": 76 }, "connect": { "install": "npx -y countly-mcp-server", "http": "curl -H \"countly-token: YOUR_TOKEN\" \"https://your-countly-url.com/o?app_id=APP_ID\u0026method=funneldata\u0026funnels=[%22FUNNEL_ID%22]\"", "claudeCode": "claude mcp add countly -e COUNTLY_SERVER_URL=https://your-countly-url.com -e COUNTLY_AUTH_TOKEN=YOUR_TOKEN -- npx -y --prefer-online countly-mcp-server@latest", "config": { "mcpServers": { "countly": { "args": [ "-y", "--prefer-online", "countly-mcp-server@latest" ], "command": "npx", "env": { "COUNTLY_AUTH_TOKEN": "YOUR_TOKEN", "COUNTLY_SERVER_URL": "https://your-countly-url.com" } } } } }, "letme": { "capability": "https://letme.dev/analytics.query", "tool": "https://letme.dev/countly" }, "area": "business", "unitPrices": [ { "item": "Flex, lowest tier", "unit": "month", "usd": 175, "note": "starting price, by monthly active users and data points, add-ons extra" } ], "provenance": { "legalEntity": "Countly Ltd", "domain": "countly.com", "domainRegistered": "2011-09-05", "endpointOnVendorDomain": true, "terms": "https://countly.com/legal/terms-of-service", "privacy": "https://countly.com/legal/privacy-policy", "statusPage": "", "changelog": "https://github.com/Countly/countly-server/blob/master/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms (last updated 25 September 2026) name Countly Ltd, incorporated in England and Wales with registered number 8568329, registered at 1 Bow Churchyard, London EC4M 9DQ. They cover Flex through supplemental terms and exclude Enterprise subscriptions, which have written agreements.", "The privacy policy (last updated 25 September 2026) covers Countly's websites, services and accounts and says it does not apply to data customers process with the Services. The DPA at countly.com/legal/dpa covers that data.", "The hosted MCP server answers at mcp.count.ly and the API reference at api.count.ly, a second domain of the vendor's. Each customer's API answers on that customer's own server address.", "countly.com/.well-known/security.txt returns 404. SECURITY.md in the repositories gives a disclosure address at count.ly.", "No status page was found. status.countly.com did not resolve.", "RDAP for countly.com gives a registration date of 2011-09-05." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/countly.json", "live": { "slug": "countly", "probe": { "target": "https://mcp.count.ly/mcp", "method": "get", "lastAt": "2026-10-09T10:14:12.099871769Z", "lastOk": false, "lastStatus": 500, "lastMs": 320, "lastNote": "server error", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-09", "probes": 28, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:23.474688008Z", "end": "0001-01-01T00:00:00Z", "note": "HTTP 500 server error" } ] }, "updatedAt": "2026-10-09T10:14:12.099871769Z" } }, "answer": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing.", "b": { "slug": "optimizely", "name": "Optimizely Experimentation", "vendor": "Optimizely", "vendorUrl": "https://www.optimizely.com", "kind": "http-api", "category": "product-analytics", "summary": "Optimizely Experimentation is a hosted platform for A/B tests, feature flags and personalisation, covering Web Experimentation and Feature Experimentation. Agents reach it through a hosted MCP server with seven tools and through REST APIs.", "url": "https://www.anchorterminal.com/tools/optimizely", "markdownUrl": "https://www.anchorterminal.com/tools/optimizely.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/optimizely.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/optimizely.json", "repo": "https://github.com/optimizely/javascript-sdk", "license": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://exp.mcp.opal.optimizely.com/mcp", "packages": [ { "registry": "npm", "name": "@optimizely/optimizely-sdk" }, { "registry": "pypi", "name": "optimizely-sdk" } ], "auth": "mixed", "authNotes": "Sales-led. Access needs a subscription. The MCP server uses OAuth 2.0 through Opti ID with PKCE and dynamic client registration, and needs an account with Opal enabled and linked to a Feature Experimentation or Web Experimentation instance. The REST APIs take a personal access token, created under Profile then API Access, in the `Authorization: Bearer` header, or OAuth 2.0 for a registered application. Tokens and MCP sessions act with the user's role.", "pricing": "paid", "pricingNotes": "No price is published. The plans page says every plan is individually packaged and leads to a demo request. No free plan, trial or sandbox was found, so an agent cannot start without a contract. MCP use does not consume Opal credits (https://www.optimizely.com/plans/, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the v2 Swagger spec or the plans page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": 460480, "pypiWeekly": 85924, "asOf": "2026-10-08" }, "docsUrl": "https://docs.optimizely.com/experimentation-strategy/docs/optimizely-experimentation-mcp-server-overview", "llmsTxt": "https://docs.optimizely.com/llms.txt", "openapi": "https://api.optimizely.com/v2/swagger.json", "capabilities": [ "analytics.experiments", "analytics.flags", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "webhooks", "status-page", "sla", "soc2", "iso27001", "bug-bounty" ], "lastRelease": "2026-09-18", "graded": true, "anchor": { "graded": true, "score": 62.6, "grade": "B", "agentReady": false, "rank": 383, "ranked": true, "rankOf": 842, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.", "bestFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "strengths": [ "Hosted MCP server with seven tools for querying, managing and implementing flags and experiments, released on 29 April 2026", "MCP sign-in is OAuth 2.0 with PKCE and dynamic client registration, and the server sees only what the user's account can see", "Public Swagger 2.0 spec for the Optimizely API with 93 operations, each with a description, plus llms.txt and a Markdown copy of every docs page", "Rate limits are published with numbers, 120 requests a minute on the Feature Experimentation API and 100 a minute on the Optimizely API", "Change history is readable through the REST API, and change approvals route flag changes to reviewers since 6 August 2026" ], "weaknesses": [ "No price is published. The plans page says every plan is individually packaged and leads to a demo request", "No free plan or trial was found, and the MCP server needs an account with Opal enabled", "No 429 response, `Retry-After` header or idempotency key was found in the spec or the pages read", "The REST OAuth flow has one scope, `all`, described as full access to the account", "The spec for the Feature Experimentation API at `/flags/v1` answers 401 without a token, and the MCP server is not in the official MCP registry" ], "agentNotes": [ "Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again", "Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs", "Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data", "Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript", "Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.6 } ], "editorialScores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 63 }, "provenanceScore": 86 }, "connect": { "http": "curl -H \"Authorization: Bearer YOUR_ACCESS_TOKEN\" \"https://api.optimizely.com/v2/projects\"", "claudeCode": "claude mcp add --transport http optimizely-exp https://exp.mcp.opal.optimizely.com/mcp", "config": { "mcpServers": { "optimizely-exp": { "type": "http", "url": "https://exp.mcp.opal.optimizely.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.experiments", "tool": "https://letme.dev/optimizely" }, "area": "business", "provenance": { "legalEntity": "Optimizely North America Inc.", "domain": "optimizely.com", "domainRegistered": "2010-01-11", "endpointOnVendorDomain": true, "terms": "https://www.optimizely.com/legal/terms/", "privacy": "https://www.optimizely.com/legal/privacy-notice/", "statusPage": "https://status.optimizely.com", "changelog": "https://docs.optimizely.com/feature-experimentation/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Software Subscription Agreement 2025-11, published 10 November 2025, names Optimizely North America Inc as the contracting entity for customers in the USA, Canada, Mexico, Australia, New Zealand, APJ and the rest of the world, Optimizely AB for the Nordics, UK, Ireland, EU, UAE and Saudi Arabia, and Optimizely GmbH for DACH.", "The API, SDK and MCP terms, version 2026-08 published 26 August 2026, are a PDF linked from https://www.optimizely.com/legal/api-sdk-mcp-terms/ and form part of the subscription agreement.", "The privacy notice, V 2026-07 published 1 July 2026, says it does not apply to customer data, which Optimizely processes under the subscription agreement and the Data Processing Agreement (V 2026-01).", "The MCP server answers at exp.mcp.opal.optimizely.com and the REST APIs at api.optimizely.com.", "www.optimizely.com/.well-known/security.txt and www.optimizely.com/security.txt both return 404.", "RDAP for optimizely.com gives a registration date of 2010-01-11." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/optimizely.json", "live": { "slug": "optimizely", "probe": { "target": "https://exp.mcp.opal.optimizely.com/mcp", "method": "get", "lastAt": "2026-10-09T10:14:22.987549307Z", "lastOk": true, "lastStatus": 401, "lastMs": 136, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 99.37, "uptime30d": 99.37, "p50ms24h": 144, "p95ms24h": 165, "samples24h": 159, "samples30d": 159, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 109, "ok": 108 } ] }, "vendorStatus": { "page": "https://status.optimizely.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:11:12.595390835Z" }, "updatedAt": "2026-10-09T10:14:22.987549307Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Countly Ltd", "b": "Optimizely", "name": "Vendor" }, { "a": "https://mcp.count.ly/mcp", "b": "https://exp.mcp.opal.optimizely.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT", "b": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "name": "Licence" }, { "a": "209", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-09-18", "name": "Last release" }, { "a": "2026-09-25", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-25", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "28k npm/wk", "b": "460k npm/wk, 86k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Countly or Optimizely Experimentation?" }, { "answer": "Countly needs an API key. Optimizely Experimentation takes an API key or an OAuth sign-in.", "question": "Do Countly and Optimizely Experimentation need an API key?" }, { "answer": "Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Optimizely Experimentation at https://exp.mcp.opal.optimizely.com/mcp.", "question": "Can an agent call Countly and Optimizely Experimentation without installing anything?" }, { "answer": "Countly is open source (Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT). No open-source release is listed for Optimizely Experimentation.", "question": "Are Countly and Optimizely Experimentation open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 17 against 0" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "An agent whose owner runs Countly on its own infrastructure or a dedicated Flex server and wants analytics, crash and remote-config data through MCP with per-category permissions.", "slug": "countly", "watchFor": "No public status page or incident history was found for Flex servers or for mcp.count.ly" }, { "aheadOn": [ "Reliability, 73 against 28", "Transparency \u0026 trust, 75 against 70" ], "also": null, "goodFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "slug": "optimizely", "watchFor": "No price is published. The plans page says every plan is individually packaged and leads to a demo request" } ], "job": { "capability": "analytics.query", "name": "Analytics query" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-countly.json", "title": "Amplitude vs Countly", "url": "https://www.anchorterminal.com/compare/amplitude-vs-countly" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.json", "title": "Amplitude vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-fullstory.json", "title": "Countly vs Fullstory", "url": "https://www.anchorterminal.com/compare/countly-vs-fullstory" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-growthbook.json", "title": "Countly vs GrowthBook", "url": "https://www.anchorterminal.com/compare/countly-vs-growthbook" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-mixpanel.json", "title": "Countly vs Mixpanel", "url": "https://www.anchorterminal.com/compare/countly-vs-mixpanel" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-pendo.json", "title": "Countly vs Pendo", "url": "https://www.anchorterminal.com/compare/countly-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-posthog.json", "title": "Countly vs PostHog", "url": "https://www.anchorterminal.com/compare/countly-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-statsig.json", "title": "Countly vs Statsig", "url": "https://www.anchorterminal.com/compare/countly-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-woopra.json", "title": "Countly vs Woopra", "url": "https://www.anchorterminal.com/compare/countly-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely.json", "title": "Fullstory vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.json", "title": "Mixpanel vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-pendo.json", "title": "Optimizely Experimentation vs Pendo", "url": "https://www.anchorterminal.com/compare/optimizely-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-woopra.json", "title": "Optimizely Experimentation vs Woopra", "url": "https://www.anchorterminal.com/compare/optimizely-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-heap.json", "title": "Countly vs Heap", "url": "https://www.anchorterminal.com/compare/countly-vs-heap" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely.json", "title": "GrowthBook vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-posthog.json", "title": "Optimizely Experimentation vs PostHog", "url": "https://www.anchorterminal.com/compare/optimizely-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.json", "title": "Optimizely Experimentation vs Statsig", "url": "https://www.anchorterminal.com/compare/optimizely-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly.json", "title": "Countly vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.json", "title": "LaunchDarkly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely" } ], "scores": [ { "by": 45, "countly": 28, "edge": "optimizely", "key": "reliability", "name": "Reliability", "optimizely": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "countly": 75, "edge": "countly", "key": "schema", "name": "Schema \u0026 documentation", "optimizely": 74, "weight": 13 }, { "by": 2, "countly": 66, "edge": "optimizely", "key": "ergonomics", "name": "Agent ergonomics", "optimizely": 68, "weight": 13 }, { "by": 3, "countly": 63, "edge": "optimizely", "key": "security", "name": "Security \u0026 auth", "optimizely": 66, "weight": 14 }, { "by": 17, "countly": 17, "edge": "countly", "key": "payments", "name": "Payments \u0026 pricing", "optimizely": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "countly": 80, "edge": "countly", "key": "maintenance", "name": "Maintenance \u0026 community", "optimizely": 78, "weight": 7 }, { "by": 5, "countly": 70, "edge": "optimizely", "key": "transparency", "name": "Transparency \u0026 trust", "optimizely": 75, "weight": 7 } ], "summary": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing. Both do analytics query.", "verdicts": { "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.", "optimizely": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/countly-vs-optimizely", "json": "https://www.anchorterminal.com/compare/countly-vs-optimizely.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/countly-vs-optimizely.md", "slim": "https://www.anchorterminal.com/compare/countly-vs-optimizely.min.md" }, "markdown": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing. Both do analytics query.\n\n- Countly: grade C, 54.8/100, rank #607 of 842. Markdown https://www.anchorterminal.com/tools/countly.md · JSON https://www.anchorterminal.com/api/v1/tools/countly.json\n- Optimizely Experimentation: grade B, 62.6/100, rank #383 of 842. Markdown https://www.anchorterminal.com/tools/optimizely.md · JSON https://www.anchorterminal.com/api/v1/tools/optimizely.json\n\n## Which one, for what\n\n### Countly (C)\n\nGood for: An agent whose owner runs Countly on its own infrastructure or a dedicated Flex server and wants analytics, crash and remote-config data through MCP with per-category permissions.\n\nAhead on:\n- Payments \u0026 pricing, 17 against 0\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: No public status page or incident history was found for Flex servers or for mcp.count.ly\n\n### Optimizely Experimentation (B)\n\nGood for: An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.\n\nAhead on:\n- Reliability, 73 against 28\n- Transparency \u0026 trust, 75 against 70\n\nWatch for: No price is published. The plans page says every plan is individually packaged and leads to a demo request\n\n\n## Score by category\n\n| Category | Weight | Countly | Optimizely Experimentation | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 28 | 73 | Optimizely Experimentation +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 74 | Countly +1 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 68 | Optimizely Experimentation +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 66 | Optimizely Experimentation +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 17 | 0 | Countly +17 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 78 | Countly +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 75 | Optimizely Experimentation +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.8 · C** | **62.6 · B** | |\n\n## Facts side by side\n\n| Fact | Countly | Optimizely Experimentation |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Countly Ltd | Optimizely |\n| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://exp.mcp.opal.optimizely.com/mcp` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT | Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0 |\n| Tools exposed | 209 | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-09-18 |\n| Terms last updated | 2026-09-25 | no date given |\n| Privacy policy last updated | 2026-09-25 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 28k npm/wk | 460k npm/wk, 86k PyPI/wk |\n\n## Verdicts\n\n**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.\n\n**Optimizely Experimentation.** Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.\n\n## Before you call either\n\n### Countly\n\n1. 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\n2. Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins\n3. Call `apps_list` first. Most tools need `app_id` or an exact `app_name`\n4. Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins\n5. 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\n\n### Optimizely Experimentation\n\n1. Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again\n2. Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs\n3. Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data\n4. Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript\n5. Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints\n\n## Questions\n\n### Which is better for AI agents, Countly or Optimizely Experimentation?\n\nOptimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing.\n\n### Do Countly and Optimizely Experimentation need an API key?\n\nCountly needs an API key. Optimizely Experimentation takes an API key or an OAuth sign-in.\n\n### Can an agent call Countly and Optimizely Experimentation without installing anything?\n\nYes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Optimizely Experimentation at https://exp.mcp.opal.optimizely.com/mcp.\n\n### Are Countly and Optimizely Experimentation open source?\n\nCountly is open source (Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT). No open-source release is listed for Optimizely Experimentation.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/countly-vs-optimizely.json, and with the fewest tokens: https://www.anchorterminal.com/compare/countly-vs-optimizely.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"countly\", \"b\": \"optimizely\"}`. From a terminal: `anchor compare countly optimizely`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/countly.json and https://www.anchorterminal.com/api/v1/tools/optimizely.json\n\n## Other comparisons with Countly or Optimizely Experimentation\n\n- [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md)\n- [Amplitude vs Optimizely Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-optimizely.md)\n- [Countly vs Fullstory](https://www.anchorterminal.com/compare/countly-vs-fullstory.md)\n- [Countly vs GrowthBook](https://www.anchorterminal.com/compare/countly-vs-growthbook.md)\n- [Countly vs Mixpanel](https://www.anchorterminal.com/compare/countly-vs-mixpanel.md)\n- [Countly vs Pendo](https://www.anchorterminal.com/compare/countly-vs-pendo.md)\n- [Countly vs PostHog](https://www.anchorterminal.com/compare/countly-vs-posthog.md)\n- [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md)\n- [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md)\n- [Fullstory vs Optimizely Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-optimizely.md)\n- [Mixpanel vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.md)\n- [Optimizely Experimentation vs Pendo](https://www.anchorterminal.com/compare/optimizely-vs-pendo.md)\n- [Optimizely Experimentation vs Woopra](https://www.anchorterminal.com/compare/optimizely-vs-woopra.md)\n- [Countly vs Heap](https://www.anchorterminal.com/compare/countly-vs-heap.md)\n- [GrowthBook vs Optimizely Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-optimizely.md)\n- [Optimizely Experimentation vs PostHog](https://www.anchorterminal.com/compare/optimizely-vs-posthog.md)\n- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)\n- [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md)\n- [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Countly vs Optimizely Experimentation", "url": "" } ], "description": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Countly's 54.8 (C), and leads in 4 of 7 scored categories. Countly leads on payments \u0026 pricing. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Countly C 54.8", "Optimizely Experimentation B 62.6", "scores" ], "h1": "Countly vs Optimizely Experimentation", "image": "https://www.anchorterminal.com/assets/og/compare-countly-vs-optimizely.png", "path": "/compare/countly-vs-optimizely", "published": "2026-10-01", "section": "tools", "title": "Countly vs Optimizely Experimentation for AI agents, C 54.8 vs B 62.6", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/countly-vs-optimizely" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }