Skip to main content
Back to the Ramp MCP server

MCP Gateway · Codex

Ramp icon

Connect Ramp to Codex

Platform engineers building internal finance tooling can use Ramp as a live data source while Codex writes and tests the code that consumes it. Spend data arrives through the Speakeasy MCP Gateway, and Speakeasy gets a say on every prompt and Ramp request first, approving or rejecting it before Codex acts.

Category
Sales & CRM
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Ramp MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Ramp to Codex in 4 steps

  1. 01

    Add Ramp from the catalog

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

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

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

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

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

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

Prototype a spend dashboard

Ask Codex to read a sample of Ramp spend data, design the schema for an internal dashboard, and build the first version against real figures.

Validate a cost allocation script

When Codex changes the script that splits shared costs across teams, it checks the output against Ramp's own spend totals before you merge.

Answer a finance ticket from the terminal

When finance asks engineering why a tool's cost doubled, Codex reads the Ramp spend history for that vendor and drafts the explanation.

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Ramp 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 store a Ramp credential?
No. Sessions authenticate with OAuth 2.1 through your identity provider, and agents never hold a Ramp credential. Access ends when the employee leaves the directory.
Is Ramp data from Codex cloud tasks covered by hooks?
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 Ramp?
An admin adds Ramp 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 Ramp tools their access allows.
Are Ramp calls from Codex logged?
Yes. Ramp 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

Ramp in other clients

AI everywhere.

Control here.