cv usk(@cv_usk):# Codex Features and Practical Usage 🔌 Turn Codex from an agent that only touches code into a partner that drives your issue tracker, database, and design tools directly. The key is MCP (Model Context Protocol). 🏷️ Title: External Tool Connectivity (MCP) 🔗 URL: https://t.co/tGkpMGGHQI 📘 Overview MCP is the standard protocol that connects Codex to external tools and context. Register an MCP server and Codex can call that tool directly to read and write. Configuration is shared across the CLI and IDE extension, so the same setup works no matter which client you use. ⚙️ How It Works ・The simplest way to add a server is via the CLI: `codex mcp add <name> -- <startup-command>`. Inside the TUI, `/mcp` lists your active servers. ・There are two transports: STDIO servers, which start a local process (configure `command`, `args`, `env`, `cwd`), and Streamable HTTP servers, accessed by URL (configure `url`, `bearer_token_env_var`, `http_headers`). ・Authentication supports Bearer tokens sourced from environment variables, or OAuth. For OAuth-capable servers, run `codex mcp login <name>`. ・You can govern tools per server: `enabled_tools` / `disabled_tools` for allow and deny lists, and `default_tools_approval_mode` (`auto`/`prompt`/`approve`) for the approval style. ・Tunables include `startup_timeout_sec` (default 10s), `tool_timeout_sec` (default 60s), and `required` (fail Codex startup if the server can't initialize). 🛠️ Practical Usage ・To add Context7 for up-to-date developer docs, it's a one-liner: `codex mcp add context7 -- npx -y @/upstash/context7-mcp`. ・For finer control, edit `~/.codex/config.toml` (or project-scoped `.codex/config.toml` for trusted projects) and define an `[mcp_servers.figma]` entry with its `url`, a `bearer_token_env_var`, and any `http_headers`. 💡 Use Cases Hand Codex an end-to-end flow: read the spec from your issue tracker, implement against the live DB schema, and pull a Figma design to build the UI. Wrap an internal API as an MCP server and Codex can invoke your custom business logic directly. ⚠️ Caveats ・You're granting external tools read/write access, so narrow permissions with `disabled_tools` and approval modes for safety. ・Don't hardcode tokens in the config file; read them from environment variables via `bearer_token_env_var`. ・For plugin-provided MCP servers, you don't specify the startup command yourself; you control enabled state and tool policy under `plugins.<plugin>.mcp

2026.08.16 07:05

# Codex Features and Practical Usage 🔌 Turn Codex from an agent that only touches code into a partner that drives your issue tracker, database, and design tools directly. The key is MCP (Model Context Protocol). 🏷️ Title: External Tool Connectivity (MCP) 🔗 URL: 📘 Overview MCP is the standard protocol that connects Codex to external tools and context. Register an MCP server and Codex can call that tool directly to read and write. Configuration is shared across the CLI and IDE extension, so the same setup works no matter which client you use. ⚙️ How It Works ・The simplest way to add a server is via the CLI: `codex mcp add -- `. Inside the TUI, `/mcp` lists your active servers. ・There are two transports: STDIO servers, which start a local process (configure `command`, `args`, `env`, `cwd`), and Streamable HTTP servers, accessed by URL (configure `url`, `bearer_token_env_var`, `http_headers`). ・Authentication supports Bearer tokens sourced from environment variables, or OAuth. For OAuth-capable servers, run `codex mcp login `. ・You can govern tools per server: `enabled_tools` / `disabled_tools` for allow and deny lists, and `default_tools_approval_mode` (`auto`/`prompt`/`approve`) for the approval style. ・Tunables include `startup_timeout_sec` (default 10s), `tool_timeout_sec` (default 60s), and `required` (fail Codex startup if the server can't initialize). 🛠️ Practical Usage ・To add Context7 for up-to-date developer docs, it's a one-liner: `codex mcp add context7 -- npx -y @/upstash/context7-mcp`. ・For finer control, edit `~/.codex/config.toml` (or project-scoped `.codex/config.toml` for trusted projects) and define an `[mcp_servers.figma]` entry with its `url`, a `bearer_token_env_var`, and any `http_headers`. 💡 Use Cases Hand Codex an end-to-end flow: read the spec from your issue tracker, implement against the live DB schema, and pull a Figma design to build the UI. Wrap an internal API as an MCP server and Codex can invoke your custom business logic directly. ⚠️ Caveats ・You're granting external tools read/write access, so narrow permissions with `disabled_tools` and approval modes for safety. ・Don't hardcode tokens in the config file; read them from environment variables via `bearer_token_env_var`. ・For plugin-provided MCP servers, you don't specify the startup command yourself; you control enabled state and tool policy under `plugins..mcp_servers.`. #OpenAICodex# #MCP#

커뮤니티로 전달