MCP Gateway · Codex
Connect Guru to Codex
A new service is easiest to document right after it is built, while the code is still open. Through the Speakeasy MCP Gateway, Codex can save that write-up to Guru as a draft card for review. Each person signs in through your identity provider, and agent hooks let Speakeasy allow or deny every Codex tool call.
- Category
- Communication
- Tools
- 6
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Guru MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Guru call inspected and logged.
Set up
Add Guru to Codex in 4 steps
- 01
Add Guru from the catalog
An admin finds Guru 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.
Guru uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
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.
- 02
Choose who can use Guru
Give teams the
mcp:connectscope on the Guru server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Guru to their gateway on the next call, and removing it takes it away. - 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' - 04
Sign in and use Guru from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Guru needs its own OAuth grant, so each person connects it once. Until they do, Guru calls fail while the rest of the gateway keeps working.
From then on, Guru'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 Guru
Draft the card for a new service
Once a service is merged, Codex writes a summary of what it does, how to run it and who owns it, and saves it to Guru as a draft card.
Read a card in full
When a ticket links to a Guru card, Codex fetches the full card content in its original HTML by ID, including tables and code samples a summary would drop.
Pick the right knowledge agent
Guru knowledge agents each cover different sources. Codex lists them, chooses the one for platform engineering, and searches its documents for the deploy checklist.
Tools
6 tools
Each Guru tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
guru_answer_generation
Generate direct answers to questions using the knowledge base. Use when users ask specific questions ('What is X?', 'How do I Y?'). Provides comprehensive answers, not just documents.
guru_create_draft
Create a Draft of a Card in Guru. Use when the users ask to save the content to Guru using a Draft
guru_search_documents
Find and retrieve specific documents, sources or cards. Use when users want to discover existing content ('find me docs on X', 'do we have cards about Y'). Returns documents for browsing, not answers.
guru_update_card
Update the content of an existing card. Use when users want to modify existing card content.
guru_list_knowledge_agents
Get available knowledge agents and their IDs. Always call this first before using guru_search_documents or guru_answer_generation tools, as both require an agentId parameter. Each agent has different expertise areas and data sources configured.
guru_get_card_by_id
Get full card content in original HTML format by card ID
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 Guru call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Guru tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Guru 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
Does Codex keep its Guru configuration on managed laptops?
Do Guru drafts from Codex publish straight away?
How do Codex users get Guru?
Are Guru calls from Codex logged?
Connect more