remote-mcp-server
Remote MCP Server that securely connects Enterprise context with your LLM, IDE, or agent platform of choice.
Links
README
From the repo.
Glean Remote MCP Server
Documentation | Setup Guide | MCP Registry
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:
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.
Collected info
- ★ 164 stars
- ⎇ 1 forks
- Source updated: 7/18/2026
Config for your environment
Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.
Tool
OS
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "{MCP_ENDPOINT_URL}"
}
}
}Paste into mcpServers in the config file. Restart Cursor after saving.
If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.