Performance Hub LogoPerformance Hub

Connect Glean to Performance Hub

Instructions current as of 17 June 2026 (AEST). Vendor MCP support changes frequently - verify against the linked sources if something looks different.

Glean, the enterprise search and AI agent platform, has documented support for connecting remote MCP servers.

Performance Hub MCP server:

https://app.performancehub.co/mcp

Glean setup

In Glean Admin, configure Performance Hub as a remote MCP server / action pack:

FieldValue
MCP server URLhttps://app.performancehub.co/mcp
TransportStreaming HTTP / Streamable HTTP
AuthenticationAPI key or OAuth, depending on your Glean configuration

Recommended auth: API key as bearer token

Glean's documented API-key mode sends the configured key as a bearer token in the Authorization header, which works with Performance Hub:

Authorization: Bearer YOUR_PERFORMANCE_HUB_MCP_KEY

Do not use x-mcp-api-key in Glean unless Glean adds documented support for arbitrary API-key header names in your tenant.

OAuth option

Glean documents OAuth modes for remote MCP servers, including admin/user OAuth and client credentials, depending on server support.

Performance Hub MCP OAuth metadata is available under:

https://app.performancehub.co/mcp/.well-known/oauth-protected-resource
https://app.performancehub.co/mcp/.well-known/oauth-authorization-server

Use OAuth only after testing the flow in Glean.

Tool selection

Publish only the tools the Glean agent needs. Large tool sets consume context and can reduce tool-selection accuracy.

Recommended starting set:

  • user_get_profile
  • facility_get_config
  • The specific module tools required for the use case

Agent instruction recommendation

Use Performance Hub tools only when the user asks for Performance Hub data or actions. Confirm before state-changing actions. Use read-only tools first and include the facility context in the answer.

Sources