Skip to main content
Back to the Pylon MCP server

MCP Gateway · Codex

Pylon icon

Connect Pylon to Codex

Codex can work through a queue of customer-reported bugs, using Pylon as the record of what customers actually saw. It reads support issues and contact details through the Speakeasy MCP Gateway, and agent hooks let Speakeasy allow or deny each prompt and tool call before Codex runs it.

Category
Productivity
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Pylon MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Pylon to Codex in 4 steps

  1. 01

    Add Pylon from the catalog

    An admin finds Pylon 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.

    Pylon 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.

  2. 02

    Choose who can use Pylon

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

    The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Pylon needs its own OAuth grant, so each person connects it once. Until they do, Pylon calls fail while the rest of the gateway keeps working.

    From then on, Pylon'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 Pylon

Turn support issues into test cases

Give Codex a Pylon issue and let it read the conversation, write a failing test that reproduces what the customer described, and then make the test pass.

Batch fixes for one account

Query the open Pylon issues for a single customer account, group the ones that point to the same code path, and fix them in one branch.

Find the right contact for a beta

When a fix needs confirmation, look up the account's contacts in Pylon so you know who to ask to try the beta build.

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Pylon 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 need its own Pylon login?
No. Codex signs in to the gateway, and every session authenticates with OAuth 2.1 through your identity provider. Agents never hold a Pylon credential.
Who can roll Pylon out to a Codex team?
A ChatGPT Business, Enterprise or Edu 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.
How do Codex users get Pylon?
An admin adds Pylon 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 Pylon tools their access allows.
Are Pylon calls from Codex logged?
Yes. Pylon 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

Pylon in other clients

AI everywhere.

Control here.