> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glean

> Remote MCP server for Glean enterprise search and knowledge management

<Info>
  **Hosted by a third party.** This MCP server is built and hosted by the
  vendor, not Runlayer. This guide covers connecting it through Runlayer for
  governance, policies, and audit.
</Info>

Connect your AI assistant to [Glean](https://www.glean.com) for enterprise search, people directory, AI chat, and document retrieval. This is a **remote MCP server** hosted by Glean — Runlayer proxies requests to Glean's own MCP endpoint using **Streamable HTTP** transport.

## Available Tools

| Tool                    | Description                                                           |
| ----------------------- | --------------------------------------------------------------------- |
| `company_search`        | Search Glean's content index with filtering and configuration options |
| `people_profile_search` | Search Glean's People directory to find employee information          |
| `chat`                  | Interact with Glean's AI assistant with message history and citations |
| `read_documents`        | Retrieve documents by ID or URL for detailed analysis                 |

## Setup

<Steps>
  <Step title="Get Your Glean MCP Server URL">
    1. Log in to Glean as an admin
    2. Identify your **Instance Name** (the subdomain of your Glean deployment)
    3. Your Glean MCP server URL follows this pattern:
       ```
       https://<GLEAN_INSTANCE>-be.glean.com/mcp/<MCP_SERVER_NAME>
       ```
       Replace `<GLEAN_INSTANCE>` with your instance name and `<MCP_SERVER_NAME>` with the server name configured in Glean
    4. Refer to the [Glean MCP documentation](https://docs.glean.com/user-guide/mcp/usage) for details on enabling MCP in your Glean instance
  </Step>

  <Step title="Add Server in Runlayer">
    1. In Runlayer, go to **My connectors** and click **Add connector**
    2. Select **Remote MCP server** and enter your Glean MCP server URL
    3. Select **Streamable HTTP** as the transport type
    4. Configure authentication as required by your Glean instance
  </Step>
</Steps>

## Troubleshooting

<Accordion title="Authentication failed">
  Verify that authentication is correctly configured for your Glean MCP endpoint. Ensure the instance name in the URL matches your Glean deployment subdomain.
</Accordion>

<Accordion title="Permission denied for certain searches">
  Your Glean MCP server may not have permissions for all content types. Contact your Glean admin to adjust permissions.
</Accordion>

<Accordion title="No results returned">
  Check that the content you're searching for has been indexed by Glean. New content may take time to appear in search results.
</Accordion>