Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Glean MCP Server for Claude

Connect Claude to Glean — run company-wide enterprise search and chat with Glean Assistant across your connected workplace apps — with the official Glean Model Context Protocol server.

by Glean·added 2026-06-17·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Glean recommends the remote MCP server integrated directly in Glean; this local server is intended for experimental and testing use.
  • Search and chat run against your connected company data — scope the API token to the right user/permissions.

Privacy notes

  • Search results and Glean Assistant responses surface internal company content into the MCP client context and the model's prompt.
  • GLEAN_API_TOKEN and GLEAN_INSTANCE are secrets — keep them in the client config or environment, never in shared repositories.

Prerequisites

  • A Glean account/instance (GLEAN_INSTANCE) and an API token (GLEAN_API_TOKEN).
  • Node.js (npx) and an MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "glean": {
      "command": "npx",
      "args": ["-y", "@gleanwork/mcp-server"],
      "env": {
        "GLEAN_API_TOKEN": "<your-token>",
        "GLEAN_INSTANCE": "<your-instance>"
      }
    }
  }
}

About this resource

Overview

The Glean MCP Server is the official Model Context Protocol server from Glean. It lets Claude run company-wide enterprise search and chat with Glean Assistant across your connected workplace apps — bringing internal knowledge into Claude in natural language. It runs locally via npx @gleanwork/mcp-server over stdio and is licensed under MIT.

Glean recommends using the remote MCP server integrated directly in Glean for production; this local server is primarily intended for experimental and testing use.

Key capabilities

  • Company search — search across the apps and content Glean has indexed for your organization.
  • Glean Assistant chat — ask questions and get answers grounded in your company's knowledge.

Results respect the permissions of the authenticated Glean user, so Claude only sees what that user is allowed to see.

Installation

Claude Code

claude mcp add glean \
  -e GLEAN_API_TOKEN=<your-token> \
  -e GLEAN_INSTANCE=<your-instance> -- \
  npx -y @gleanwork/mcp-server

Claude Desktop

{
  "mcpServers": {
    "glean": {
      "command": "npx",
      "args": ["-y", "@gleanwork/mcp-server"],
      "env": {
        "GLEAN_API_TOKEN": "<your-token>",
        "GLEAN_INSTANCE": "<your-instance>"
      }
    }
  }
}

Requirements

  • A Glean instance and API token.
  • Node.js (npx) and an MCP client (Claude Code or Claude Desktop).

Security

  • For production, prefer Glean's integrated remote MCP server; the local server is for testing.
  • Search and chat surface internal company data — scope the token to the right user and permissions.
  • Treat GLEAN_API_TOKEN and GLEAN_INSTANCE as secrets.

Source Verification Notes

Verified on 2026-06-17:

  • The official repository github.com/gleanwork/mcp-server (MIT) documents the @gleanwork/mcp-server package, the GLEAN_API_TOKEN/GLEAN_INSTANCE configuration, the search and chat capabilities, and the recommendation to use Glean's integrated remote MCP for production.
  • Glean's developer documentation describes the underlying search and assistant APIs.
  • Claude Code's MCP documentation describes the connector setup pattern used here.
#glean#enterprise-search#knowledge-management#rag#productivity

Source citations

Add this badge to your README

Show that Glean MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/glean-mcp-server.svg)](https://heyclau.de/entry/mcp/glean-mcp-server)

How it compares

Glean MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldGlean MCP Server for Claude

Connect Claude to Glean — run company-wide enterprise search and chat with Glean Assistant across your connected workplace apps — with the official Glean Model Context Protocol server.

Open dossier 		DataStax Astra DB MCP Server for Claude

Connect Claude to DataStax Astra DB — manage collections and records, run bulk operations, and perform vector and hybrid search — with the official Astra DB Model Context Protocol server.

Open dossier 		Dropbox Dash MCP Server for Claude

Official Dropbox Dash remote MCP server that lets Claude search connected company content, read documents, resolve source URLs, and inspect Dash knowledge from MCP-capable clients.

Open dossier 		Weaviate MCP Server for Claude

Connect Claude to a Weaviate vector database — run hybrid search, inspect collection config, list tenants, and upsert objects — using Weaviate's built-in Model Context Protocol server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorGleanDataStaxDropboxWeaviate
Added2026-06-172026-06-172026-06-032026-06-17
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Glean recommends the remote MCP server integrated directly in Glean; this local server is intended for experimental and testing use. Search and chat run against your connected company data — scope the API token to the right user/permissions.✓Tools create, update, and delete collections and records, including bulk operations — scope the application token and confirm destructive actions. Bulk delete/update operations affect many records at once; review before running them through Claude.✓Dropbox Dash can search across many connected company sources, including cloud documents, collaboration tools, CRM records, support systems, meeting content, and code or project tools. Start with narrow prompts and source filters instead of broad company-wide searches. Treat Dropbox OAuth tokens, app keys, app secrets, and bearer tokens as secrets. Store them in MCP client credential storage or environment variables rather than prompts, checked-in config, screenshots, or shared transcripts. The published remote MCP tools are centered on search, reading, discovery, URL resolution, identity lookup, and read-only source actions, but returned content can still influence generated code, decisions, emails, or tickets. Keep human review on downstream actions. Respect Dropbox team admin controls for app integrations. If a user cannot register or connect an app, do not work around that by sharing another user's token or app credentials.✓The MCP server runs inside your Weaviate instance and respects its existing RBAC; scope the API key to least privilege. The object-upsert tool writes data — restrict write access to the collections Claude should modify.
Privacy notes✓Search results and Glean Assistant responses surface internal company content into the MCP client context and the model's prompt. GLEAN_API_TOKEN and GLEAN_INSTANCE are secrets — keep them in the client config or environment, never in shared repositories.✓Documents, vectors, and search results enter the MCP client context and the model's prompt. ASTRA_DB_APPLICATION_TOKEN and ASTRA_DB_API_ENDPOINT are secrets — keep them in the client config or environment.✓Tool results can expose document titles, metadata, preview text, markdown content, visual page renders, binary file content, source names, labels, original URLs, user identity details, and source-specific records visible through Dropbox Dash. Connected sources may include Google Workspace, Microsoft 365, Slack, Gmail, Jira, Confluence, Gong, Zoom, Workday, GitHub, Dropbox, and other internal systems. Returned snippets can contain customer data, credentials, unreleased product details, employee records, sales notes, or support history. MCP client logs, AI transcripts, screenshots, terminal scrollback, and generated artifacts may retain Dash results outside Dropbox's normal audit and retention controls. The optional local MCP server stores Dropbox tokens in the system keyring when available, with a documented fallback token file. Review local machine access, backups, and secret-cleanup policy before using it on shared hosts.✓Query text, retrieved objects, and collection metadata enter the MCP client context and the model's prompt. The Weaviate endpoint URL and API key are secrets — keep them in the client config or environment, not in shared repositories.
Prerequisites
  • A Glean account/instance (GLEAN_INSTANCE) and an API token (GLEAN_API_TOKEN).
  • Node.js (npx) and an MCP client such as Claude Code or Claude Desktop.
  • A DataStax Astra DB account and a database.
  • An Astra DB application token (ASTRA_DB_APPLICATION_TOKEN) and API endpoint (ASTRA_DB_API_ENDPOINT).
  • Node.js (npx) and an MCP client such as Claude Code or Claude Desktop.
  • Dropbox Dash account with access to the sources Claude should search or read
  • MCP-capable client with remote HTTP MCP support, such as Claude Code, Claude Web/Desktop custom connectors, Cursor, or ChatGPT
  • Dropbox OAuth approval or a Dropbox app access token when using clients that do not support Dynamic Client Registration
  • Dropbox team/admin policy allowing the user to connect Dash to external MCP clients
  • A Weaviate instance on v1.37.1 or later (self-hosted or Weaviate Cloud).
  • The MCP server enabled on that instance via MCP_SERVER_ENABLED=true.
  • A Weaviate API key with the RBAC permissions for the collections Claude should reach.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add glean -e GLEAN_API_TOKEN=<your-token> -e GLEAN_INSTANCE=<your-instance> -- npx -y @gleanwork/mcp-server
claude mcp add astra-db -e ASTRA_DB_APPLICATION_TOKEN=<your-token> -e ASTRA_DB_API_ENDPOINT=<your-endpoint> -- npx -y @datastax/astra-db-mcp
claude mcp add --transport http DropboxDashMCP https://mcp.dropbox.com/dash
claude mcp add --transport http weaviate https://<your-weaviate-host>/v1/mcp
Config
{
  "mcpServers": {
    "glean": {
      "command": "npx",
      "args": ["-y", "@gleanwork/mcp-server"],
      "env": {
        "GLEAN_API_TOKEN": "<your-token>",
        "GLEAN_INSTANCE": "<your-instance>"
      }
    }
  }
}
{
  "mcpServers": {
    "astra-db-mcp": {
      "command": "npx",
      "args": ["-y", "@datastax/astra-db-mcp"],
      "env": {
        "ASTRA_DB_APPLICATION_TOKEN": "<your-token>",
        "ASTRA_DB_API_ENDPOINT": "<your-endpoint>"
      }
    }
  }
}
{
  "mcpServers": {
    "Dropbox Dash MCP": {
      "url": "https://mcp.dropbox.com/dash"
    }
  }
}
{
  "mcpServers": {
    "weaviate": {
      "url": "https://<your-weaviate-host>/v1/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.