# Basedash MCP vs Countly (slim)

> Basedash MCP scores 61.1 (C) to Countly's 54.9 (C) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-countly.md (~5,500 tokens) · this version ~3,430 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-countly.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-countly
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Basedash MCP scores 61.1 (C) on agent readiness against Countly's 54.9 (C), and leads in 4 of 7 scored categories. Countly leads on schema & documentation, agent ergonomics and maintenance & community. Both do analytics queries.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- Countly: C 54.9, rank #813 of 1266 · https://www.anchorterminal.com/tools/countly.min.md
- Basedash MCP, good for Teams already on Basedash, or choosing a BI tool, that want an agent to answer questions from governed metrics and build dashboards under each person's access. Ahead on Reliability, 70 against 28; Security & auth, 68 against 63; Payments & pricing, 32 against 17. Also Free to start without a card.
- Countly, good 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. Ahead on Schema & documentation, 75 against 57; Agent ergonomics, 66 against 55; Maintenance & community, 80 against 75. Also Runs on your own machine; Open source.

| Category | Basedash MCP | Countly |
| --- | --- | --- |
| Reliability (16%) | 70 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 75 |
| Agent ergonomics (13%) | 55 | 66 |
| Security & auth (14%) | 68 | 63 |
| Payments & pricing (10%) | 32 | 17 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 80 |
| Transparency & trust (7%) | 74 | 71 |

| Fact (where they differ) | Basedash MCP | Countly |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | BaseDash Inc. | Countly Ltd |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://mcp.count.ly/mcp` |
| Transports | Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Auth | OAuth | API key |
| Licence | Proprietary hosted service under Basedash's Terms of Service (updated 14 October 2026), governed by Delaware law. The Basedash/mcp repository holds only a README and server.json, with no licence file and no server code | 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 |
| Tools exposed | 10 | 209 |
| Read-only variant documented | no | yes |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-10-07 |
| Terms last updated | 2026-10-14 | 2026-09-25 |
| Privacy policy last updated | 2026-06-01 | 2026-09-25 |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 28k npm/wk |

Why the edge:
- Reliability, Basedash MCP +42: Basedash MCP 70 (Graded with the hosted lines, on the remote server at charts.basedash.com. Instatus status page at status.basedash.com with one component, App, and notices back to April 2021; the MCP server isn't a separate component (20). No notices since 14 March 2026 and 100.0 per cent shown for September, October and November 2026, so the last 90 days are clean (30). No rate limit is published for the MCP server. The public API allows 60 requests a minute by default, per the changelog of 7 August 2026, which we count in part since the MCP surface may differ (5 of 15). The OpenAPI file documents a 429 with `RateLimitExceeded` and `retryAfterMs` on all 91 operations and an `Idempotency-Key` on starting a chat, but nothing is documented for 429s or retries over MCP (5 of 15). No uptime SLA; the about page names priority support SLAs on Enterprise only (0). The server isn't labelled beta or preview and is on both paid plans (10). Total 70.); Countly 28 (Graded on the hosted lines, for a Countly Flex server reached through its HTTP API and the official MCP server. No status page was found on countly.com, the Flex page or the docs, and status.countly.com did not resolve (0). With no page there is no readable incident history (5). The MCP server's HTTP endpoint is limited to 120 requests a minute per IP, but the Countly server's own `api_rate_limit_requests` setting ships at 0 (off), and the Flex terms reserve usage limits without numbers (8 of 15). No 429 or retry guidance and no idempotency keys were found in the API reference (0). The pricing page lists an SLA as optional on Flex and included in Enterprise, with no SLA text published (5 of 10). The API and MCP server 1.7.0 are generally available (10).)
- Schema & documentation, Countly +18: Basedash MCP 57 (The served tool definitions can be read only in a signed-in MCP session, which this run doesn't open. The docs and feature page list all ten tools with their inputs, which are required or optional, their scopes, what each returns and which one is annotated destructive, and the REST API counterpart has a public OpenAPI 3.1.0 file (50 paths, 91 operations). Judgement call, 10 of 25 for documented inputs without published JSON Schemas. llms.txt and Markdown copies of every docs page are served (10). Each tool's purpose is stated, with when to use MCP over the REST API and `get_data_sources` described as the call to make before asking; when not to call a build tool isn't stated (12 of 20). Inputs are a free-text `question` or `instructions` plus ids, with no enums or constraints documented (5 of 15). Example questions on the feature page and the launch posts, and troubleshooting for Forbidden or not-a-member, usage blocked and not-found errors, but no error payload shapes (10 of 15). A public dated changelog with MCP entries on 5 June, 14 August, 4 and 25 September and 7 and 9 October 2026, and a server.json version (1.1.0), but the registry entry is still 1.0.0 and the llms.txt of 7 October 2026 still describes two tools (10 of 15). Total 57.); Countly 75 (No OpenAPI document was found on api.count.ly or in Countly/countly-server. Every MCP tool has a typed JSON Schema input (18 of 25). countly.com/llms.txt indexes 366 help articles and points automated clients to the help centre's JSON API, while api.count.ly has no llms.txt and article pages answered 403 to our reader (8). MCP tool descriptions name the endpoint, the plugin required and the tool to use instead, and API pages state permissions and behaviour (16). 82 enums across the tool sources, but the HTTP API takes JSON arrays and objects as query-string values (9). API pages carry request examples, response fields and error responses, as plain message strings (11). The API reference is versioned 24.05, 25.03 and 26.01, and the server and MCP server keep public changelogs (13).)
- Payments & pricing, Basedash MCP +15: Basedash MCP 32 (No x402, MPP or L402 (0). Plan prices are public, $1,000 a month for Startup with $1,000 of AI credits included, but the cost of an MCP question in AI usage isn't published (10). A 14-day trial needs no card, includes up to $250 of AI usage and has the MCP server, since it's on every plan and the trial has full feature access (20). A person signs up in a browser and approves the OAuth connection; clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 32.); Countly 17 (No x402, MPP or L402 (0). The pricing page gives only a starting price for Flex, $175 a month, priced on monthly active users and data points, with tier prices shown during signup and Enterprise on quotation (7 of 20). The 14-day Flex trial needs a credit card. Countly Lite is free to self-host with no card, without funnels, retention, cohorts or Drill, so half credit (10). A person signs up in a browser, creates a server and makes a token in the dashboard (0).)
- Agent ergonomics, Countly +11: Basedash MCP 55 (Ten tools, grouped by the vendor into ask, build and look up. Their definitions' size couldn't be measured without a session, so 20 of 25 rather than 25. No paging, filters or size controls are documented for `list_dashboards` or `list_charts`; `ask_question` returns tables as CSV files rather than inline rows, and the client can page through the tool list, per the changelog of 14 August 2026 (5 of 20). The troubleshooting section names Forbidden or not-a-member, usage blocked and not-found or archived artifacts with what to do, and `ask_question` and `get_data_sources` return typed structured payloads since 5 June 2026 (10 of 20). `edit_dashboard` is annotated destructive and a failed dashboard or chart build is cleaned up, but no readOnlyHint on the look-up tools or idempotency on the create tools is documented (10 of 20). One or two required inputs per tool and nothing to install; the only official SDK is the React embedding SDK, which isn't for MCP (10 of 15). Total 55.); Countly 66 (The MCP README counts 209 tools in 43 categories, far past 30 (5). Add back 8 because the server hides tools the edition, enabled plugins or user's permissions cannot run, and `COUNTLY_TOOLS_*` settings switch categories off (13). List endpoints take `iDisplayStart` and `iDisplayLength`, and MCP list tools take `skip`, `limit` and `search` (15). API errors are `{"result": "message"}` strings with HTTP status codes and no error codes. The MCP server returns failures as `isError` results that name the missing plugin or permission (12). MCP tools carry readOnlyHint, destructiveHint and idempotentHint since 1.7.0. No idempotency keys on API writes (14). MCP tools accept `app_name` in place of `app_id` and set defaults. The SDKs cover data collection, not the read API (12).)
- Security & auth, Basedash MCP +5: Basedash MCP 68 (OAuth on Basedash's own authorisation server, with the authorisation code grant and PKCE S256 only, refresh tokens, public clients, dynamic client registration, client ID metadata documents and a revocation endpoint. Three scopes separate asking, reading dashboards and writing them, and the token goes in the header only (30). Building needs `mcp:dashboards:write` on top of `mcp:chat:ask`, `edit_dashboard` is annotated destructive, no tool deletes, and Basedash's AI can change database rows only from the web app with an approval card, per the accuracy page. No server-side confirmation is documented for dashboard edits, and the consent screen on the feature page shows all three scopes together (15 of 20). Answers are drawn from connected company data, which can include text written by outsiders (tickets, CRM records synced by Fivetran), and no prompt-injection guidance was found. Hidden columns and row-level security narrow what reaches the model (5 of 15). The MCP server is a named audit log source, but AI tool calls and queries are recorded on Enterprise only; AI usage per person and feature is shown on every plan (10 of 15). No security.txt on www or charts, and no bug bounty or disclosure policy found. Basedash says it holds SOC 2 Type II, with the report under NDA, and runs third-party penetration tests (8 of 20). Total 68.); Countly 63 (Auth tokens are scoped to apps and endpoint patterns, expire after a set lifetime, are revocable and carry create, read, update and delete permissions since 25.03.54. The dashboard `api_key` has its user's full access (26 of 30). Less 10 because `api_key` and `auth_token` are documented as query-string parameters, with the `countly-token` header as the recommended alternative (16). MCP read-only mode and per-category CRUD levels, bounded by the token's permissions. No confirmation step for destructive tools (16). Tools return event names, user properties and crash data written by end users, and no prompt-injection guidance was found. The docs suggest a self-hosted model for sensitive data (3). A system logs API records dashboard actions, and the security FAQ cites more than 30 log types (12). No security.txt. SECURITY.md gives a disclosure address and a bounty for medium severity and above, security fixes are listed in the public changelog, and the site claims ISO 27001, 27017, 27018 and SOC 2 Type II without public reports (16).)
- Maintenance & community, Countly +5: Basedash MCP 75 (Read as a closed hosted service. The changelog's latest entry is 30 October 2026, and the latest MCP-specific entries are 7 and 9 October 2026 (chart placement on a dashboard tab, restyled MCP sign-in pages), all within 30 days (30). Weekly dated changelog entries, with MCP changes on 14 August, 4 and 25 September and 7 and 9 October 2026 (20). Support by email and by Slack on paid plans, with response times not tested (10 of 15). Active in the official MCP registry as com.basedash/mcp under the reverse-DNS namespace for basedash.com, though its description still names two tools (15). No package to judge; the registry entry lags the repository's server.json (0 of 10). Total 75.); Countly 80 (`countly-mcp-server` 1.7.0 was published on 7 October 2026 and server tag 25.03.54 on 22 September 2026 (30). Four server tags (25.03.49, .50, .51, .54) and MCP 1.5.0 and 1.7.0 since 10 July 2026 (20). 821 commits on the server's default branch since 10 July 2026, a Discord community and a support portal. We could not read issue response times because the GitHub API refused us (12 of 25). SDK docs are at 26.1.x for Android, iOS, Web and Flutter, while the NodeJS SDK docs are at 24.10.x. The MCP server is not in the official MCP registry (10 of 15). CI, CodeQL and Docker workflows on the server, and test, nightly end-to-end and CodeQL workflows on the MCP server (8).)