Klue overview
Search Klue cards and battlecards alongside content from your other connected apps. You can also connect Klue's hosted Model Context Protocol (MCP) server to retrieve competitive intelligence through tools using each user's Klue account.
Supported objects
The native connector indexes these Klue objects:
| Object | Indexed content and limits |
|---|---|
| Card | Non-dynamic cards, including title, body content, and author information, with their document permissions |
| Battlecard | Non-dynamic battlecards visible to everyone, with content assembled from their member cards |
Card metadata includes competitors, competitor groups, topics, and tags. Battlecard metadata includes competitors, competitor groups, status, and reviewer information when available. Glean uses this metadata for facets rather than indexing it as standalone documents.
Authentication
Indexing and MCP use separate credentials:
| Capability | Authentication | Availability |
|---|---|---|
| Indexed search | Admin API key with content:read and scim:read | Content becomes searchable as Glean crawls and indexes it |
| Klue MCP tools | Per-user OAuth through Dynamic Client Registration (DCR) | Users authorize their Klue accounts after an admin connects MCP and makes tools available to them |
The indexing API key does not authorize MCP tool calls. MCP authorization does not grant Glean the API key it needs for indexing.
Permissions
Glean reads Klue user profiles through System for Cross-domain Identity Management (SCIM). It uses the profiles' Klue roles and visibility groups to build group memberships and enforce card permissions.
Card access depends on its audience:
- Cards shared with everyone are available across the Glean organization, subject to connector access settings.
- Cards limited to curators are available to Klue admins and curators.
- Cards shared with visibility groups are available to those groups, Klue admins, curators, and users with full access.
Glean indexes only battlecards with the everyone audience. These battlecards are available across the Glean organization, subject to connector access settings. Restricted battlecards are not indexed.
For MCP tools, Klue enforces the permissions of the user who authorizes the request. Those permissions are separate from the Admin API key used for indexing.
Sync behavior
Glean runs full and incremental crawls for cards and battlecards. Incremental crawls request content updated since the previous crawl. Full identity syncs refresh Klue users and the group memberships derived from their profiles.
Content and permission changes depend on these syncs. They do not appear in indexed search immediately after a change in Klue.
Limitations
Keep these limits in mind when choosing content to test:
- Glean does not index dynamic cards or restricted battlecards.
- Competitors, competitor groups, topics, and tags are metadata, not standalone documents.
- Indexing requires SCIM access as well as content access. The API key must include both required scopes.
See also
- Choose your Klue setup: Select the guide that matches your setup page.
- Klue MCP: Configure or manage a standalone MCP connection.
- Troubleshoot Klue: Check missing content, API key validation, and permissions.