Model Context Protocol (MCP) Remote Server
Connect your AI tools to Glean's enterprise knowledge base with zero setup required. The Remote MCP Server is built directly into Glean's platform, providing instant access to your organization's data through any MCP-compatible host application.
The Remote MCP Server is available to all Glean customers during the public beta period.
General Availability: Targeting late September 2025
Install Now
Get started in seconds with our quick installer. Click here to configure your setup - select your host application and enter your Glean instance details below.
Quick Install Remote MCP Server
Get connected in seconds with our MCP Host configurator
- CLI Command
- Manual Config
CLI Installation Command
claude mcp add glean_default https://[instance]-be.glean.com/mcp/[endpoint] \
--transport http \
--scope user
Run this command in your terminal to add the MCP server to Claude Code.
Configuration Preview
{
"glean_default": {
"type": "http",
"...": "Complete the 'Configure Server URL' section above"
}
}
How does this work?
The Remote MCP Server connects your AI tools directly to Glean's search and knowledge platform. Installation is simple:
- Configurator: Use our configurator to quickly generate the MCP server configuration.
- CLI configuration: Use our CLI tool to automatically configure supported hosts from your terminal.
- Manual configuration: Copy the generated configuration to your host's settings file.
- Administrator setup: ChatGPT Connectors and Claude for Teams/Enterprise require your admin to install first - no local configuration needed.
By default, authentication uses OAuth with Dynamic Client Registration (DCR) - no API keys needed. If you need to use an API token instead, chose the Bearer Token option under Authentication Method.
For ChatGPT Connectors and Claude for Teams/Enterprise, administrator setup is required. The configurator will provide instructions when you select these hosts.
Host Compatibility
MCP host compatibility is evolving. The table below reflects validated support and our recommended OAuth method:
MCP Host Application | Recommended OAuth Method | Configuration Method |
---|---|---|
ChatGPT | Native | Custom Setup |
Claude Code | Native | Quick Installer / CLI / Manual |
Claude for Desktop | Bridge | Quick Installer / CLI / Manual |
Cursor | Native | One-Click / CLI / Manual |
Goose | Native | Quick Installer / CLI / Manual |
Visual Studio Code | Native | One-Click / CLI / Manual |
Windsurf | Bridge | Quick Installer / CLI / Manual |
Available Servers
During the public beta, we're providing access to two specialized MCP servers:
- Tools Server (Default)
- ChatGPT Server
The Tools Server provides unified access to Glean's core capabilities through a streamlined interface. This server is ideal for general-purpose AI interactions with your enterprise data.
Endpoint: https://[instance]-be.glean.com/mcp/default
Key Features:
- Comprehensive search across all your connected data sources
- Intelligent chat interactions with context awareness
- Document retrieval and analysis
- People directory search
The ChatGPT Server is optimized specifically for ChatGPT Connectors, providing seamless integration with OpenAI's ChatGPT workspace.
Endpoint: https://[instance]-be.glean.com/mcp/chatgpt
Key Features:
- Conforms to OpenAI's MCP Connector spec
- Optimized response formatting for ChatGPT
- Automatic citation handling
- Token-efficient responses
Use this endpoint specifically for ChatGPT integrations as it uses tool naming conventions that ChatGPT expects (e.g., "fetch" instead of "read_document").
To configure Glean's MCP servers, follow these setup instructions.
Core Capabilities
The remote MCP server exposes a curated set of Glean capabilities as MCP tools. Administrators can enable defaults and optionally add more.
Default Tools
search
(Search) - Search across your entire knowledge basechat
(Chat) - Interactive conversations with Glean's AIread_document
(Read Document) - Retrieve specific documents by ID or URL
Additional Configurable Tools
code_search
(Code Search) - Search your codebase and repositoriesemployee_search
(Employee Search) - Find people and expertise in your organizationgmail_search
(Gmail Search) - Search Gmail messages and threadsmeeting_lookup
(Meeting Lookup) - Find meeting recordings and notesoutlook_search
(Outlook Search) - Search Outlook emails and calendar
Troubleshooting
Client Authentication Failed
When repeatedly connecting and disconnecting, some host applications may end up using stale client ids. If you see the message
Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). The requested OAuth 2.0 Client does not exist.
while authenticating, you can clear your MCP credentials and re-authenticate. Doing so is specific to the MCP host application.
- Visual Studio Code - Run the command
Authentication: Remove Dynamic Authentication Providers
- Cursor - Run the command
Cursor: Clear All MCP Tokens
Local MCP Server
You can also use Glean's open-source stdio MCP server:
@gleanwork/local-mcp-server
Self-hosted MCP server implementation for Glean's search and chat capabilities
The local server is ideal for:
- Development and testing
- Air-gapped environments
- Custom tool development
- Full control over the server infrastructure