Glean Remote MCP Server

com.gleanPublished by glean.comv1.2.1Updated Oct 25, 2026

Remote MCP Server that securely connects Glean Enterprise Knowledge with your IDE, LLM, or agents.

The publisher's own server: Registry Mcp

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Glean's remote MCP server gives AI assistants permission-aware access to an organization's enterprise knowledge, documents, and people.

What you can do
Search and retrieve information from company documents, wikis, and knowledge bases through natural language requests, respecting existing access permissions. Find colleagues, understand org structure, and identify subject matter experts. Connect from any MCP-compatible client over streamable HTTP with OAuth 2.0 and SSO authentication.
When to use it
Useful when an assistant working in an IDE, LLM, or agent platform needs to answer questions from internal company knowledge or locate people and expertise, and the organization already runs Glean with configured access controls.
Requirements
A remote endpoint at the organization's unique Glean MCP server URL, obtained through the vendor's setup guide. OAuth 2.0 authentication with SSO, configured in the MCP client. An MCP-compatible client such as Claude Desktop or Cursor.
Before you install
The server exposes internal company documents and people data to the connected assistant; access is limited to the user's existing permissions but queries and results leave the local machine for Glean's remote service. Setup requires OAuth sign-in through the organization's SSO.

Installation

In SourceWeft

  1. Open Glean Remote MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

[Glean Logo]

Glean Remote MCP Server

Documentation | Setup Guide | MCP Registry

[MCP Server] [GA]


Remote MCP Server that securely connects Glean Enterprise Knowledge with your IDE, LLM, or agent platform of choice.

Overview

The Glean MCP Server implements the Model Context Protocol to provide AI assistants and developer tools with secure, real-time access to your organization's enterprise knowledge. It enables natural language interaction with company documents, people, and data while respecting existing access permissions.

Features

  • Enterprise Knowledge Access - Search and retrieve information from your company's documents, wikis, and knowledge bases
  • People & Expertise Discovery - Find colleagues, understand org structure, and identify subject matter experts
  • Permission-Aware - All data access respects your organization's existing access controls
  • OAuth 2.0 Authentication - Secure authentication with SSO integration
  • Streamable HTTP Transport - Modern, efficient protocol for real-time communication

Getting Started

Each organization has a unique Glean MCP server URL. To set up the Glean MCP Server for your organization:

View the Setup Guide

The guide covers:

  • Obtaining your organization's MCP server URL
  • Configuring your MCP client (Claude Desktop, Cursor, etc.)
  • Authentication setup
  • Available tools and example prompts

Compatibility

The Glean MCP Server works with any MCP-compatible client. See the full list of supported hosts for details.

Documentation

Support

  • Documentation: docs.glean.com
  • Issues: For bugs or feature requests related to the Glean MCP Server, please contact Glean support through your organization's support channel

License

This project is licensed under the MIT License - see the LICENSE file for details.

Source: README.md at commit 8fc3156

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Remote-Mcp integrations