remote

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

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio gleanwork-remote-mcp-server node server.js \
  --env GLEAN_MCP_CLIENT_ID="your-client-id" \
  --env GLEAN_MCP_SERVER_URL="https://your-org.mcp.glean" \
  --env GLEAN_MCP_CLIENT_SECRET="your-client-secret"

How to use

The Glean Remote MCP Server exposes a Model Context Protocol (MCP) interface that lets your IDE, IDE-integrated tools, or AI agents securely query and interact with your organization's enterprise knowledge base. It supports enterprise-style search across documents, wikis, and knowledge bases, along with people and expertise discovery. The server enforces existing permissions and OAuth 2.0 authentication to ensure secure access. Tools provided by MCP clients (such as Claude, Cursor, or other MCP-enabled assistants) can issue natural language prompts that are translated into structured MCP requests, allowing real-time, contextually aware responses that respect access controls. To get started, point your MCP client at the organization’s MCP server URL and complete the authentication flow as guided by your internal setup guide. The server is designed to be compatible with any MCP client listed in the MCP registry, enabling broad interoperability across tools used in development, analysis, or governance workflows.

How to install

Prerequisites:

Node.js (LTS version) installed on the host
Access to your organization's MCP server URL and credentials

Clone or obtain the MCP server package for the Glean Remote MCP Server (as provided by your organization).
Install dependencies:
- npm install
Configure environment variables:
- Create a .env file or export variables in your shell: GLEAN_MCP_SERVER_URL=https://your-org.mcp.glean GLEAN_MCP_CLIENT_ID=your-client-id GLEAN_MCP_CLIENT_SECRET=your-client-secret (Add any other environment variables your deployment requires)
Run the server:
- node server.js
- Or use a process manager (e.g., PM2) for production, e.g.: pm2 start server.js --name glean-remote-mcp
Verify the server is reachable by querying the MCP endpoint from a client, and ensure authentication succeeds.
If you’re deploying behind a reverse proxy or TLS terminator, configure your proxy accordingly and ensure MCP traffic is secured.

Additional notes

Tips and common issues:

Ensure GLEAN_MCP_SERVER_URL is the public, reachable MCP server URL used by your clients.
If you rotate client credentials, update GLEAN_MCP_CLIENT_ID and GLEAN_MCP_CLIENT_SECRET accordingly and restart the server.
For production deployments, use a process manager and enable TLS termination at a reverse proxy; ensure the OAuth 2.0 flow is correctly configured for your identity provider.
Check your organization’s access controls and permissions; misconfigured permissions can block data retrieval.
Monitor logs for authentication errors and MCP tool compatibility notes from the MCP Tools Reference to align with client expectations.