MCP Gateway · Codex
Connect Pulumi to Codex
Codex is a good fit for clearing the policy violations that pile up in an infrastructure repository. It reads open violations from Pulumi, fixes the program, and can hand larger jobs to Pulumi Neo and follow them. Agent hooks let Speakeasy allow or deny each prompt and tool call before Codex runs it, and budgets can stop Codex traffic once a limit is reached.
- Category
- Infrastructure
- Tools
- 14
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Pulumi MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Pulumi call inspected and logged.
Set up
Add Pulumi to Codex in 4 steps
- 01
Add Pulumi from the catalog
An admin finds Pulumi 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.
Pulumi 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 Pulumi
Give teams the
mcp:connectscope on the Pulumi server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Pulumi 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 Pulumi from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Pulumi needs its own OAuth grant, so each person connects it once. Until they do, Pulumi calls fail while the rest of the gateway keeps working.
From then on, Pulumi'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 Pulumi
Fix policy violations in a stack
Ask Codex for the open policy violations on a project's stack, then let it change the resource definitions that cause them and explain each fix in the commit.
Hand a migration to Pulumi Neo
Start a Neo task for a larger infrastructure change, read its messages as it works, and approve the next step only when you have checked the plan.
Find stacks matching a naming rule
Search for stacks whose names match a pattern, such as every staging stack, before Codex applies the same configuration change across them.
Tools
14 tools
Each Pulumi tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
get-stacks
Call this tool to list Pulumi stacks for the authenticated user and organization. , "stacks with 'prod' in the name", "stacks created after 2024", "show me stacks containing 'bob'"). Use resource-search instead for these filtered queries.
resource-search
Search and analyze Pulumi-managed cloud resources. This tool should be used to find stacks when the user query has a filter, such as "with name 'Bob'".
get-policy-violations
Get policy violations for Pulumi stacks. Use this tool to answer questions like: - "Do I have any policy violations?" - "What security issues are in my infrastructure?" - "Show me policy violations for my production stack" - "Are there any compliance issues in my project?"
get-users
List all users (members) in the organization. Use this when asked about users, members, admins, or team members.
neo-bridge
Launch and monitor Neo tasks step by step. Pulumi Neo is a purpose-built cloud infrastructure automation agent. If the JSON result has has_more=true, call this tool again to read more data. Continue calling until has_more=false.
neo-reset-conversation
Reset the Neo conversation for a specific task
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 Pulumi call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Pulumi tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Pulumi 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
Is Pulumi activity from Codex attributed to a person?
Can Codex approve a Neo task by itself?
How do Codex users get Pulumi?
Are Pulumi calls from Codex logged?
Connect more