Skip to main content
Back to the Cube MCP server

MCP Gateway · Codex

Cube icon

Connect Cube to Codex

Engineering decisions go better with data behind them. With Cube behind the Speakeasy MCP Gateway, Codex can explore analytics data and surface insights while it works on a change, and generate SQL for jobs that need it. Agent hooks check each prompt and tool call before Codex runs it, and the device agent keeps Codex's configuration in sync on managed laptops.

Category
Data & analytics
Authentication
None
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Cube MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Cube to Codex in 4 steps

  1. 01

    Add Cube from the catalog

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

    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 Cube

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

Back a pull request with data

For a pull request that changes an onboarding or checkout flow, Codex explores Cube data on how that flow is used today and adds the findings to the description.

Draft SQL for a scheduled job

Codex asks Cube to generate the SQL for a scheduled export or data job, then wires the query into the code so a reviewer can check it.

Investigate a metric drop

When an alert says a metric fell, Codex explores the analytics data in Cube and reports which part of the data changed, so you know where to look in the code.

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

Access by role

Gateway

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

Request and response blocking

Gateway

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

How do I attribute Cube activity in Codex to a developer?
Add an [otel] block to ~/.codex/config.toml to send telemetry to Speakeasy. Export is off by default.
Are Codex cloud tasks that use Cube governed by the plugin?
No. Codex cloud tasks run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
How do Codex users get Cube?
An admin adds Cube 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 Cube tools their access allows.
Are Cube calls from Codex logged?
Yes. Cube 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

Cube in other clients

AI everywhere.

Control here.