Codex
Before you start
Use this guide on the computer where Codex runs. A terminal inside a hosted chat sandbox does not configure your desktop client. You need Codex installed and access to the intended Simplified workspace; Node.js and npm are needed only for the skills installer below.
If Simplified tools already work through an installed app or plugin, reuse that connection and go to verification. Do not add a second server for the same working integration.
1. Inspect and connect
In your local terminal:
If Simplified is missing, add the hosted server:
2. Sign in
Use the existing server’s name if it differs. Complete the Simplified sign-in in the browser, then return to Codex. Never paste your password or OAuth token into the conversation.
For a client that needs an API key, use the environment-variable option described in MCP authentication. A terminal’s environment may differ from the desktop app’s environment.
3. Add skills if needed
Skills provide reusable instructions for campaigns, content production, and reporting. They do not authenticate the connector. If a Simplified plugin already supplies them, skip this installation.
Inspect the available skills:
Install for Codex across projects:
For project-only installation, run the command in that project and omit --global. Review the installer’s prompts. Start a new Codex session afterward if the skills are not visible.
Verify the connection
Start a new conversation if the client has not loaded the new tools. Ask:
Use Simplified to identify my connected workspace and list its teamspaces. Do not create or change anything.
The assistant should call api_getWorkspaceInfo and api_listTeamspaces, then report the workspace and available teamspaces. Choose the intended teamspace before starting work. A saved server entry or a successful skills installation alone does not verify tool access.
Next, follow the MCP quickstart to prepare a social draft. For a read-only first task, ask the assistant to list your brand kits. Social accounts are only needed for social tasks; an empty account list does not mean the connection failed.
Troubleshooting and updates
- The server exists but requires authentication: use
codex mcp loginwith its actual name. - Tools appear in the CLI but not the app: confirm both use the same local user/configuration and that the app has reloaded the connection.
- Skills are present but tools are absent: verify the MCP connection separately; skills installation is not server setup.
- A capability is missing: check tool availability. Do not create another connection merely to change the tool count.
Update a plugin through the mechanism that installed it. For separately installed skills, inspect npx skills --help for supported update options. Keep an existing working connection when refreshing instructions.