Skip to main content
Back to the Glean MCP server

MCP Gateway · Codex

Glean icon

Connect Glean to Codex

Codex does better work when it knows how your company does things. Glean gives it a search over enterprise knowledge, so a long task can pick up internal standards, architecture notes and prior decisions along the way. Speakeasy sees every prompt and tool call before Codex runs it, and an [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy.

Category
Productivity
Authentication
None
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Glean from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Glean

Apply the internal API style guide

When Codex adds an endpoint, it searches Glean for your company's API guidelines and follows them for naming, errors and versioning.

Learn the context before a migration

Before Codex moves a service to a new datastore, it searches Glean for earlier proposals and incident write-ups about that service and notes the risks in its plan.

Write onboarding docs for a repo

Ask Codex to draft a repository's contributing guide, pulling the setup steps and team practices it finds in Glean into one file.

Control

What Speakeasy can see and stop in Codex

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

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Are Glean searches from Codex cloud tasks recorded?
Codex cloud tasks run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Can only some teams use Glean in Codex?
Yes. The gateway decides which Glean tools each team can call, so engineering can have access that other roles don't.
How do Codex users get Glean?
An admin adds Glean from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Glean tools their access allows.
Are Glean calls from Codex 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.