Does Glean have an MCP server?

Yes Official

Glean maintains an official MCP server.

Verified 2026-09-29 against vendor docs
Access
Built into the product
Endpoint
<company>-be.glean.com/mcp/default — per-instance endpoint
Maintainer
Glean Technologies Inc
License
MIT
Stars
166
Last commit
6mo ago
What it does
Remote MCP Server that securely connects Enterprise context with your LLM, IDE, or agent platform of choice.
— how gleanwork/remote-mcp-server describes itself
The receipts
In-product <company>-be.glean.com/mcp/default — per-instance endpoint

Ships inside Glean's own product rather than as a standalone server. Documented at docs.glean.com.

Official repository gleanwork/remote-mcp-server

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

★ 166 pushed 2026-04-17 MIT Maintained
Connect it

Ships inside the vendor's own app or CLI rather than as a standalone download.

Add it from the terminal, then restart your session:

terminal
claude mcp add glean -- npx -y <package-from-readme>

Swap in the exact package and flags from the repo README — most servers need an API key passed as an environment variable.

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does Glean have an official MCP server?

Yes. Glean maintains an official MCP server. The source lives at gleanwork/remote-mcp-server on GitHub.

How do I connect Glean to Claude?

Run the server locally and register it in Claude's MCP config. In Claude Code that's a single "claude mcp add" command; in Claude Desktop you add it to claude_desktop_config.json.

How is this verdict verified?

Glean's MCP server is built into every Glean instance and on by default with OAuth, served per tenant at https://{backend-domain}/mcp/{path} as documented at docs.glean.com; also listed in the MCP Registry under Glean's own namespace com.glean/mcp, pointing to the gleanwork/remote-mcp-server repo. GitHub metadata is refreshed every six hours.

How we know

Glean's MCP server is built into every Glean instance and on by default with OAuth, served per tenant at https://{backend-domain}/mcp/{path} as documented at docs.glean.com; also listed in the MCP Registry under Glean's own namespace com.glean/mcp, pointing to the gleanwork/remote-mcp-server repo.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Workplace & Productivity

See all Workplace & Productivity servers →