Codex

Install the display.dev Codex plugin to add the publishing skill and remote MCP connection together.

Install the plugin

1. Add the display.dev plugin marketplace:

   shCopy

   codex plugin marketplace add display-dev/skill

2. Open /plugins in Codex and install display.dev.

3. Complete MCP OAuth when Codex prompts you. The plugin and its publishing tools are available in new tasks after authentication.

Configure remote MCP directly

If you only want the remote MCP server, configure it in ~/.codex/config.toml:

1. Generate an API key at app.display.dev/settings/api-keys. Keys start with sk_live_….

2. Set DISPLAYDEV_API_KEY=sk_live_... in your shell profile. Codex reads it on session start.

3. Add:

   tomlCopy

   [mcp_servers.display]
   url = "https://api.display.dev/v1/mcp"
   bearer_token_env_var = "DISPLAYDEV_API_KEY"

4. Exit the Codex session (Ctrl+D or /exit) and start a new one. Codex caches MCP server registrations at session start; hot-reload is not supported.

Configure local stdio

If you already have the CLI (npm install -g @displaydev/cli + dsp login):

[mcp_servers.display]
command = "dsp"
args = ["mcp"]

To point at a non-production environment, add an env sub-table:

[mcp_servers.display]
command = "dsp"
args = ["mcp"]
 
[mcp_servers.display.env]
DISPLAYDEV_API_URL = "https://api.staging.display.dev"

Approval prompt

Codex can prompt before it invokes MCP tools, based on the server's tool approval mode. To preapprove tools from display, set default_tools_approval_mode = "approve" under [mcp_servers.display].