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

Glean vs Guru

Glean scores 69.6 (B) on agent readiness against Guru's 48.8 (D), and leads in 6 of 7 scored categories. Both do company knowledge search.

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

Which one, for what

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

  • Reliability, 60 against 53
  • Schema & documentation, 93 against 58
  • Agent ergonomics, 80 against 48
  • Security & auth, 87 against 57
  • Maintenance & community, 85 against 65
  • Transparency & trust, 78 against 61

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

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

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

  • A hosted endpoint, with nothing to install

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.

Schema & documentation Glean +35

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

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

Agent ergonomics Glean +32

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

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

Security & auth Glean +30

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

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

Maintenance & community Glean +20

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

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

Transparency & trust Glean +17

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

Guru 61

A closed service under terms dated 25 March 2026. The SDK is MIT, and the MCP repository holds only a README and server.json (15). The terms delete content 90 days after a subscription ends and bar training publicly available models on customer content, while allowing models private to that customer. The security page says third-party LLMs neither train on nor retain customer data, and since 26 October 2026 Knowledge Agent owners can set chat-thread retention from 1 to 90 days. The privacy policy (modified 19 August 2025) gives no retention periods and names no processors (16 of 30). The terms promise 30 days' email notice of material changes, and the January 2026 release notes record the /boards endpoint's sunset, but there's no API deprecation policy (10 of 20). The security page says Guru runs on AWS and the privacy policy says EU personal data goes to the United States, but we found no subprocessor list (6 of 20).

Reliability Glean +7

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

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

CategoryWeightGleanGuruEdge
Reliability16%6053Glean +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9358Glean +35
Agent ergonomics13%8048Glean +32
Security & auth14%8757Glean +30
Payments & pricing10%00even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8565Glean +20
Transparency & trust7%7861Glean +17
Negative events≤1500
TotalB 69.6/100D 48.8/100

Facts side by side

FactGleanGuru
KindHTTP APIHTTP API
VendorGlean Technologies, Inc.Guru Technologies, Inc.
Hosted endpointno (local only)https://mcp.api.getguru.com/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Glean's terms of service. The OpenAPI specs repository, the API clients and the Glean CLI on GitHub are MITProprietary 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
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.getguru/mcp-server
Last release2026-10-282026-10-30
Terms last updatednot read yet2026-03-25
Privacy policy last updated2026-04-012025-08-19
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity58k npm/wk, 26k PyPI/wknone
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Glean 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

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.

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

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

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, Glean or Guru?

Glean scores 69.6 (B) on agent readiness against Guru's 48.8 (D), and leads in 6 of 7 scored categories.

Do Glean and Guru need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Glean and Guru without installing anything?

No hosted endpoint is listed for Glean. Guru has a hosted endpoint at https://mcp.api.getguru.com/mcp.

Other comparisons with Glean 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.