Codex CLI /mcp can show 'Tools: (none)' while MCP tools are callable

Summary

In Codex CLI, /mcp can show No MCP tools available and per-server Tools: (none) even when MCP tools are actually callable in the same session.

This appears to be an MCP discovery/rendering mismatch in CLI status output rather than a hard MCP connectivity failure.

Environment

• Codex CLI: 0.118.0
• OS: macOS
• Date: 2026-04-07
• MCP type: local stdio MCP server exposing tools (tool-only or tools-first setups)

Reproduction (generic)

1. Configure any local MCP server that successfully exposes callable tools.
2. Start a fresh Codex CLI session.
3. Run /mcp and observe output.
4. Then call one MCP tool in-session.

Expected

• /mcp should list discovered tools for enabled/healthy MCP servers.

Actual

• /mcp sometimes reports:
• No MCP tools available
• Tools: (none)
• But tool invocation still succeeds in-session.

Notes

• This can mislead users into thinking MCP is broken, while runtime tool calls are actually functional.
• Related behavior appears similar to existing MCP discovery/status regressions, but this report is specifically about CLI status misreporting vs successful tool execution.