Codex MCP: add, configure and debug MCP servers in Codex CLI
Originally published on vibeide.dev Codex can call tools from Model Context Protocol (MCP) servers: documentation lookups, browsers, design files, issue trackers and more. You add a server once, and the Codex CLI, the Codex app and the IDE extension all pick it up because they share one configuration. This guide shows the exact codex mcp commands and config.toml keys from the official Codex MCP…
Codex MCP allows the Codex CLI to access tools from Model Context Protocol (MCP) servers such as documentation lookups, browsers, design files, and issue trackers. To add an MCP server, use the command `codex mcp add` followed by the server name and either a command for a local (stdio) server or a URL for a remote (Streamable HTTP) server.
Once the server is added, start Codex and use `/mcp` to see the connected servers. MCP servers are stored in a configuration file, and can be added, configured, and debugged through various `codex mcp` commands. Configurations can be stored globally or in a project-specific file, with the latter offering more control over which servers are available in specific repositories.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
