Glean
Arcade MCP server exposing Glean Client API search over custom OAuth2.
0.2.0The Glean toolkit connects Arcade to a Glean enterprise deployment, exposing the Glean Client API so agents can search an organization's indexed content with results permission-filtered to the authenticated user.
Capabilities
- Enterprise search — Query the Glean index via
Glean.Search; results are ranked and scoped to the authorized user's permissions. - Pagination — Supports offset/limit paging (up to ~2000 results, ~20 pages × 100 items);
has_next_pagesignals more results; offsets beyond the supported range raise an explicit error. - Result-size budgeting — Response payloads are trimmed when items are large;
truncatedflags a trimmed page whilehas_next_pageremainstrueso callers can continue paging or narrow their query. - Fail-loud semantics — The tool raises an error rather than return a partial or misleading page when the fetch budget is exhausted or an unsupported offset is requested.
OAuth
This toolkit uses OAuth 2.0 against a custom/self-hosted Glean OAuth provider. Because the provider ID is specific to your Glean deployment, consult your Glean administrator for client credentials and authorization endpoint details. Arcade's general OAuth provider reference is at https://docs.arcade.dev/en/references/auth-providers.
Secrets
GLEAN_API_URL— The base URL of your organization's Glean API endpoint (e.g.,https://<your-deployment>.glean.com/api). This value is deployment-specific and is not the public Glean website. Obtain it from your Glean administrator or from the Glean admin console under Setup → API (exact path may vary by Glean version). It is required so the toolkit knows which Glean instance to route requests to.
Store secrets in Arcade using the Arcade secrets guide or manage them directly at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(1)
| Tool name | Description | Secrets | |
|---|---|---|---|
Search the user's Glean enterprise index and return ranked results.
Results are permission-filtered to the authorized user. Use 'offset' with
'limit' to page; 'has_next_page' indicates more results remain. Offset
paging is supported up to roughly 2000 results (20 pages x 100 items);
deeper offsets raise an error rather than return a misleading empty page.
When the fetch budget is exhausted before the requested window is filled,
the tool raises rather than return a partial page (fail loud over mislead).
The result list is trimmed to a size budget when items are large;
'truncated' flags it and 'has_next_page' stays true so the caller can page
or narrow the query. | 1 |
Selected tools
No tools selected.
Click "Show all tools" to add tools.
Requirements
Select tools to see requirements
Glean.Search
Execution hints
Signals for MCP clients and agents about how this tool behaves.
Reads data without modifying any state in the target system.
May permanently delete or overwrite data in the target system.
Repeated calls with the same inputs produce no additional effect.
Communicates with external APIs, databases, or other services.
Search the user's Glean enterprise index and return ranked results. Results are permission-filtered to the authorized user. Use 'offset' with 'limit' to page; 'has_next_page' indicates more results remain. Offset paging is supported up to roughly 2000 results (20 pages x 100 items); deeper offsets raise an error rather than return a misleading empty page. When the fetch budget is exhausted before the requested window is filled, the tool raises rather than return a partial page (fail loud over mislead). The result list is trimmed to a size budget when items are large; 'truncated' flags it and 'has_next_page' stays true so the caller can page or narrow the query.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
query | string | Required | Natural-language search query to run against the user's Glean index. |
limit | integer | Optional | Maximum number of results to return (1-100). Defaults to 10. |
offset | integer | Optional | 0-indexed position of the first result to return. Defaults to 0 (first result). |
Requirements
Output
json— Ranked Glean results plus pagination metadata. 'has_next_page' is true when more results are available (page with a larger 'offset'); 'truncated' is true when the result list was trimmed to fit a response-size budget.