Connect / Glean

Connect Glean to Telara

A Glean administrator can publish Telara as an OAuth remote-MCP action pack for Assistant and Agents. Employees use the centrally available actions while Telara enforces their individual access and action policies.

client_type: glean

The endpoint

Streamable HTTPhttps://api.telara.dev/v1/mcp

AuthOAuth 2.1 + PKCE with dynamic client registration

Rolling it out centrally

Glean’s official path is an admin-managed remote-MCP action pack. It is an enterprise deployment route, not a self-service public directory listing.

A Glean Admin opens Admin Console, then Platform > Actions > Add > Import tools from MCP server.

Enter the approved Telara Streamable HTTP endpoint and select OAuth with dynamic client registration.

Review the discovered Telara tools, enable the approved read and write capabilities for Assistant and/or Agents, and apply Glean role controls.

Publish the action pack, then run a test agent or Assistant request that uses an authorized Telara tool and verify the Telara audit event.

Before you commit to this

Verified template status is separate

Glean can import any compliant OAuth MCP server. Its Verified MCP templates are curated by Glean, so Telara is not a verified template until Glean completes its own validation.

Write tools remain governed

Glean can add its own role and human-in-the-loop controls. Telara separately evaluates every request against the employee’s organization membership and access or action policy.

Confirm it actually worked

The client's “connected” badge reports a successful handshake, not a tool call. Ask Glean something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=glean.

An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.

Support, privacy, and reviewer testing

The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.

For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.

Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.