How do I connect Zapier to OpenAI's Codex with MCP?
Codex can fix the bug, but it cannot file the ticket or tell the team. Zapier MCP changes that. Here is the setup for the Codex CLI and the ChatGPT desktop app, what it costs to run, and what we would hand it first.
By Lucas Mack, founder and CEO of SMGPPublished 7 minute read
The short answer
Run codex mcp add zapier with Zapier's connect URL in your terminal. A browser window opens so you can sign in to Zapier and click Allow. If no window opens, run codex mcp login zapier. Then type /mcp inside Codex and confirm Zapier is listed. Zapier creates and configures the server for you during sign-in, and every action from an app already connected to your Zapier account is ready to call. The ChatGPT desktop app and the IDE extension share the same configuration, so one setup covers all three.
Key takeaways
MCP is an open standard that lets an AI app call tools in other software. Zapier MCP turns the actions of your connected Zapier apps into those tools.
Codex needs one command and one browser sign-in. There is no server to build and no token to paste.
The Codex CLI, the IDE extension and the ChatGPT desktop app share one MCP configuration, so you connect Zapier once.
Each successful tool call uses two tasks from your Zapier plan, so enable the actions you will use and let Codex write only where a mistake is easy to undo.
Questionsbefore you start.
Short answers to what people ask before they run the first command. Anything else, ask below: the answer comes from this guide and the official docs.
Does Codex have to be installed and signed in before I add Zapier?
Yes. The add command is a Codex command, so the Codex CLI has to be on the machine and signed in with a ChatGPT account on a plan that includes Codex, or with an API key. Run codex --version in a terminal; if it prints a version, you are ready. The full list is in what you need before you start.
Do I need Node.js or npx for Zapier MCP?
No. Zapier MCP is a remote server that Codex reaches over Streamable HTTP, so nothing runs on your machine and there is no npx line to start. You need Codex, a terminal and a browser for the sign-in. Node.js only matters if you installed Codex through npm.
Should I connect my apps in Zapier before I run the command?
Connect at least one. The apps already connected to your Zapier account get their actions enabled the moment the server is created, so a Slack workspace or a scratch Google Sheet connected first gives you something to test right away. Pick an app where a mistake is easy to undo.
How long does the whole setup take?
A few minutes if Codex is already installed. The command takes seconds, the sign-in is a browser click on Allow, and the check is typing /mcp in a session. The steps are in how to connect Zapier to the Codex CLI.
Your earlier questions on this guide, kept in this browser.
Answers come from this guide and the official documentation, checked live, and follow-up questions build on the ones before. For anything bigger, contact our team.
How to connect Zapier to Codex with MCP, in about a minuteA video with no sound. Every word is on screen.Read the video transcript
SMGP explains. How to connect Zapier to Codex with MCP. In about a minute.
MCP is an open standard.
It lets an AI app call tools in other software.
Zapier MCP gives Codex hands in your apps.
Thousands of apps. Nothing to host. Zapier sets up the server when you sign in.
One command in the Codex CLI.
codex mcp add zapier --url, with the connect URL.
codex mcp login zapier if no browser opens. Then /mcp to confirm.
The ChatGPT app and the editor share the setup.
Add a Streamable HTTP server named zapier, restart, then Authenticate.
Then hand it the work after the code.
File the ticket for the bug you just fixed.
Post the release note to Slack.
Add a row to a Google Sheet.
Update a CRM contact after a call.
Each successful call uses two tasks from your Zapier plan.
Enable what you will use. Let it write only where a mistake is easy to undo.
A connector is a hand, not a system.
AI engineering builds the workflow that runs on its own.
SMGP. Embedded GTM engineering and embedded AI engineering. smgp.co
What is Zapier MCP, and why connect it to Codex?
Codex is OpenAI’s coding agent. It reads your project, edits files and runs commands in the terminal. What it cannot do on its own is reach the software the rest of your company runs on: the issue tracker, the team’s Slack, the CRM, the spreadsheet where someone tracks the releases. The Model Context Protocol (MCP) closes that gap. MCP is an open standard that lets an AI app call tools in other software, so the agent can act on those systems instead of only telling you what to do in them.
Zapier MCP is Zapier’s MCP server. It takes the actions of the apps connected to your Zapier account and offers them to Codex as tools. Zapier says it connects to more than 9,000 apps, which covers nearly every tool a small company pays for.
The part most people expect to be hard is the part Zapier removed. You do not build a server or paste a token into a config file. You run one command, sign in from the browser, and Zapier creates and configures the server for you during that sign-in.
What do you need before you start?
You need four things, and none of them takes long.
Codex installed and signed in. If it is not on your machine yet, our guide to installing the Codex CLI on Mac and Windows takes a few minutes. Codex signs in with a ChatGPT account on a plan that includes it, or with an API key.
A Zapier account. The Free plan works. Zapier MCP is included in every plan.
The apps you want Codex to use, connected in Zapier. Apps already connected to your account have their actions enabled the moment the server is created. If nothing is connected, the server starts empty, so connect your first app now or be ready to connect it when Codex asks.
A decision about what Codex may do. Reading a ticket is low risk. Posting to a channel or editing a contact is not. Give Codex the apps you would give a new teammate in week one, and add the rest once you trust the results.
How do you connect Zapier to the Codex CLI?
The connection starts with one command. Run it from any terminal where Codex is installed.
That line registers a remote MCP server named zapier that Codex reaches over Streamable HTTP. A browser window opens on Zapier’s authorization screen. Review the access Zapier is asking for, choose an account if you have more than one, and click Allow.
If no browser window opens, start the sign-in yourself.
codex mcp login zapier
Leave the server’s auth setting at its default, oauth. That way every call runs as you, signed in with your own Zapier account, rather than through a credential the whole team shares.
Zapier also offers a paste-in prompt for Codex on its Codex guide. Paste it into a Codex session and Codex runs the add command and the sign-in for you. The result is the same.
How do you set it up in the ChatGPT desktop app or your editor?
The Codex CLI, the IDE extension and the ChatGPT desktop app share one MCP configuration. If you added Zapier from the terminal, it is already there. If you prefer to start in the app, add a server by hand.
Open the MCP server settings in the ChatGPT desktop app or the Codex IDE extension.
Add a server named zapier.
Choose the transport Streamable HTTP.
Enter the URL https://mcp.zapier.com/api/v1/connect.
Restart the app or the extension.
Choose Authenticate on the Zapier entry and complete the sign-in in your browser.
In the ChatGPT desktop app, type /mcp in the composer to see the servers that are connected. ChatGPT on the web does not read your local Codex configuration, so the connection shows up in the desktop app and the CLI, not in a browser tab.
How do you check that it worked?
Inside a Codex session, type /mcp. Zapier should be in the list with its tools. If it shows as not authenticated, run the login command above and try again.
From the terminal, you can also list every MCP server Codex knows about.
codex mcp list
Then give it a harmless job. Ask Codex to post a short test message to a Slack channel you own, or to add one test row to a scratch spreadsheet, and look at the app. If the message or the row is there, the connection is live.
What can you do once it is connected?
The useful work is the work that used to happen after the code was done, in four other tabs. These are the asks we would hand it first.
File the ticket for the bug you just fixed. After Codex patches the code, ask it to open the Jira or Linear issue with the root cause and the fix, and to close it when the change ships.
Post the release note to Slack. Codex summarizes the change it made and posts it to the channel where the team reads release notes, without you leaving the session.
Create a Trello or Asana task from a code review. Every “we should also fix that” Codex notices becomes a card with an owner and a due date.
Add a row to a Google Sheet. Give Codex the details of a deploy, a test run or an expense, and it fills the columns the way the sheet expects.
Update a HubSpot or Salesforce contact after a call. Paste your notes, and the contact’s title, stage and next step are updated without opening the CRM.
Draft a Gmail reply. Codex reads the thread you paste, writes the answer, and saves it as a draft for you to send.
Look up a customer’s record before you change something. Ask which plan a client is on before Codex touches the feature flag, and it checks the system of record instead of guessing.
Each of these started life as a Zap somebody had to build and maintain. With MCP, you describe the outcome in the session, and Codex picks the action.
What does it cost to run?
Zapier MCP is included in every Zapier plan, so there is nothing extra to buy. Usage counts against the task quota your plan already has. Each successful tool call uses two tasks, and a call that fails costs nothing.
The Free plan includes 100 tasks a month, which works out to about 50 tool calls. That is enough to connect an app and try every use case above. Paid plans include more tasks and can switch to pay-per-task billing when you pass the limit.
The cost that matters more is attention. A single call is cheap, but an agent that reads a ticket, updates it, posts about it and files a follow-up has made four calls. Enable the actions you will actually use, prefer read actions for research, and let Codex write to a system only where a mistake is easy to undo.
Where does Zapier fit next to n8n?
Zapier MCP is the fastest way to give a coding agent hands in the apps your company already uses. There is nothing to host, the sign-in takes a minute, and the actions are already written.
n8n is what we run our own company on. We do not use Zapier internally. When a workflow needs branching, loops, a few lines of code or a server you control, n8n is the better fit, and it has an MCP server of its own. The full comparison, including how each one bills and which one we recommend, is in n8n vs Zapier. If you want Codex connected to n8n instead, the steps are in how to connect n8n MCP to Codex.
The same pairing works on the Claude side. If your team builds in Claude Code, the guide to connecting n8n to Claude with MCP walks through both of n8n’s servers.
Where does this fit in an AI-run company?
AI engineering is the work of pointing AI at how a company runs: the finance, the reporting, the company memory and the internal tools. Connecting Zapier to Codex is a small, concrete piece of that work. It takes an agent that can only change code and gives it a way to act in the systems around the code, under a person’s eye.
That is also where it stops. A connector is a hand, not a system. The next step is a workflow that runs on its own, with AI doing the repetitive work and a person making the decisions that matter. That is what an embedded AI engineer builds, and how SMGP runs on AI shows what it looks like once a whole company works that way.
Written by Lucas Mack
Lucas is the founder and CEO of SMGP. He has done every job in the company, runs the strategy and the sales, and built every system SMGP runs on, from the outbound engine to the finance software. He writes about what he builds and what he has learned building it.
Do I need a paid Zapier plan to use Zapier MCP with Codex?
No. Zapier MCP is included in every Zapier plan, and the Free plan includes 100 tasks a month. Each successful tool call uses two tasks, so the Free plan gives you about 50 tool calls a month to try it with. Paid plans add more tasks.
Do I have to create the server on Zapier's site first?
No. For Codex, Zapier creates and configures the server during the browser sign-in. Creating a server on Zapier's site first is only needed for code-based integrations and for clients Zapier does not list, which use a connection token instead.
Does Codex see my Zapier password?
No. You sign in on Zapier's own authorization screen, and Codex receives permission to call only the actions you allowed. Leave the server's auth setting at its default, oauth, so every call runs as you rather than through a shared credential.
Which apps will Codex be able to use?
Any app already connected to your Zapier account has its actions enabled when the server is created. If nothing is connected yet, the server starts empty. Once you connect an app in Zapier, Codex can turn on the action it needs during the same request.
Will the connection also work in the ChatGPT desktop app and my editor?
Yes. The Codex CLI, the IDE extension and the ChatGPT desktop app read the same MCP configuration. Add Zapier once from the terminal, or add it in the app as a Streamable HTTP server, restart, and choose Authenticate on the Zapier entry.
Thirty minutes on your business: where a GTM engineer or an AI engineer would make the biggest difference, and what to build first. You leave with a plan either way.