Skip to main content
Glama
gleanwork

Glean MCP Server

by gleanwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GLEAN_ACT_ASNoEmail to impersonate when using global tokens (optional)
GLEAN_INSTANCENoYour Glean instance name
GLEAN_API_TOKENNoYour Glean API token with chat and search scopes
GLEAN_SUBDOMAINNoYour Glean subdomain (legacy, GLEAN_INSTANCE is preferred)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
company_searchC

Find relevant company documents and data

    Example request:

    {
        "query": "What are the company holidays this year?",
        "datasources": ["drive", "confluence"]
    }
chatC

Chat with Glean Assistant using Glean's RAG

    Example request:

    {
        "message": "What are the company holidays this year?",
        "context": [
            "Hello, I need some information about time off.",
            "I'm planning my vacation for next year."
        ]
    }
people_profile_searchC

Search for people profiles in the company

    Example request:

    {
        "query": "Find people named John Doe",
        "filters": {
            "department": "Engineering",
            "city": "San Francisco"
        },
        "pageSize": 10
    }

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: 'chat' is for conversational interaction with an assistant, 'company_search' is for finding documents and data, and 'people_profile_search' is for locating employee profiles. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

Naming Consistency4/5

The tool names follow a consistent snake_case pattern and are descriptive, but there is a minor deviation: 'chat' uses a simple verb, while the other two tools use a noun_noun structure (e.g., 'company_search'). This slight inconsistency does not hinder readability or predictability significantly.

Tool Count3/5

With only 3 tools, the set feels thin for a server named 'Glean MCP Server', which implies broader capabilities in information retrieval and assistance. While the tools cover chat, document search, and people search, the scope might benefit from additional tools for more granular operations or updates, making the count borderline appropriate.

Completeness3/5

The tools provide basic search and chat functionalities, but there are notable gaps. For example, there is no tool for updating or managing data (e.g., creating documents or modifying profiles), and the chat tool lacks explicit support for follow-up actions or context persistence. This limits the server's ability to handle full lifecycle operations in its domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources