Glean MCP Server

MIT License

603

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description
`GLEAN_ACT_AS`	No	Email to impersonate when using global tokens (optional)
`GLEAN_INSTANCE`	No	Your Glean instance name
`GLEAN_API_TOKEN`	No	Your Glean API token with chat and search scopes
`GLEAN_SUBDOMAIN`	No	Your Glean subdomain (legacy, GLEAN_INSTANCE is preferred)

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

Functions exposed to the LLM to take actions

Name	Description
company_search	Find relevant company documents and data Example request: { "query": "What are the company holidays this year?", "datasources": ["drive", "confluence"] }
chat	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_search	Search for people profiles in the company Example request: { "query": "Find people named John Doe", "filters": { "department": "Engineering", "city": "San Francisco" }, "pageSize": 10 }

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gleanwork/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server