Skip to main content
Back to the Glean MCP server

MCP Gateway · Claude Cowork

Glean icon

Connect Glean to Claude Cowork

Cowork is built for longer tasks, and many of them start with finding what the company already knows. With Glean synced in as a plugin, a session can search internal knowledge repeatedly as it researches, compares and writes. Each prompt goes to Speakeasy for an allow or deny decision before the step runs, and Cowork's OTLP export ties sessions to people.

Category
Productivity
Authentication
None
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Glean MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glean call inspected and logged.

Deploy on MCP Gateway

Set up

Add Glean to Claude Cowork in 4 steps

  1. 01

    Add Glean from the catalog

    An admin finds Glean in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Glean

    Give teams the mcp:connect scope on the Glean server through team access or a role. Claude Cowork connects to the Glean server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Glean from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Glean's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Glean

Consolidate scattered documentation

Ask Cowork to collect everything written about a process across teams, find where documents disagree, and write one consolidated draft for the owners to approve.

Assemble a quarterly business review

Cowork searches Glean for the quarter's project updates, launch notes and customer documents, then drafts the review deck outline with sources.

Prepare a request for proposal response

Hand Cowork an RFP and it works through each question, searching Glean for approved answers and prior responses, and drafts the full reply.

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Glean call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Glean tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Glean can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can Glean use in personal Claude accounts be governed?
No. Personal Claude accounts can't be governed in Cowork. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
Do new Cowork sessions see Glean plugin changes?
Yes. Cowork reads the synced repository, so a new session picks up plugin changes.
How do Claude Cowork users get Glean?
An admin adds Glean from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Glean tools their access allows.
Are Glean calls from Claude Cowork logged?
Yes. Glean calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Glean in other clients

AI everywhere.

Control here.