An MCP host is the application that runs an MCP client. It is where the user interacts with an assistant, and it is responsible for connecting to MCP servers (like the Glean MCP server) and exposing those servers’ tools to the model.

​
Host vs. Server

  • MCP Server: Provides capabilities (tools) such as search, chat, and read document. The Glean MCP server is the provider of Glean’s permission-aware capabilities.
  • MCP Host: The app that your users run (e.g., a desktop IDE or chat app). It discovers and invokes tools from connected MCP servers.

​
How hosts connect to Glean MCP Server

Hosts differ in connection method and who configures them:
  • Native HTTP: Connects directly to the Glean MCP server over HTTP.
  • stdio-only (bridge required): Uses local process I/O. To reach remote HTTP servers like Glean, use a bridge (e.g., mcp-remote).
  • Web-based/managed: No local config; an administrator adds the Glean MCP server centrally.

​
Admin-managed vs. end‑user installs

  • Admin-managed: An administrator configures the Glean MCP server as a remote URL for the organization. Example: ChatGPT managed install; Claude for Teams/Enterprise.
  • End‑user: Individual users add the Glean MCP server in their own app settings. Examples: Cursor, VS Code, Claude Code, Goose, Windsurf (with bridge where required).

​
Supported hosts

Supported hosts

The following hosts are supported for connecting to the Glean MCP server. Install type and key constraints are noted for clarity.
  • ChatGPT — Admin-managed install; fixed endpoint https://[instance-name]-be.glean.com/mcp/chatgpt . Connection: HTTP (managed). Tools: search, fetch. Auth: OAuth (recommended).
  • Claude Code — End-user install. Connection: Native HTTP (also supports stdio). Platforms: macOS, Linux, Windows. Tools: search, chat, read_document. Auth: OAuth (recommended).
  • Claude for Desktop — End-user install. Connection: stdio only; requires mcp-remote to bridge to HTTP servers. Platforms: macOS, Windows, Linux. Tools: search, chat, read_document.
  • Claude for Teams/Enterprise — Admin-managed install. Connection: HTTP (managed). Servers configured at organization level; no local config. Tools available per admin policy.
  • Cursor — End-user install. Connection: Native HTTP. Platforms: macOS, Linux, Windows. Tools: search, chat, read_document. Auth: OAuth (recommended).
  • Goose — End-user install. Connection: Native HTTP (YAML config). Platforms: macOS, Linux, Windows. Tools: search, chat, read_document.
  • Visual Studio Code — End-user install. Connection: Native HTTP (one-click protocol vscode:). Platforms: macOS, Linux, Windows. Tools: search, chat, read_document.
  • Windsurf — End-user install. Connection: stdio only; requires mcp-remote to bridge to HTTP servers. Platforms: macOS, Linux, Windows. Tools: search, chat, read_document.

​
Choosing a host

  • Your users’ workflow: Editors (VS Code, Cursor) vs. chat (Claude Desktop, ChatGPT).
  • Connection model: Native HTTP is simplest; stdio-only hosts need a bridge to reach remote servers.
  • Admin requirements: If you need central control, pick a managed host; otherwise enable end‑user installs.

​
Next steps