Glean MCP Server

MCP server for Glean. The glean mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

An MCP server implementation that integrates the Glean API, providing the Search and Chat functions.

Its toolset

Everything the assistant can do here goes through one of these:

• Search — List of search results given a query
• Chat — Q&A with Chatbot

Configuration

You will need 2 environment variables: GLEAN_API_KEY, GLEAN_DOMAIN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Glean's toolset — Search, Chat — is a fair guide to whether it matches your workflow. It is maintained by longyi1207; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the glean mcp server does with a few real requests.