Skip to Content
ResourcesIntegrationsSearch ToolsGlean

Glean

Glean icon
Arcade OptimizedBYOC

Arcade MCP server exposing Glean Client API search over custom OAuth2.

Author:Arcade
Version:1.0.0
Auth:User authorization
1tools
1require secrets

Glean Toolkit

Arcade toolkit that exposes the Glean Client API, enabling search over a company's Glean enterprise index with results permission-filtered to the authenticated user.

Capabilities

  • Enterprise search: Query the Glean index and retrieve ranked, permission-filtered results scoped to the authorized user.
  • Pagination: Page through results using offset and limit; has_next_page signals additional pages. Offset paging is supported up to ~2 000 results (e.g. 20 pages × 100 items); deeper offsets raise an error instead of returning a misleading empty page.
  • Result trimming and transparency: When the fetch budget is exhausted before the requested window is filled, or when result items are large and the list is trimmed to a size budget, the tool raises or sets truncated: true and keeps has_next_page: true — failing loud rather than silently returning incomplete data.

OAuth

Authentication uses OAuth 2.0 via the Glean provider. Users must authorize through Glean's OAuth flow before searches are executed on their behalf.

Secrets

  • GLEAN_API_URL — The base URL for your organization's Glean Client API endpoint (e.g. https://<your-tenant>-be.glean.com). This is tenant-specific and can be found in your Glean admin or developer settings. Refer to your Glean workspace administrator or the Glean developer documentation to locate the correct endpoint for your deployment.

See the Arcade secrets guide for how to configure secrets, and manage them at https://api.arcade.dev/dashboard/auth/secrets.

Available tools(1)

1 of 1 tools
Operations
Behavior
Tool nameDescriptionSecrets
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
Last updated on