Skip to main content
Glama
glean-company-docs

glean-company-docs

Halcyon Docs Chatbot

Grounded question answering over a local document corpus, built on Glean's Indexing, Search and Chat APIs and exposed as a single MCP tool.

How it works

Read — a question arrives

flowchart TD
    Z["MCP client — POST /mcp, streamable HTTP"] --> A["MCP tool: ask_company_docs"]
    A --> C["search() — Active documents only"]
    C --> D{"results ≥ 1,<br>and passages carry text?"}
    D -->|no| E["grounded refusal — Chat is never called"]
    D -->|yes| F["generate() — Chat, with retrieval disabled"]
    F --> G["resolve_citations()"]
    E --> H["Answer: answer, sources, diagnostics"]
    G --> H

Write — extraction and indexing

flowchart TD
    U["glean-index (CLI)"] --> C["extract() — one adapter per format"]
    C --> D{"body ≥ GLEAN_MIN_BODY_CHARS?"}
    D -->|no| E["skipped as an extraction failure"]
    D -->|yes| F["ensure_datasource()"]
    F --> G["bulk_index() in pages of 50<br>POST /api/index/v1/bulkindexdocuments"]

Related MCP server: mcp-business-bot

Configuration

Everything is configured through one .env file, read by both the containers and the Poetry entrypoints.

cp .env.example .env      # then fill in the tokens

Variable

Used by

Notes

GLEAN_INSTANCE

both

SDK builds https://{instance}-be.glean.com

GLEAN_INDEXING_TOKEN

indexing only

never loaded on the query path

GLEAN_CLIENT_TOKEN

search + chat

scope Chat/Search, type Global

GLEAN_DATASOURCE

both

shared sandbox, so this namespaces doc IDs

GLEAN_DOCS_ROOT

indexing only

corpus root; also the host side of the indexer's bind mount

GLEAN_ACT_AS

search + chat

email to act as; required for Global tokens

Optional, with defaults: GLEAN_DOC_ID_PREFIX (halcyon), GLEAN_TOP_K (5), GLEAN_MAX_SNIPPET_SIZE (2000), GLEAN_MIN_RESULTS (1), GLEAN_MIN_BODY_CHARS (200), GLEAN_CHAT_TIMEOUT_MS (60000), MCP_PORT (8000), MCP_ALLOWED_HOSTS.

Usage

Three steps, once .env is filled in: index the corpus, start the server, point an MCP client at it. Only step 1 is repeated, whenever the corpus changes.

1. Indexing

The indexer is a separate compose service (the write path) behind the index profile, so it never starts with the server. Run it on demand:

docker compose run --rm indexer                         # extract and push to Glean

Indexing is asynchronous. The command returns once Glean has accepted the documents, and they stay unsearchable for several minutes after that. Add --process-now to ask Glean to process immediately — rate limited to once per three hours per datasource.

Re-running is idempotent: the bulk upload replaces the datasource contents as a unit. The corpus is bind-mounted read-only from GLEAN_DOCS_ROOT, so editing a document on the host and re-running picks it up with no rebuild.

2. Start the MCP server

docker compose up --build          # foreground, logs to the terminal
docker compose up -d --build       # background

3. Connect an MCP client

The client needs the URL and nothing else — the Glean token lives with the server, not the client.

Claude Code

claude mcp add --transport http glean-company-docs http://127.0.0.1:8000/mcp

Then /mcp inside Claude Code lists the server and its one tool.

Cursor — ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "glean-company-docs": {
      "type": "http",
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

Claude Desktop — Settings → Connectors → Add custom connector, with the same URL. On a build that only speaks stdio, bridge it:

{
  "mcpServers": {
    "glean-company-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://127.0.0.1:8000/mcp"]
    }
  }
}

Restart the client after editing its config. Then ask it something the corpus covers — "how much PTO does a Level 6 employee get?" — and it should call ask_company_docs rather than answering from its own knowledge.

Demo Flow

  1. "How many PTO days do I get?" → 18, cited to HR-004

  2. "What corporate card do we use?" → Ramp, not Brex — then "What's the meal per diem for domestic travel?" → $75, not $50

  3. "How long do I have to submit an expense?" → 30 days

  4. "What's our 401k employer match?" → grounded refusal, Chat never called

  5. "Show me the diagnostics from that last tool call"

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers