Skip to main content
Back to the Grain MCP server

MCP Gateway · Codex

Grain icon

Connect Grain to Codex

Design reviews and architecture calls decide a lot that never reaches the docs. Through the Speakeasy MCP Gateway, Codex can open the Grain notes from those meetings and check a change against what the team agreed. Agent hooks let Speakeasy allow or deny each Codex tool call, and sign-in runs through your identity provider.

Category
Productivity
Tools
22
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Grain MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Grain to Codex in 4 steps

  1. 01

    Add Grain from the catalog

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

    Grain 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 Grain

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

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

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

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

Check a change against the decision

Point Codex at last week's design review. It finds the meeting and reads Grain's AI notes, then flags anything in your diff that contradicts what was decided.

list_meetingsfetch_meeting_notes

Fall back to the full transcript

Older meetings may not have AI notes. Codex fetches the meeting by ID and reads the transcript instead, so a migration plan from months ago is still usable.

fetch_meetingfetch_meeting_transcript

Find which customers raised an issue

Before deprecating an endpoint, ask Codex which companies and people mentioned it on recorded calls, so you know who to warn about the change.

search_companiessearch_persons

Tools

22 tools

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

myself

Get information about the logged-in Grain user.

list_meetings

Returns a filtered list of Grain meetings you have access to, ordered by most recent.

list_attended_meetings

Returns a filtered list of Grain meetings you have attended, ordered by most recent.

fetch_meeting

Fetches information about a single Grain meeting by ID. The response format is the same as is returned by list_meetings.

fetch_meeting_notes

Fetches the AI notes payload from a single Grain meeting by ID. In some cases, older meetings may not have had notes generated for them. In these cases you can use fetch_meeting_transcript instead to determine the content of the meeting.

fetch_meeting_action_items

Fetches the action items extracted from a single Grain meeting by ID. Action items include the task description, timestamp, status (pending or completed), due date, and the person assigned to the action item (if any).

See all 22 tools

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Grain 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 Grain access cover Codex cloud tasks?
Codex cloud tasks run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Which Grain meetings can Codex read?
Only meetings the signed-in Grain user has access to. Tools such as list_meetings and search_persons return results from meetings that person can already see in Grain.
How do Codex users get Grain?
An admin adds Grain 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 Grain tools their access allows.
Are Grain calls from Codex logged?
Yes. Grain 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

Grain in other clients

AI everywhere.

Control here.