Skip to main content
Back to the Glean MCP server

MCP Gateway · Claude Code

Glean icon

Connect Glean to Claude Code

The answer to "why is it built this way?" is often in a design doc or a past discussion, not the code. With Glean behind the Speakeasy gateway, Claude Code can search your company's knowledge from the terminal before it changes anything. Agent hooks check each tool call with Speakeasy first, and the OpenTelemetry exporter ties each session to a named developer.

Category
Productivity
Authentication
None
Claude Code
CLI

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 Code 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. The organization gateway works out each person's servers from their live access, so granting access adds Glean to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Glean from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Glean

Find the design doc behind a service

Before refactoring an unfamiliar service, ask Claude Code to search Glean for its design doc or decision record, so the change respects the original constraints.

Follow the internal runbook

When a deploy step fails, Claude Code searches Glean for the team's runbook on that system and walks through the documented fix instead of improvising.

Check internal conventions while coding

Ask Claude Code how your company names metrics or structures config, and it looks up the internal guideline in Glean before writing the code.

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Does each developer need Glean credentials in Claude Code?
No. Each session authenticates through your identity provider, and agents never hold a Glean credential. Access ends when the employee leaves the directory.
Can Glean search results carry prompt injection into Claude Code?
Prompt injection detection and PII redaction run on every Glean tool call at the gateway. Agent hooks can also deny a tool call before Claude Code runs it.
How do Claude Code users get Glean?
An admin adds Glean from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Glean tools their access allows.
Are Glean calls from Claude Code 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.