# Basedash MCP vs ClicData MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-clicdata-mcp.md (~4,600 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-clicdata-mcp.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-clicdata-mcp
- 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 ClicData MCP's 33.8 (F), and leads in every scored category. Both do analytics queries.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- ClicData MCP: F 33.8, rank #1181 of 1266 · https://www.anchorterminal.com/tools/clicdata-mcp.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 25; Schema & documentation, 57 against 12; Agent ergonomics, 55 against 24; Payments & pricing, 32 against 20; Maintenance & community, 75 against 35.
- ClicData MCP, good for Companies already on ClicData that want Claude or ChatGPT to answer questions from their own governed warehouse and show charts, without writing SQL.

| Category | Basedash MCP | ClicData MCP |
| --- | --- | --- |
| Reliability (16%) | 70 | 25 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 12 |
| Agent ergonomics (13%) | 55 | 24 |
| Security & auth (14%) | 68 | 64 |
| Payments & pricing (10%) | 32 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 35 |
| Transparency & trust (7%) | 74 | 71 |

| Fact (where they differ) | Basedash MCP | ClicData MCP |
| --- | --- | --- |
| Vendor | BaseDash Inc. | ClicData SAS |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://api.clicdata.com/mcp/` |
| 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 | Proprietary hosted service under ClicData's Terms of Service (effective 10 April 2025). No source is public |
| Tools exposed | 10 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-10-12 |
| Terms last updated | 2026-10-14 | 2025-04-10 |
| Privacy policy last updated | 2026-06-01 | 2025-04-10 |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

Why the edge:
- Reliability, Basedash MCP +45: 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.); ClicData MCP 25 (Graded with the hosted lines, on the remote MCP server. ClicData has a status page at status.clicdata.com on UptimeRobot, but its components and history load from /api/, which its robots.txt disallows, so they weren't read. The status page on www.clicdata.com names Core Services, Web Application and API, not the MCP server. Judgement call, 10 of 20 for a page whose components couldn't be confirmed. No readable incident history (5). No rate limit with numbers was found on the MCP, pricing or plan comparison pages or in the terms; the help articles couldn't be read (0). No 429, Retry-After or backoff guidance found (0). The terms publish a 99.5 per cent uptime target and service credits for paid subscriptions of 10, 25 and 50 per cent below 98.5, 97 and 95 per cent (10). The MCP page calls access early access rolling out to customers first, so not generally available (0).)
- Schema & documentation, Basedash MCP +45: 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.); ClicData MCP 12 (`initialize` and `tools/list` answered 401 without a token, and no public tool manifest or source was found, so typed inputs on the tools are unread. The OAuth protected-resource and authorisation server metadata are machine-readable but describe sign-in, not tools (2 of 25). llms.txt answers 404, and the help articles on the server (mcp-server, connect-mcp-server, api-mcp, custom-mcp-url) draw their text by script whose files answered 502, so nothing for agents was read (0 of 10). The MCP page states the purpose in four areas (questions in plain words, analysis from the warehouse, inline charts, dashboards in the conversation), and the five read scopes name what can be reached, but not per tool (3 of 20). Typed inputs unread (0). One example question on the MCP page and a demonstration video; the 401 has an empty body and a `WWW-Authenticate` header (2 of 15). ClicData versions its platform (app 2026.4.204.0, dated 12 October 2026) and lists dated release notes in the help centre's sitemap, whose text couldn't be read, so no MCP changelog was confirmed (5 of 15).)
- Maintenance & community, Basedash MCP +40: 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.); ClicData MCP 35 (Read as a closed hosted service. The public app configuration gives version 2026.4.204.0 dated 12 October 2026, and the help centre's sitemap dates the custom-mcp-url FAQ 26 October 2026, both within 30 days (30). The release notes 2026-3 and 2026-4 are dated 8 and 14 September 2026 in the sitemap, but their text couldn't be read, so three dated changes in 90 days weren't confirmed (0). Support by email, a ticket portal and phone on some plans, with no guaranteed response time without a support agreement, untested; release notes exist but weren't read (5 of 25). Not in the official MCP registry (a search for clicdata returned no servers) and no official SDK (0). No packages to judge (0). The server has been described on ClicData's site since September 2026 by the sitemap dates.)
- Agent ergonomics, Basedash MCP +31: 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.); ClicData MCP 24 (Graded on the MCP server. The tool count and definition sizes are unknown. Five read scopes suggest a small surface, unconfirmed (10 of 25). No pagination, filters or size controls could be confirmed (0). The 401 names resource metadata, but on a host that answered 403, and no error codes for tool calls were found (2 of 20). Every scope is a read scope, so retries are safe by design; readOnlyHint and destructiveHint couldn't be checked (10 of 20). Connecting is one URL and an OAuth sign-in, but no dynamic client registration endpoint is listed, so a client may need its own registered client ID, and there's no SDK (2 of 15).)
- Payments & pricing, Basedash MCP +12: 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.); ClicData MCP 20 (No x402, MPP or L402 (0). Plan prices are public in the pricing page's source ($290, $520 and $835 a month, or $3,180, $5,700 and $9,120 a year), with nothing per MCP call and AI credits per plan whose use by MCP isn't stated (10). The terms and the roadmap page name a 15-day trial with no card, but the MCP page calls access early access for customers, and the AI page says AI tools are on paid plans, so whether the trial reaches the server is unconfirmed. Judgement call, 10 of 20. A person signs up in a browser and completes the OAuth sign-in, and there is no dynamic client registration (0).)