MCP Gateway · Codex
Connect Vercel to Codex
Codex can chase a production error by reading the same function output your team would open in the Vercel dashboard. Behind Speakeasy's gateway, engineers authenticate once with your IdP, each team gets the Vercel tools its role needs, and every call lands in an audit log tied to a named person. An [otel] block in Codex's config sends session telemetry to Speakeasy.
- Category
- Developer tools
- Tools
- 18
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Vercel MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Vercel call inspected and logged.
Set up
Add Vercel to Codex in 4 steps
- 01
Add Vercel from the catalog
An admin finds Vercel 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.
Vercel 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.
- 02
Choose who can use Vercel
Give teams the
mcp:connectscope on the Vercel server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Vercel to their gateway on the next call, and removing it takes it away. - 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' - 04
Sign in and use Vercel from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Vercel needs its own OAuth grant, so each person connects it once. Until they do, Vercel calls fail while the rest of the gateway keeps working.
From then on, Vercel'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 Vercel
Trace a production error to code
Ask Codex for runtime logs from production, filtered by error level and time range, then have it match the logged output to the serverless function in your repository.
Find the right project in a monorepo
When one repository maps to several Vercel projects, Codex lists your teams and projects to get the IDs it needs before it reads any logs or deployments.
Look up platform behavior mid-change
When an edit touches caching, redirects, rewrites or cron jobs, Codex searches the Vercel docs and applies the guidance to the configuration it is changing.
Tools
18 tools
Each Vercel tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
search_vercel_documentation
Search the Vercel documentation.
deploy_to_vercel
Deploy the current project to Vercel
list_projects
List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.
get_project
Get a specific project in Vercel
list_deployments
List all deployments for a project
get_deployment
Get a specific deployment by ID or URL.
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 Vercel call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Vercel tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Vercel 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
Do Speakeasy's Codex hooks cover cloud tasks?
Which Vercel tools can a team call from Codex?
How do Codex users get Vercel?
Are Vercel calls from Codex logged?
Connect more