Fix the Codex connection on a Mac
Use this workaround if Codex on a Mac cannot finish Data Parrot authentication or load its tools.
Try the standard Codex app setup steps before using this workaround.
Apply the workaround
Quit Codex completely
With Codex open, press Command-Q. Closing the window is not enough.
Set the certificate path
Open Terminal, run this command, and press Return:
Mac connection workaroundlaunchctl setenv CODEX_CA_CERTIFICATE /etc/ssl/cert.pemTerminal does not normally show a success message. When the prompt returns, the command has finished. This does not turn off security checks. It tells Codex to use the certificate file already on your Mac.
Reopen Codex and authenticate
Open Codex, then go to Settings → Plugins → MCPs. Find Data Parrot, select Authenticate, and complete the sign-in in your browser.
Confirm the connection
Start a new Codex task and enter:
Codex MCP command/mcpConfirm that
data_parrot_mcpshows as connected.
If Authenticate still does not work
Quit Codex with Command-Q, open Terminal, and run:
CODEX_CA_CERTIFICATE=/etc/ssl/cert.pem /Applications/Codex.app/Contents/Resources/codex mcp login data_parrot_mcpKeep data_parrot_mcp exactly as written. Complete the Data Parrot sign-in in your browser, then reopen Codex and start a new task.
If Terminal says that the file or MCP server cannot be found, contact Data Parrot support and include a screenshot of the message.
After you restart your Mac
The setting lasts for your current Mac login session. If you restart your Mac or log out, apply the workaround again.
You should not need to sign in to Data Parrot again unless Codex asks you to authenticate.
Remove the workaround
Quit Codex with Command-Q, open Terminal, and run:
launchctl unsetenv CODEX_CA_CERTIFICATEReopen Codex.
Still can't connect?
Contact Data Parrot support and include:
- A screenshot of the message in Codex or Terminal
- Your Mac version
- Your Codex version from Codex → About Codex
- Whether
data_parrot_mcpappears under Settings → Plugins → MCPs