Skip to main content
Back to the Context7 MCP server

MCP Gateway · Codex

Context7 icon

Connect Context7 to Codex

Codex writes and reviews code against libraries that change faster than any model's training data. Context7 gives it current documentation and code examples for those libraries, and the Speakeasy MCP Gateway gives the team one governed URL for it. Agent hooks check each prompt and tool call before Codex runs it, and spend limits can block Codex traffic once a budget is reached.

Category
Developer tools
Tools
2
Authentication
None
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Context7 MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Context7 to Codex in 4 steps

  1. 01

    Add Context7 from the catalog

    An admin finds Context7 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 Context7

    Give teams the mcp:connect scope on the Context7 server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Context7 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 Context7 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, Context7'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 Context7

Review a changed call against the docs

During review, Codex checks a changed library call against the documentation and flags arguments or patterns the docs don't describe.

query-docs

Scaffold a service on a new framework

Starting a service on a framework your team hasn't used, Codex resolves it in Context7, reads the setup guide and examples, and writes the first routes from them.

resolve-library-idquery-docs

Check for a built-in before writing helpers

Before writing a helper by hand, ask Codex to search the library's documentation for an existing function that already does the job.

query-docs

Tools

2 tools

Each Context7 tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.

resolve-library-id

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

query-docs

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.

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 Context7 call is logged with the person and the client that made it.

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Context7 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

Do Codex cloud tasks use the same Context7 controls?
No. Codex cloud tasks and GitHub code review run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Can a role be denied Context7 in Codex?
Yes. Both Context7 tools can be allowed or denied per team and role at the MCP Gateway.
How do Codex users get Context7?
An admin adds Context7 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 Context7 tools their access allows.
Are Context7 calls from Codex logged?
Yes. Context7 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

Context7 in other clients

AI everywhere.

Control here.