Head to head · Docs and wikis · October 2026 research run

DataHub vs Guru

DataHub scores 55 (C) on agent readiness against Guru's 48.8 (D), and leads in every scored category. Both do docs and wikis.

Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons

Which one, for what

DataHub C

Best 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

  • Reliability, 58 against 53
  • Schema & documentation, 81 against 58
  • Agent ergonomics, 78 against 48
  • Security & auth, 65 against 57
  • Payments & pricing, 15 against 0
  • Maintenance & community, 77 against 65

Also in its favour

  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar

Guru D

Best for Companies already running Guru that want agents to answer from verified cards with each user's permissions, and to draft card changes.

Also in its favour

  • No incidents deducted, where DataHub loses 8 points for them

Watch for

No public prices, plans or trial, and the pricing page sends everyone to sales

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics DataHub +30

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).

Guru 48

We couldn't count the MCP tools without signing in. The developer page lists five, the help centre's six groups (among them reporting queries and image uploads) suggest more, and no toolsets or read-only subset are documented for MCP. Guru's own CLI pages say the MCP server loads its full tool schema on every turn (15). The REST API pages with Link headers and paging tokens, returns at most 50 cards a page, and filters and sorts cards. MCP paging is unknown (14 of 20). Status codes per operation, but no error body format documented (8 of 20). The help centre says the MCP server can create cards, move cards and folders, archive cards, apply draft edits and change collaborators, and we found no annotations, confirmation step or idempotency guidance. Card changes and uploaded images land in drafts (5 of 20). One URL with OAuth for pre-approved clients. The only official SDK is Python, at 0.1.0 and installed from GitHub rather than PyPI (6 of 15).

Schema & documentation DataHub +23

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 still stops at 0.5.3 with everything since under Unreleased, six releases behind (10 of 15). Since 0.8.0 tools publish single-type schemas instead of multi-type unions. 25+10+15+9+12+10 = 81.

Guru 58

Each API reference page on developer.getguru.com shows its operation's OpenAPI 3.1 definition in the page's Markdown copy (Guru API v1, with enums and defaults), and Guru's Python SDK repository carries a matching Swagger 2.0 file. The MCP server is closed and its tool schemas aren't published outside a signed-in session (18). llms.txt at developer.getguru.com and a Markdown copy of each docs page (10). The developer site describes five MCP tools in one line each with no when-not-to-use, while the help centre article (updated 21 October 2026) describes six groups of tools without names and says the names depend on the client (6 of 20). The REST spec has enums for query type, sort field and sort order and a 50-result default, with free strings elsewhere. MCP inputs weren't visible to us (8 of 15). One curl example in the quick start, status codes per operation in the spec, and no error catalogue (8 of 15). A v1 path, and a dated product changelog at feedback.getguru.com that replaced the help centre's release notes and includes MCP changes. The developer changelog now returns 404 and we found no API version policy, so the earlier partial is carried (8 of 15).

Payments & pricing DataHub +15

DataHub 15

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Guru 0

No x402, MPP or L402 (0). The pricing page shows no prices and sends every visitor to sales (0). No free plan or trial on the pricing or home pages. A blog post from 2020, updated in 2023, describes a free Starter plan for 10 users and points to a pricing page that no longer lists it (0). A person has to buy through sales, then sign in and approve OAuth or create a token (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Maintenance & community DataHub +12

DataHub 77

DataHub v1.6.0.4 (LTS) tagged on 28 October 2026 and mcp-server-datahub v0.8.0 on 21 October, 7 and 14 days before this check (30). Since 6 August, DataHub v1.7.0.1 (3 September), v1.6.0.3 (25 September), v1.8.0 (12 October) and v1.6.0.4, plus MCP server v0.7.0 (13 August), v0.7.1 (15 September) and v0.8.0, dated by tag commit, with release candidates left out (20). Per the 3 October check, the MCP server had 12 open issues, the oldest from December 2025, and DataHub 521 open issues and 781 open pull requests with a stale-issue workflow; reply times couldn't be read then or on 4 November. Community pull requests (#184, #185, #198, #208, #210, #238, #271) were merged in October (12 of 25). Not in the official MCP registry on 4 November, where a search returns third-party DataHub servers (txn2's mcp-datahub among them). Official Python and Java SDKs are current (7 of 15). CI on every push, and Dependabot pull requests merged on 29 October (8 of 10). 30+20+12+7+8 = 77.

Guru 65

Guru's product changelog moved from the help centre to feedback.getguru.com. Its newest dated entry that changes what API and MCP callers get is 30 October 2026, when Knowledge Agents, which the MCP server's question tool calls, began returning the records behind analytical answers (30). Dated entries in the 90 days from 7 August that change what API and MCP callers get are MCP image uploads (20 October), DLP masking extended to MCP requests (26 October) and Knowledge Agents returning the records behind analytical answers (30 October), the datasets the help centre's MCP reporting tools query (20). Older entries load only by script and weren't read. A closed service with a dated public changelog, a help centre and a community site. Support response wasn't tested, and the MCP repository holds only a README and server.json (10 of 15). The earlier official MCP registry reading came from the registry's JSON API, which this checklist no longer accepts, so it's struck, and the vendor's server.json naming com.getguru/mcp-server is a claim. The only SDK, Python 0.1.0, has no release and installs from GitHub, and the Guru CLI's npm page couldn't be read (0). The Python SDK runs CircleCI and takes Dependabot updates, but it isn't published to PyPI (5 of 10).

Security & auth DataHub +8

DataHub 65

Personal access tokens per user, gated by a privilege, expiring after 1 hour to 365 days with never-expiring tokens off by default, and revocable. HTTP mode takes each user's own bearer token in the header and rejects ?access_token=, and Cloud's managed endpoint uses OAuth with dynamic client registration. Tokens have no scopes of their own and carry the user's full privileges (26 of 30). Write tools are off by default, save_document may only update documents the agent created unless the operator changes that, DataHub policies and views narrow what a user sees, but there's no confirmation step on writes (14 of 20). Tools return descriptions, documents and SQL that people and source systems wrote. The server strips HTML and base64 embeds but publishes no injection guidance (4 of 15). DataHub records the acting user on metadata changes and the docs say per-user tokens keep audit attribution per user, and we found no per-call MCP log for the operator (8 of 15). SECURITY.md with security@datahub.com and a PGP key (re-read on 4 November), 10 GitHub advisories with four in the last twelve months per the 3 October check, SOC 2 claimed for Cloud and third-party penetration tests on the security page. No bug bounty, and datahub.com/.well-known/security.txt still answers 404 (13 of 20). 26+14+4+8+13 = 65.

Guru 57

OAuth for MCP clients Guru has pre-approved, while other clients need Guru Support to allowlist them, and no MCP scopes are documented. OAuth2 clients for the REST API, enabled through Guru Support, take read:* for read-only or *:* for read and write. The REST API takes basic auth with an email and a user token that reads and writes with the user's rights, or a collection token that's read-only and limited to one collection, and the MCP server takes Bearer email:token. No secret in a query string (22 of 30). Collection tokens and read:* OAuth2 clients give read-only access, and every call keeps the user's Guru permissions. MCP actions include archive and move with no documented confirmation, though card edits through MCP land as drafts (10 of 20). Tools return cards and connected-source documents written by people, and we found no prompt-injection guidance. The security page says DLP masking redacts PII, PHI and financial data, and since 26 October 2026 it also covers MCP requests (4 of 15). The MCP docs say every interaction is logged in Guru's AI Agent Center, and the pricing page lists centralised audit logs. We found no per-call log for REST API calls (10 of 15). The security page lists a SOC 2 Type II report under NDA, PCI SAQ A-EP, Data Privacy Framework certification and penetration tests at least twice a year. No security.txt (404), disclosure policy or bug bounty found (11 of 20).

Reliability DataHub +5

DataHub 58

Read with the local-software lines, since what an agent runs is mcp-server-datahub against a DataHub instance its owner hosts (the same server works against DataHub Cloud). PyPI and Docker packages, Python 3.11+ stated, but no minimum DataHub version is published. The server hides tools a too-old GMS can't run, and issue #64 asking for the minimum has been open since December 2025 (15 of 20). ci.yml runs lint, unit tests, Docker checks and integration tests against DataHub quickstarts on every push and pull request (re-read in a clone on 4 November). The last three runs on main passed per the 3 October check, but main has moved on since (v0.8.0 on 21 October, commits to 3 November) and GitHub's pages answer 403, so the pass state is unread (15, this run's reading for public CI that runs the tests with the result unread, as node-red). Per the 3 October check, 12 open issues, four of them bug reports (#110, #118, #131, #139) open since April to July, and we couldn't see replies. DataHub itself has 521 open issues and 781 open pull requests (15 of 25). The changelog follows Keep a Changelog and marks breaking changes, but stops at 0.5.3 while tags reach 0.8.0 (21 October 2026), a breaking HTTP change sits under Unreleased, and 0.5.3 replaced the filters object with a filter string while calling it not breaking. DataHub's Updating DataHub page has a Breaking Changes section for every release (8 of 15). DataHub is at 1.8 with an LTS line, but the MCP server agents load is 0.8.0 (5 of 15). DataHub Cloud's status page, status.datahub.com, moved to incident.io and its feed lists no incident on 4 November; it isn't scored on these lines. 15+15+15+8+5 = 58.

Guru 53

Read as a hosted service. Atlassian Statuspage at status.getguru.com with components for the web app, extension, Slack bot, API, analytics, message delivery and infrastructure, but no MCP component (20). One incident in the 90 days from 7 August 2026. On 7 August intermittent connectivity made new MCP registrations fail while existing ones kept working, resolved 17 minutes after the first update, a partial incident read as minor (20 of 30). The 24 July network incident is now outside the window. No rate limits with numbers in the developer docs or the MCP help article, and the terms leave AI usage limits to each order (0). No 429 or backoff guidance in the docs. The Python SDK maps 429 to RateLimitError without reading Retry-After, an earlier partial carried (3 of 15). The terms sell the service as is and as available with no uptime commitment, and we found no SLA (0). The developer docs carry no beta or preview label on the MCP server or the REST API (10).

Score by category

CategoryWeightDataHubGuruEdge
Reliability16%5853DataHub +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8158DataHub +23
Agent ergonomics13%7848DataHub +30
Security & auth14%6557DataHub +8
Payments & pricing10%150DataHub +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7765DataHub +12
Transparency & trust7%6461DataHub +3
Negative events≤15-80
TotalC 55/100D 48.8/100

Facts side by side

FactDataHubGuru
KindPlatformHTTP API
VendorAcryl Data, Inc. (DataHub)Guru Technologies, Inc.
Hosted endpointhttps://mcp.datahub.com/mcphttps://mcp.api.getguru.com/mcp
Transportsstdio, HTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceApache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closedProprietary hosted service under Guru's terms of service. The Python SDK (guruhq/guru-py-sdk) is MIT, and the MCP server's public repository holds only a README and server.json
Tools exposed8none
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrynot listedcom.getguru/mcp-server
Last release2026-10-282026-10-30
Terms last updated2020-05-282026-03-25
Privacy policy last updated2026-08-112025-08-19
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity13k stars, 1.6M PyPI/wknone
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate DataHub higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

DataHub

Apache-2.0 platform and MCP server, run with uvx mcp-server-datahub@latest or the acryldata/mcp-server-datahub Docker image against DataHub Core or DataHub Cloud. The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar.

Guru

Guru's hosted MCP server and v1 REST API keep each user's Guru permissions, collection tokens and read:* OAuth2 clients give read-only access, and MCP interactions are logged in the AI Agent Center. There are no public prices, plans or trial, no published rate limits or 429 guidance, and MCP tool schemas are visible only after signing in.

Before you call either

DataHub

  1. Start keyword queries with /q and pass filters as one string, such as entity_type = dataset AND platform = snowflake
  2. Call search with num_results=0 first to get the tags, glossary terms, platforms and domains in use
  3. Page with offset. num_results is capped at 50
  4. Expect no write tools unless the operator set TOOLS_IS_MUTATION_ENABLED=true, and create tags and terms before add_tags or add_terms refers to them
  5. Use https://mcp.datahub.com/mcp with OAuth only on DataHub Cloud v1.0.2 or later. DataHub Core needs the local server and a personal access token

Guru

  1. Ask the person for a Guru account. There's no trial or keyless route, and OAuth needs a pre-approved client
  2. Send Authorization: Bearer email:token to the MCP server when OAuth isn't available, and basic auth to https://api.getguru.com/api/v1/
  3. Use a collection token or a read:* OAuth2 client for read-only work. User tokens write with the user's full rights
  4. Follow the Link header to page REST search results. Each page holds at most 50 cards
  5. Confirm with a person before archiving or moving cards. Guru documents no confirmation step

Questions

Which is better for AI agents, DataHub or Guru?

DataHub scores 55 (C) on agent readiness against Guru's 48.8 (D), and leads in every scored category.

Can an agent call DataHub and Guru without installing anything?

Yes. DataHub has a hosted endpoint at https://mcp.datahub.com/mcp and Guru at https://mcp.api.getguru.com/mcp.

Are DataHub and Guru open source?

DataHub is open source (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). No open-source release is listed for Guru.

Other comparisons with DataHub or Guru

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.