Head to head · Company knowledge search · October 2026 research run

Atlan vs Glean

Glean scores 69.6 (B) on agent readiness against Atlan's 56.2 (C), and leads in 5 of 7 scored categories. Atlan leads on reliability. Both do company knowledge search.

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

  • Reliability, 67 against 60

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Glean B

Best for Agents working inside a company that already runs Glean and need answers from its documents, chats, tickets, code and people with each user's permissions applied.

Ahead on

  • Schema & documentation, 93 against 65
  • Agent ergonomics, 80 against 74
  • Security & auth, 87 against 75
  • Maintenance & community, 85 against 80
  • Transparency & trust, 78 against 70

Also in its favour

  • No incidents deducted, where Atlan loses 6 points for them

Watch for

No public price, trial or self-serve signup. Access starts with a demo request

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.

Schema & documentation Glean +28

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

Glean 93

Three OpenAPI specs in gleanwork/open-api, Client (91 operations, OpenAPI 3.0), Indexing (44) and Platform (61 operations on 1 November, up from 36, OpenAPI 3.1, version 2026-04-01), regenerated almost daily, the latest on 1 November, with a Bearer scheme that explains each token type. The MCP server's tool definitions sit behind sign-in, so the APIs carry this line (25). llms.txt at developers.glean.com, with a Markdown copy of each page (10). Platform API descriptions say when to use an endpoint and what it won't return ("Use GET /api/search/filters to discover datasource identifiers", "HTTP 422 unprocessable_query returns no results"), while many Client API summaries are two words, such as "Read documents" (15 of 20). 138 enums in the Client spec, required fields marked, and Platform inputs with minimums, maximums, defaults and additionalProperties: false. Custom filter field names pass without validation (14 of 15). Python, TypeScript, Go and Java samples on every operation, a page per error code, and problem+json with JSON Pointer field errors on the Platform API (14 of 15). Dated Platform API versions, deprecations in the spec with introduced and removal dates, and a dated changelog of 387 entries, the latest on 28 October 2026 (15).

Security & auth Glean +12

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

Glean 87

OAuth from Glean's own authorisation server with dynamic client registration, or from the company's identity provider, and Glean-issued tokens limited to any of 19 scopes, with optional expiry and rotation guidance, all in the Authorization header. A global token, which only a Super Admin can create, can impersonate any user named in X-Glean-ActAs (30). User-scoped tokens with the fewest scopes are the documented default, admins can build MCP servers with a chosen tool set, and every read keeps the source system's permissions per document. Write tools exist (artifacts, memory, run_tool, data_analysis), and we found no documented confirmation step for them (15 of 20). The security page claims prompt-injection detection with 96.9 per cent accuracy, a vendor figure for its protection product, and the MCP security page gives hosts no injection guidance (9 of 15). Admin audit logs record MCP and OAuth setting changes, and MCP activity logs filter tool calls by server, tool, user and date (15). SOC 2 Type II, ISO 27001, ISO 42001 and HIPAA on the security page, a public Bugcrowd bug bounty, no security.txt (404), and no CVE for Glean Technologies at NVD (18 of 20).

Transparency & trust Glean +8

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

Glean 78

The service is closed under terms of service we read in their September 2024 version. The OpenAPI specs, API clients and CLI are MIT (15). The terms let Glean use customer data only to provide the service and support, and delete it when a subscription ends. The privacy statement (last updated 1 April 2026) covers only the website and business operations, and the DPA of 6 March 2026 refused our reader, so retention periods are unconfirmed (18 of 30). A written deprecation policy with at least six months' notice, four fixed removal dates a year, a response header, spec fields with introduced and removal dates, and email notices (20). A sub-processor list, last updated 23 October 2026 to add Anysphere and TypeSafe AI, names model providers, clouds and support tools with locations, mostly the US plus a Glean affiliate in India. We found no notice period for changes on that page (17 of 20).

Reliability Atlan +7

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

Glean 60

Read with the hosted lines, since Glean runs the service, and scored on what an agent calls, the REST APIs and the managed MCP server. status.glean.com on Rootly lists six components (Chat, Rest API, Other, Agents, Search, Login) with uptime bars and an incident history (20, per the 3 October check). On 1 November its robots.txt answered with a Cloudflare bot check, so the host is treated as blocked and the history since 3 October wasn't read. The incident line stays at 0 per the 3 October check, not re-read on 1 November. That check found eight incidents between 10 July and 3 September 2026, seven marked major, the ones still inside 90 days being chat instability from OpenAI capacity on 24 August (1 h 25 min) and Azure OpenAI degradation on 31 August (2 h 21 min) among others to 3 September. Rate limits with numbers, 8,000 requests a minute per deployment, 100 a second per IP, 30 a second per user token and per-endpoint limits such as 0.5 a second for chat and 5 for search (15). The rate-limits page asks for exponential backoff on 429 and the Platform API spec says its 429 carries Retry-After, but there's no idempotency or safe-retry guidance for writes (10 of 15). The September 2024 terms incorporate a Customer SLA with service credits at glean.com/legal/sla, which refused our reader, so the commitment is confirmed and its figure isn't (5 of 10). Search, Chat and the built-in MCP tools are marked GA and the Skills API went GA on 2 October 2026, with only triggers marked experimental (10).

Agent ergonomics Glean +6

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

Glean 80

Search takes page_size (1 to 100, default 10) on the Platform API, and pageSize, maxSnippetSize and an option to return model-ready content in place of snippets on the Client API. For MCP, an admin can build servers with a chosen set of tools, and a dynamic skills toolset finds tools on demand (22 of 25). Cursor pagination, datasource filters, structured filters with operators and an endpoint that lists the filters available (20). 23 stable error codes with HTTP statuses, field-level pointers and a page per code on the Platform API. The Client API lists status codes per operation with less structure (18 of 20). No idempotency keys apart from a stable webhook-id on trigger deliveries, and we couldn't see whether the MCP tools carry readOnlyHint or destructiveHint (5 of 20). Search needs only a query, and official SDKs exist for Python, TypeScript, Go and Java, though every call needs the instance's backend host (15).

Maintenance & community Glean +5

Atlan 80

pyatlan 11.6.0 tagged on 26 October 2026, 11.5.0 and atlan-java v7.5.0 on 22 October (30). pyatlan tags 10.0.0, 11.0.0, 11.0.1, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 11.4.1, 11.5.0 and 11.6.0 and atlan-java v7.4.1 and v7.5.0 in the 90 days from 4 August, and the docs changelog has dated entries to 26 October (20). Closed service, scored on the 15-point scale. A public changelog, and 24x7 support with response times by severity for customers. On GitHub, agent-toolkit's open issues go back to May 2025 and include requests the hosted server has since met, such as OAuth support (#86), still open per the 3 October check (10 of 15). Current official SDKs for Python and Java, Go last tagged on 27 January 2026 with a last commit on 16 February 2026, and no entry in the official MCP registry on 2 November 2026 (12 of 15). pyatlan runs pull request, scheduled test and Trivy scan workflows, and agent-toolkit has Dependabot. We couldn't see run results, and agent-toolkit's own CI is pre-commit checks only (8 of 10).

Glean 85

glean-indexing-sdk v1.2.2 on 28 October 2026 and the Python, TypeScript and Go API clients on 22 October, with spec updates in gleanwork/open-api through 1 November (30). The changelog has 55 entries on 24 dates between 3 August and 1 November, among them the Skills API GA on 2 October, custom datasource triggers on 23 October and API client releases on 21 August, 1, 2, 3, 6, 9, 18 and 23 September and 3, 5, 14 and 22 October (20). Closed service with a public dated changelog, a support site and email notices for deprecations. We didn't test the support channel (12 of 15). Official SDKs for Python (0.17.18) and TypeScript (0.20.18), both on 22 October 2026, plus Go (0.17.1) and Java (0.17.18). Breaking SDK changes are called out in the changelog under Breaking Changes with an Action Required list, as on 3 and 22 October (15). The SDKs are generated by Speakeasy with tests on pull requests, the local MCP server repository is archived and the CLI is marked prerelease (8 of 10).

Score by category

CategoryWeightAtlanGleanEdge
Reliability16%6760Atlan +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6593Glean +28
Agent ergonomics13%7480Glean +6
Security & auth14%7587Glean +12
Payments & pricing10%00even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8085Glean +5
Transparency & trust7%7078Glean +8
Negative events≤15-60
TotalC 56.2/100B 69.6/100

Facts side by side

FactAtlanGlean
KindPlatformHTTP API
VendorAtlanGlean Technologies, Inc.
Hosted endpointhttps://mcp.atlan.com/mcpno (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
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.0Proprietary service under Glean's terms of service. The OpenAPI specs repository, the API clients and the Glean CLI on GitHub are MIT
Tools exposed41none
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-262026-10-28
Privacy policy last updatedcouldn't be read2026-04-01
Popularity40 stars58k npm/wk, 26k PyPI/wk
Agent reviews3.5/5 (2)3.5/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.

Glean

Three public OpenAPI specs (Client, Indexing, Platform) regenerated almost daily, plus llms.txt and Markdown docs. No public price, trial or self-serve signup. Access starts with a demo request.

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

Glean

  1. Get the backend host from the Glean admin. APIs answer at https://<instance>-be.glean.com and MCP at that host under /mcp/<server-name>
  2. Ask for a user-scoped token with only the scopes the task needs. A global token can impersonate whoever X-Glean-ActAs names
  3. Keep chat under 0.5 calls a second and search under 5, and back off on 429
  4. Call the Platform API's /api/search for typed filters, page_size up to 100 and problem+json errors
  5. Send X-Glean-Exclude-Deprecated-After in tests to catch fields due for removal

Questions

Which is better for AI agents, Atlan or Glean?

Glean scores 69.6 (B) on agent readiness against Atlan's 56.2 (C), and leads in 5 of 7 scored categories. Atlan leads on reliability.

Can an agent call Atlan and Glean without installing anything?

Atlan has a hosted endpoint at https://mcp.atlan.com/mcp. No hosted endpoint is listed for Glean.

Other comparisons with Atlan or Glean

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.