LABSCO SUMMARY
Two surfaces, both pointed at your own Glean domain.
It is a thin bridge rather than a reimplementation: results come from your organization's index and the answers come from Glean's own chatbot, so permissions and coverage stay whatever Glean already gives that key. Setup is a docker build and two environment variables.
What it is
An MCP server over the Glean API, exposing Glean's two main surfaces: search across your indexed workplace content, and Q&A with Glean's chatbot.
What you get
- Search — a list of results for a query, from your organization's Glean index
- Chat — question and answer with the Glean chatbot
- Ships as a Dockerfile, built from src/glean/Dockerfile
Requirements
GLEAN_API_KEY and GLEAN_DOMAIN, passed into the container by your client's config. Build the image yourself with docker build -t glean-server:latest -f src/glean/Dockerfile . — there is no published package.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Finding an internal document mid-conversation
Query the company index without switching to the Glean tab.
02
Asking a question your wiki should already answer
Put it to the Glean chatbot and get the answer with its sources.
BEFORE YOU INSTALL
What to know first
Requires
- docker on PATH
- GLEAN_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
TERMINAL
git clone https://github.com/longyi1207/glean-mcp-server.git
cd glean-mcp-server
docker build -t glean-server:latest -f src/glean/Dockerfile .MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"glean-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GLEAN_API_KEY",
"-e",
"GLEAN_DOMAIN",
"glean-server"
],
"env": {
"GLEAN_API_KEY": "<YOUR_GLEAN_API_KEY>",
"GLEAN_DOMAIN": "<YOUR_GLEAN_DOMAIN>"
}
}
}
}
