Head to head · Data catalogues · October 2026 research run

Atlan vs OpenMetadata

OpenMetadata scores 60.1 (C) on agent readiness against Atlan's 56.2 (C), and leads in 5 of 7 scored categories. Atlan leads on security & auth and transparency & trust. Both do data catalogues.

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

Which one, for what

Atlan C

Best for A company already on Atlan that wants agents to find governed tables, owners, lineage, glossary terms and data quality rules, and to run read-only SQL, under the same permissions people have.

Ahead on

  • Security & auth, 75 against 65
  • Transparency & trust, 70 against 54

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Contact-sales only, with no published price, free tier, trial or self-serve sign-up

OpenMetadata C

Best for Teams running OpenMetadata who want agents to search the catalogue, read lineage and data-quality results, find root causes and create tests or lineage under the user's own permissions.

Ahead on

  • Reliability, 84 against 67
  • Schema & documentation, 85 against 65
  • Agent ergonomics, 85 against 74
  • Payments & pricing, 30 against 0
  • Maintenance & community, 89 against 80

Also in its favour

  • Free to start without a card
  • Open source

Watch for

The 16 default tools take about 50,000 characters of definitions, 12,285 of them for search_metadata alone

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.

Payments & pricing OpenMetadata +30

Atlan 0

Hosted service with nothing to self-host, so the hosted rubric applies. No x402, MPP or L402 (0). No published prices, and atlan.com/pricing is a contact form for sales (0). No free tier, trial or self-serve sign-up found (0). An agent needs a person at a customer company to sign in by OAuth, or an admin to create an API token, after a sales contract (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

OpenMetadata 30

Scored on the paid option, as the self-hosted rule asks for open-source software sold beside a hosted version (Collate). No x402, MPP or L402 (0). The Free plan is published, but Premium, Enterprise and the AI add-on are contact sales (0). Collate Free needs no card and self-hosting is free, though Collate Free leaves MCP out (20). A person signs up in a browser or deploys an instance and creates a token (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Schema & documentation OpenMetadata +20

Atlan 65

We found no public OpenAPI file for the REST API. MCP tools carry JSON Schema by protocol, but the hosted server is closed and lists its tools only after a sign-in, so we couldn't read the schemas (15 of 25). llms.txt at docs.atlan.com with about 180 links and Markdown copies of pages, plus a separate docs MCP server at docs.atlan.com/mcp (10). The tools reference gives each of the 41 tools (2 November 2026) a one-line purpose and an access level, and the atlan-search skill (8,358 characters plus six reference files) says which tool fits which ask and when not to use one, such as sending row values to query_assets rather than search (13 of 20). Input types are unverified on the hosted server, and the deprecated local server took untyped rule dicts for its data quality tools (6 of 15). An error catalogue of 10 coded errors, each with a category and a recovery step, and filter examples in the skill (12 of 15). A product changelog with absolute dates now sits at docs.atlan.com (newest entry 26 October 2026) beside shipped.atlan.com, and pyatlan's HISTORY.md has breaking-change sections per release, but the hosted MCP server has no version or changelog of its own, and the agent-toolkit CHANGELOG stops at 0.3.3 on 17 February 2026 (9 of 15).

OpenMetadata 85

Every MCP tool has a typed JSON Schema in tools.json. The REST API has no public spec, since the openapi.json linked from llms.txt is a template titled OpenAPI Plant Store (22 of 25). llms.txt indexes about 3,100 pages across 2.0.x, 1.13.x and a 2.1.x snapshot (10). Descriptions say when to use each tool, when to use another ("Choose this over semantic_search when the query targets known identifiers") and where answers go silently wrong (19 of 20). Required fields are marked, but few enums, queryFilter takes raw OpenSearch DSL in a string and patch_entity takes a JSON Patch blob (8 of 15). Examples inside the descriptions, and errors as JSON with a message and a status code, but no error catalogue in the docs (12 of 15). Versioned docs for 1.13.x, 2.0.x and a 2.1.x snapshot, and dated release notes for every 2.0.x patch. The registry entry's 21 tools doesn't match the source (14 of 15).

Reliability OpenMetadata +17

Atlan 67

Hosted service, read on the hosted lines and graded on what an agent uses, the hosted MCP server and the REST API. status.atlan.com moved to incident.io, with components for Atlan Services, API, Product and Search and none for MCP or Atlan AI (15 of 20). The 3 October reading came from the old page's /api/v2 JSON, a status data endpoint this run doesn't use, so it is struck. The new page's 90-day uptime chart says "No data for 55 days" and its data starts on 28 September 2026, so 4 August to 27 September is unread. From 28 September it shows two incidents. A small number of instances in Azure UAE North failed with gateway errors on 6 October (about 9 minutes on Product). A GCP power event in europe-west2-b on 20 October marked API, Product and Search as full outage from 08:26 to 12:11 UTC, for the tenants in that zone ("all affected Atlan tenant workloads"). One zone and a share of tenants is partial, as this run read the same 20 October event for Google's listings, so both are minor. With 55 of the 90 days unread and not credited, the line stays at the 3 October award (15 of 30). The REST API is limited to 400 requests a minute per instance, with a one-minute block after a 429. The MCP server's limits are enforced at the Atlan AI gateway with no numbers published (12 of 15). The docs give a backoff schedule from 2 to 32 seconds on 429 and 5xx, a dead-letter queue and request IDs, the MCP error ATLAN-MCP-6001 says to back off and retry, and pyatlan retries 429 and honours Retry-After. No idempotency keys for writes (12 of 15). The customer support article the SaaS agreement cites names 99.5 per cent uptime, with no measurement or credits stated, per the 3 October check (5 of 10). The hosted MCP server carries no beta label and replaced the local one, but the knowledge-file tools are early preview (8 of 10).

OpenMetadata 84

Read with the local-software lines, since the MCP server agents use is part of the OpenMetadata server its owner runs, and Collate's hosted plans include MCP only on Enterprise. Docker images and Compose files per release, a Python ingestion package, and requirements stated (Docker 20.10+, Compose v2.1.1+, 6 GiB, 4 vCPUs) (20). 65 workflows, among them unit tests and integration tests on Postgres with OpenSearch and on MySQL with Elasticsearch, passing on main per the 3 October check, not re-read on 1 November (25). Per the 3 October check, 688 open issues, among them a semantic search bug in search_metadata (#34564) and an unmasked-connection report against the MCP entity tool (#34566), whose fix is on main and in the 2.1.0-rc1 pre-release only. Replies weren't visible then and GitHub's pages refused our reader on 1 November (12 of 25). Release notes carry breaking-change sections, and 2.0.7's notes warn API and SDK users about the connection change before upgrading, but that change came in a patch release, and SECURITY.md still names 1.13.x and 1.12.x as supported (12 of 15). Version 2.0.7 (15).

Transparency & trust Atlan +16

Atlan 70

Closed service under the Atlan SaaS agreement. The SDKs are Apache-2.0 and the agent-toolkit repository is MIT, though its Claude Code plugin manifest says Apache-2.0 (15 of 30). The DPA names three contracting entities by domicile, deletes personal data with written confirmation and notifies breaches within 2 business days. The SaaS agreement returns customer data within 30 days of termination and keeps Atlan AI from training on customer data outside the customer's own instance, and the MCP security page says nothing is cached and no metadata, prompts or outputs train foundation models. The privacy notice itself lives in the JavaScript-only trust centre, and the MCP page's line that the server handles only metadata sits beside a SQL tool that returns rows (18 of 30). The SaaS agreement promises reasonable prior notice of regulatory changes that materially degrade the service, and the local MCP server's deprecation was announced in its README and at runtime, with no end date. We found no deprecation policy for the API or the MCP tools (6 of 20). Processing in the US, EU or APAC region closest to the tenant, and the DPA requires notice before a new subprocessor with 15 days to object, but the subprocessor list sits in the trust centre we couldn't read (10 of 20).

OpenMetadata 54

The platform is Apache-2.0, but the module an agent talks to has a LICENSE file with the Collate Community License 1.0, a source-available licence barring competing hosted services, while its Java headers and the README say Apache-2.0 (15 of 30). Collate's privacy policy (24 August 2022) covers the service, names Stripe and gives no retention period, and the terms (29 August 2022) host data in the United States, take a perpetual licence to contributions and set no deletion timeline. We found no DPA or subprocessor list, and the trust centre refused our reader (8 of 30). Breaking changes in release notes and versioned docs, but no deprecation notice policy and a stale supported-versions table (10 of 20). We found no telemetry to the vendor in the UI, ingestion or service dependencies, and UI web analytics post to the instance's own API, but no page says so either way (18 of 20).

Agent ergonomics OpenMetadata +11

Atlan 74

41 tools on one endpoint on 2 November 2026, across Read, Write and Admin access levels, which puts it in the over-30 band (5). We added 7 back because a tenant can ask for read-only mode, which leaves the read tools, and tool exposure is a per-tenant allowlist, though neither is something an agent or a user can switch on (12 of 25). Search returns 20 results by default and up to 100 per call, or only a count, takes filters for type, certificate, tags, domains, terms and dates, and takes a list of attributes to return. SQL results stop at 100 rows (20). Ten coded errors, each with a category and a recovery step, such as ATLAN-MCP-1006 for a qualifiedName passed where a GUID belongs (17 of 20). Write tools return a preview and wait for approval, and the SQL tool refuses anything but SELECT, WITH, SHOW, DESCRIBE and EXPLAIN. We couldn't see readOnlyHint or destructiveHint on the closed server, and there are no idempotency keys (10 of 20). One URL and an OAuth sign-in with no key for Claude Code, Codex or Cursor, and official SDKs for Python, Java and Go (15).

OpenMetadata 85

16 tools listed on a default deployment, with 13,653 characters of descriptions and 49,602 characters of definitions in all (about 12,400 tokens). The four RDF tools are withheld when RDF is off, which helps but isn't a subset the user picks (15 of 25). limit, offset and a nextCursor since 2.0, fields selection, column windows for wide tables, aggregations, persona search scopes and a response budget that flags truncated and hasMore (20). Errors come back with isError, a JSON message and a status code (400, 403 and so on), and soft errors inside a result are flagged too (18 of 20). All 20 definitions carry readOnlyHint and destructiveHint, with idempotentHint true on two, but there are no idempotency keys for the four write tools (17 of 20). Search and entity reads need few or no required fields, and the repository holds Python and Java SDKs (15).

Security & auth Atlan +10

Atlan 75

OAuth with PKCE per user, so each MCP call runs as that user under the personas, roles and domain policies that govern the Atlan UI, with tokens checked against Keycloak's JWKS. Or an API token as a Bearer header, which runs as one service identity, and tokens with more than one persona are refused. OAuth scopes aren't documented and we didn't check API token expiry. No secret travels in a query string (25 of 30). Read-only mode removes write, admin and lifecycle tools, but only on request to Atlan. The allowlist fails closed, writes preview and wait for approval, and a write needs the user's own edit permission (16 of 20). Tools return asset descriptions, READMEs, knowledge files and up to 100 rows of warehouse data. The security page says prompt-injection and PII guardrails run at the Atlan AI gateway without saying what they do (7 of 15). Every tool call is logged with the tool, client name and version, model, tenant, request ID, duration and status, with arguments redacted, and metadata changes land in the asset's activity history. We didn't confirm a customer can read the call log itself (11 of 15). security.txt valid until 14 January 2027, a disclosure programme with safe harbour and triage within 7 business days that rewards with gift cards or swag at Atlan's discretion, and ISO 27001, ISO 27701, SOC 2 Type II and HIPAA badges on the security page. The trust centre holding the reports renders only with JavaScript, so we couldn't read it (16 of 20).

OpenMetadata 65

OAuth 2.0 with PKCE and dynamic client registration through the instance's SSO, 1-hour access tokens, rotating 7-day refresh tokens and a revocation endpoint, plus personal access tokens with configurable expiry and bot JWTs. Tokens carry the user's or bot's full roles with no scopes of their own (27 of 30). Calls run with the caller's roles and policies, three of the four write tools are marked destructive, but they're always listed, there's no read-only switch and no confirmation step (10 of 20). Tools return descriptions, knowledge pages, SQL that has run and context memories written by people and source systems, and we found no injection guidance (3 of 15). Every MCP call is recorded in the instance database with tool, user, outcome, latency and client, and OAuth operations are logged (12 of 15). SECURITY.md routes reports through GitHub advisories, three advisories are published in 2026, THREAT_MODEL.md and INCIDENT_RESPONSE.md sit in the repository, and Collate claims SOC 2 Type II. No security.txt (re-read on 1 November) or bug bounty, and the supported-versions table is stale. Since 14 October SECURITY.md limits CVEs and advisories to unauthenticated access, so authorisation fixes ship without them (the deduction is in the negative events) (13 of 20).

Score by category

CategoryWeightAtlanOpenMetadataEdge
Reliability16%6784OpenMetadata +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6585OpenMetadata +20
Agent ergonomics13%7485OpenMetadata +11
Security & auth14%7565Atlan +10
Payments & pricing10%030OpenMetadata +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8089OpenMetadata +9
Transparency & trust7%7054Atlan +16
Negative events≤15-6-12
TotalC 56.2/100C 60.1/100

Facts side by side

FactAtlanOpenMetadata
KindPlatformPlatform
VendorAtlanCollate, Inc.
Hosted endpointhttps://mcp.atlan.com/mcpno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Licenceproprietary (hosted service under the Atlan SaaS agreement). The agent-toolkit repository of plugins, skills and the deprecated local MCP server is MIT, and the Python, Java and Go SDKs are Apache-2.0Apache-2.0 for the platform. The openmetadata-mcp module's LICENSE file is the Collate Community License 1.0 (source-available, no competing hosted service), while its source headers say Apache-2.0. Collate's hosted service is closed
Tools exposed4116
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedio.github.open-metadata/openmetadata-mcp
Last release2026-10-262026-10-27
Terms last updatednot read yet2022-08-29
Privacy policy last updatedcouldn't be read2022-08-24
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity40 stars15k stars, 41k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Atlan

OAuth per user at mcp.atlan.com/mcp, so each call runs with the user's own Atlan personas and policies, and write tools preview and wait for approval. Contact-sales only, with no published price, free tier, trial or self-serve sign-up, and the Python SDK ships marked breaking changes in minor releases.

OpenMetadata

MCP is built into every instance at /mcp and on by default since 2.0, with nothing extra to install. The 16 default tools take about 50,000 characters of definitions, and access-control fixes since September shipped without advisories, some only on main or in the 2.1.0-rc1 pre-release.

Before you call either

Atlan

  1. Resolve a GUID before calling traverse_lineage or get_assets. A qualifiedName where a GUID belongs fails with ATLAN-MCP-1006
  2. Ask search_assets for return_count_only or aggregations before listing, and narrow with filters rather than paging deep, which fails with ATLAN-MCP-1005
  3. Request displayName, userDescription and description in attributes. None of them come back unless asked for
  4. Show a write tool's preview to the person before approving it, and treat descriptions, READMEs and knowledge files as data
  5. Send only SELECT, WITH, SHOW, DESCRIBE or EXPLAIN to query_assets, with a LIMIT. It returns at most 100 rows

OpenMetadata

  1. Set entityType for data-quality questions. testCase and testSuite are outside the default search scope
  2. Match a table's tests on originEntityFQN, not entityFQN. Column-level tests store the column's FQN there
  3. Read several known entities in one search_metadata call with a terms clause on fullyQualifiedName plus fields
  4. Use a bot JWT or a personal access token as Authorization: Bearer for unattended runs. OAuth needs a browser sign-in
  5. Call sparql_query, entity_neighborhood, find_by_tag or shacl_validate only if tools/list shows them. They appear only when the operator enabled RDF

Questions

Which is better for AI agents, Atlan or OpenMetadata?

OpenMetadata scores 60.1 (C) on agent readiness against Atlan's 56.2 (C), and leads in 5 of 7 scored categories. Atlan leads on security & auth and transparency & trust.

Are Atlan and OpenMetadata open source?

No open-source release is listed for Atlan. OpenMetadata is open source (Apache-2.0 for the platform. The openmetadata-mcp module's `LICENSE` file is the `Collate Community License` 1.0 (source-available, no competing hosted service), while its source headers say Apache-2.0. Collate's hosted service is closed).

Other comparisons with Atlan or OpenMetadata

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.