# Basedash MCP vs DataHub (slim)

> Basedash MCP scores 61.1 (C) to DataHub's 59.4 (C) for data catalogues. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-datahub.md (~4,450 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-datahub.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-datahub
- 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 DataHub's 59.4 (C), and leads in 4 of 7 scored categories. DataHub leads on schema & documentation and agent ergonomics. Both do data catalogues.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- DataHub: C 59.4, rank #601 of 1266 · https://www.anchorterminal.com/tools/datahub.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 Payments & pricing, 32 against 10; Transparency & trust, 74 against 64. Also Free to start without a card; No incidents deducted, where DataHub loses 5 points for them.
- DataHub, good for Teams already running DataHub who want agents to find tables, trace column lineage, read the SQL people run and see owners and glossary terms before touching data. Ahead on Schema & documentation, 81 against 57; Agent ergonomics, 78 against 55. Also Runs on your own machine; Open source.

| Category | Basedash MCP | DataHub |
| --- | --- | --- |
| Reliability (16%) | 70 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 81 |
| Agent ergonomics (13%) | 55 | 78 |
| Security & auth (14%) | 68 | 65 |
| Payments & pricing (10%) | 32 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 77 |
| Transparency & trust (7%) | 74 | 64 |

| Fact (where they differ) | Basedash MCP | DataHub |
| --- | --- | --- |
| Kind | MCP server | Platform |
| Vendor | BaseDash Inc. | Acryl Data, Inc. (DataHub) |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://mcp.datahub.com/mcp` |
| Transports | Streamable HTTP | stdio, HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| 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 | Apache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closed |
| Tools exposed | 10 | 8 |
| Read-only variant documented | no | yes |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-09-25 |
| Terms last updated | 2026-10-14 | 2020-05-28 |
| Privacy policy last updated | 2026-06-01 | 2026-08-11 |
| Popularity | none | 13k stars, 1.6M PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Schema & documentation, DataHub +24: 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.); DataHub 81 (Every tool has a JSON Schema generated from Python type hints, and each instance serves an OpenAPI spec and GraphQL (25). llms.txt at docs.datahub.com (10). Descriptions say what each tool is for and when to reach for another (list_schema_fields "when search results truncate fields"), with a full filter grammar. The docs page lists tools the open-source server doesn't register and annotations it doesn't set (15 of 20). Literal enums for direction, sort order, query source and description operation, but filters are one free string with a grammar in prose, the 50-result cap lives only in prose, and properties carry no descriptions in the schema (9 of 15). Worked examples in every description and errors that say what to do next ("use the search tool ... or create the tags first"), but no error catalogue (12 of 15). Tags and PyPI versions, and DataHub's release notes, but the MCP changelog is five releases behind (10 of 15).)
- Agent ergonomics, DataHub +23: 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.); DataHub 78 (Eight tools by default, within the ten the rubric names, but they carry about 26,000 characters of descriptions (roughly 6,500 tokens), because search and get_lineage each embed the same 3,063-character filter grammar. Write, user and data-quality tools sit behind environment flags, which work as toolsets (18 of 25). `offset` and `num_results` (max 50), facet-only search, keyword filters on schema fields, lineage hops and an 80,000-token response budget that truncates long descriptions (20). Errors come back as tool errors naming the bad input and the next step, without codes (15 of 20). The 10 read tools carry readOnlyHint, the 12 write tools carry no annotations at all, and there are no idempotency keys (10 of 20). Every read tool runs on defaults (`query="*"`), and DataHub ships Python and Java SDKs (15).)
- Payments & pricing, Basedash MCP +22: 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.); DataHub 10 (Scored on the paid option, as the self-hosted rule asks for open-source software sold beside a hosted version (DataHub Cloud). No x402, MPP or L402 (0). Cloud pricing is contact sales and datahub.com/pricing/ returns 404 (0). DataHub Core is free to self-host with no card, but Cloud has no free tier or trial we could find (10 of 20). A person deploys DataHub and creates a token in the UI, or signs a Cloud contract (0).)
- Transparency & trust, Basedash MCP +10: Basedash MCP 74 (The editorial half. A closed service under dated terms (14 October 2026) naming Basedash Inc. and Delaware law, with 30 days' notice of material adverse changes to the agreement (15). The privacy policy (1 June 2026), the data processing addendum (6 October 2026) and the security docs agree that customer data isn't used for training by Basedash or its AI providers, and the security docs say table and column names and query results go to AI providers. Retention periods differ by document. The privacy policy says a reasonable period, the terms 60 days after a deletion request, the security docs complete removal on request, and audit events are kept 90 days. Locations differ in wording (San Francisco servers in the security docs, DigitalOcean in the United States in the privacy policy) (18 of 30). No deprecation policy for the MCP server; the REST API is unversioned and breaking changes are communicated in advance when possible, and the dashboard scopes were granted to existing connections without re-authorising (8 of 20). The DPA names ten subprocessors (OpenAI, Sentry, Stripe, DigitalOcean, Anthropic, Amazon Web Services, Microsoft Azure, Fivetran, MotherDuck, Betterstack) in the United States and the Czech Republic (16 of 20). Total 57.); DataHub 64 (DataHub Core and the MCP server are Apache-2.0. DataHub Cloud and its extra MCP tools are closed (27 of 30). The privacy policy of 11 August 2026 excludes paying customers' use of the service, the terms of 28 May 2020 cover the website, and we found no DPA, subprocessor list or Cloud retention statement. The security page names AWS and KMS encryption (6 of 30). Updating DataHub lists Breaking Changes, Deprecations and Potential Downtime for every release, and v1.6.0 has an LTS line, but there's no stated notice period (12 of 20). Telemetry is on by default and documented with an opt-out for the server and the CLI, but the MCP server's per-call events and error text aren't on the telemetry page, the README or the MCP docs (10 of 20).)