Skip to main content
Back to the DeepWiki MCP server

MCP Gateway · Codex

DeepWiki icon

Connect DeepWiki to Codex

Dependency bumps and new integrations both require reading code your team doesn't own. Codex can ask DeepWiki about a public GitHub repository and read its generated wiki while it reviews or writes a change, reaching it through the Speakeasy MCP Gateway. Codex hooks report every prompt and tool call to Speakeasy for an allow or deny decision, and the device agent keeps the configuration in sync on managed laptops.

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

Behind the MCP Gateway

Run DeepWiki MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add DeepWiki to Codex in 4 steps

  1. 01

    Add DeepWiki from the catalog

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

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

Review a dependency upgrade

When a pull request bumps an open source dependency, Codex asks DeepWiki about the affected areas of that repository and notes risks in the review.

ask_questionread_wiki_contents

Compare two candidate libraries

Codex reads the wikis for two public repositories you're choosing between and writes a short engineering note on how each is structured.

read_wiki_structureread_wiki_contents

Write an integration from the source

Codex asks DeepWiki how a public SDK's client is meant to be initialized, then writes the integration code to match what the repository does.

ask_question

Tools

3 tools

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

read_wiki_structure

Get a list of documentation topics for a GitHub repository.

read_wiki_contents

View documentation about a GitHub repository.

ask_question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response.

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to DeepWiki 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 DeepWiki lookups in Codex cloud tasks covered?
Codex cloud tasks and GitHub code review run off the device, so the plugin and OpenTelemetry don't cover them. OpenAI's Compliance Logs record them after the fact.
Can Codex spend be capped for sessions that use DeepWiki?
Spend limits can block Codex traffic once a budget is reached.
How do Codex users get DeepWiki?
An admin adds DeepWiki 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 DeepWiki tools their access allows.
Are DeepWiki calls from Codex logged?
Yes. DeepWiki 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

DeepWiki in other clients

AI everywhere.

Control here.