Skip to main content
Back to the Ordinal MCP server

MCP Gateway · Codex

Ordinal icon

Connect Ordinal to Codex

Teams that report on social performance often want Ordinal numbers inside their own dashboards and scripts. Codex can pull those numbers while it writes the code that consumes them. With Ordinal behind Speakeasy's gateway, engineers authenticate once with your IdP, each team gets only the Ordinal tools its role needs, and every call is recorded in one audit log tied to a person.

Category
Productivity
Tools
63
Authentication
API key
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Ordinal MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Ordinal to Codex in 4 steps

  1. 01

    Add Ordinal from the catalog

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

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

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

Feed post analytics into a report

Ask Codex to fetch LinkedIn and X post analytics for a date range, inspect the response shape, and write the job that loads it into your reporting tables.

analytics-linkedin-postsanalytics-x-posts

Reproduce earned media value in code

Codex reads the CPM values Ordinal uses for each platform's EMV calculation, so your own report computes earned media value from the same inputs.

analytics-cpm-get

Debug a webhook that stopped firing

When your handler stops receiving Ordinal events, Codex fetches the webhook to check its URL and topics, then updates it to match the endpoint in your code.

webhooks-getwebhooks-update

Tools

63 tools

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

analytics-linkedin-followers

LinkedIn follower growth

analytics-linkedin-posts

LinkedIn post analytics

analytics-x-followers

X follower growth

analytics-x-posts

X post analytics

analytics-cpm-get

Get CPM Values

analytics-cpm-update

Update CPM Values

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Ordinal 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

Can engineers read Ordinal analytics in Codex without changing CPM values?
Yes. Tools are allowed or denied per team and role at the MCP Gateway, so a role can call analytics-cpm-get without analytics-cpm-update.
How do Ordinal tools reach a whole Codex 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.
How do Codex users get Ordinal?
An admin adds Ordinal 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 Ordinal tools their access allows.
Are Ordinal calls from Codex logged?
Yes. Ordinal 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

Ordinal in other clients

AI everywhere.

Control here.