Cmd. /mcp
List configured MCP tools and inspect server diagnostics.
Key takeaways
- List configured MCP tools and inspect server diagnostics.
- Check the input surface and availability before using the examples below.
Purpose
List configured MCP tools and inspect server diagnostics.
/mcpAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/mcpWhen to use it
- Run
/mcpbefore asking Codex to use an external tool. - Run
/mcp verbosewhen a server is present but a tool is missing or failing. - Confirm the design-context, metadata, and screenshot tools before starting from a Figma node.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/mcp | Lists MCP tools and diagnostics | You need the actual tool surface |
/apps | Inserts app mentions | You need a connector in the prompt |
/plugins | Manages packaged capabilities | You need to inspect installed bundles |
Effects and persistence
Inspects configured MCP servers and exposed tools. Use the appropriate codex mcp subcommand to add or remove servers.
/mcp lists configured Model Context Protocol tools available to Codex. Use /mcp verbose for
server-level diagnostics.
Authentication in 0.155.0
Local TUI sessions on supported Macs can use Touch ID verification for MCP requests. Expired OAuth credentials are reported more accurately, with reconnect guidance after refresh failure.
Cautions
- Tool availability can differ by profile, workspace, and trust state.
- Pair MCP write or destructive tools with
/permissionsand team policy. - Do not read “deprecated” as “already removed,” and do not postpone migration merely because the old subcommand still starts.
Official sources
Complete command list · Verification scope · History for this command