Skip to main content
Back to the Glyphic MCP server

MCP Gateway · Codex

Glyphic icon

Connect Glyphic to Codex

Engineering teams using Codex can bring the customer's voice into a task. Glyphic holds sales call recordings, transcripts and deal insights, so Codex can read what buyers said about a feature while it plans or builds. Agent hooks let Speakeasy approve or block each prompt and tool call before Codex acts on it, and budgets can cap Codex spend.

Category
Sales & CRM
Authentication
API key
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Glyphic MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Glyphic to Codex in 4 steps

  1. 01

    Add Glyphic from the catalog

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

    Glyphic authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.

    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 Glyphic

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

Write acceptance criteria from calls

Codex reads the transcripts of the deals that asked for a feature and turns the buyers' requirements into acceptance criteria in the ticket or spec file.

Prioritize integration work by deals

Ask Codex which third-party integrations come up most in deal insights, then order the integration backlog in the repo's roadmap file by that demand.

Draft a technical answer for sales

When a call left a technical question open, Codex reads the transcript, checks the code for the answer, and drafts a reply the account team can send.

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Glyphic 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 Codex cloud tasks that use Glyphic covered?
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 engineering read Glyphic without seeing everything sales sees?
The gateway decides which Glyphic tools each team can call, so engineering can get the access its role needs and nothing more. PII redaction also runs on every Glyphic tool call.
How do Codex users get Glyphic?
An admin adds Glyphic 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 Glyphic tools their access allows.
Are Glyphic calls from Codex logged?
Yes. Glyphic 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

Glyphic in other clients

AI everywhere.

Control here.