Skip to main content

Set up Klue

Connect Klue tools and configure card and battlecard indexing in one setup flow. Use this guide when your setup page shows Connect, Set up indexing, and Review setup.

The Connect step uses Klue's hosted Model Context Protocol (MCP) server. You can skip MCP and continue with indexing. The Set up indexing step requires a separate Admin API key, whether you connect MCP or skip it.

Prerequisites​

Before you start, confirm your access in Glean and Klue:

  • Have permission to add and configure connectors in the Glean Admin console.
  • Have a Klue Admin account to generate the indexing API key.
  • Enable System for Cross-domain Identity Management (SCIM) provisioning for your Klue instance so Glean can read the identities it needs to enforce document permissions.
  • If you plan to connect MCP, have a Klue account that can authorize access to Klue's MCP server.

Connect Klue​

Add the connector, then choose whether to connect MCP:

  1. In the Glean Admin console, go to Connectors, click Add connector, and select Klue.
  2. Enter a connector Name.
  3. Choose how to continue:
    • To include Klue tools, click Connect, sign in to Klue, and approve access for Glean.
    • To configure indexing without Klue tools, click Skip.
  4. Continue to Set up indexing after authorization succeeds or you skip MCP.

Glean registers its OAuth client through Dynamic Client Registration (DCR). You don't create an OAuth app, enter a client ID or client secret, or register a callback URL in Klue. Each user authorizes their own Klue account before using tools.

Set up indexing​

Generate an Admin API key in Klue, then enter it in Glean. Authorizing MCP does not supply this key or replace the indexing configuration.

Generate an API key​

Create the indexing key with both required scopes:

  1. Sign in to Klue as an Admin.
  2. Go to Apps & Integrations → Manage API Keys.
  3. Click Create New API Key.
  4. Give the key a description, such as Glean connector, and set an expiration that matches your security policy.
  5. Grant content:read to read cards and battlecards, and scim:read to read identities for permission enforcement.
  6. Copy the generated key and store it securely.

Enter the API key​

In Glean's Set up indexing step, paste the key into the API Key field and click Save. Glean validates access to Klue content and SCIM identities. Resolve any validation errors before continuing to Review setup.

Review setup​

Review the configuration before starting the crawl:

  1. Confirm that you completed the indexing configuration and connected or skipped MCP as intended.
  2. If User access appears, choose All users, Test group only, or None. Select the intended test group if you choose Test group only.
  3. Click Begin indexing to start the initial crawl.

Connector access settings can restrict availability in Glean. Glean also applies the indexed documents' permissions. Content becomes searchable as Glean crawls and processes it, not immediately after you save the API key.

If Skip for now appears, you can defer the crawl. This does not skip the required API key configuration. It is separate from Skip on the MCP Connect step.

Review Klue tools​

If you connected MCP, open the connector's Tools tab and review which tools are available to the intended users. Tool access settings are separate from the indexing API key. See Tool visibility scoping.

Klue enforces each user's permissions when they use a tool. The Admin API key does not authorize tool calls on a user's behalf.

Verify the setup​

Check indexing and MCP separately:

  1. Monitor crawl progress on the Klue connector page in the Admin console.
  2. After the crawl processes content, search for a known non-dynamic card or a battlecard visible to everyone. Test a restricted card with users who should and should not have access.
  3. If you connected MCP, ask Glean to retrieve Klue competitive intelligence. Complete the user's Klue authorization when prompted, and confirm that Glean uses a Klue tool and returns content that user can access.

See also​