Skip to Content
ResourcesIntegrationsSearch ToolsGlean

Glean

Glean icon
Arcade OptimizedBYOC

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

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

Glean Toolkit

Arcade toolkit that exposes the Glean Client API, enabling search over a Glean enterprise knowledge index on behalf of authenticated users.

Capabilities

  • Enterprise search: Query the Glean index and receive ranked, permission-filtered results scoped to the authorized user.
  • Pagination: Offset-based paging via offset and limit; has_next_page signals remaining results. Supported up to ~2 000 results (≈20 pages × 100 items); deeper offsets raise an explicit error.
  • Result budgeting: When the fetch budget is exhausted before the requested window is filled, the tool raises rather than returns a partial page. When items are large, the result list is trimmed to a size budget, flagged via truncated, with has_next_page kept accurate so callers can continue paging or narrow the query.

OAuth

Authentication uses OAuth 2.0 via Glean as the provider. Users must authorize the Arcade app through Glean's OAuth flow before search requests can be made on their behalf.

Secrets

  • GLEAN_API_URL — The base URL for your organization's Glean API endpoint (e.g., https://<your-org>.glean.com/api). Glean deployments are tenant-specific, so there is no single global URL. Obtain this value from your Glean administrator or from the Glean admin console under your organization's API settings. See Glean's API documentation for guidance on locating the correct endpoint for your tenant.

For configuring secrets in Arcade, see the Arcade secrets guide. You can also manage secrets directly 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