/mcp in codex-cli v0.117.0 omits Status and renders working MCP servers as Tools: (none)

What version of Codex is running?

codex-cli 0.117.0

What subscription do you have?

ChatGPT

Which model were you using?

gpt-5.4

What platform is your computer?

WSL2 on Windows, Arch Linux userland (x86_64)

What issue are you seeing?

In codex-cli 0.117.0, the /mcp screen appears to have regressed.

For working MCP servers, /mcp no longer shows the per-server Status line and can render servers as:

• Tools: (none)
• Resources: (none)
• Resource templates: (none)

This happens even when the MCP server is actually enabled and its tools are callable.

In my case this reproduces with non-hyphenated server names such as:

• context7
• openaiDeveloperDocs

So this looks different from issue #15565, which is specifically about hyphenated MCP server names.

Why this looks like a real regression

1. The official docs for /mcp say it should show which MCP servers and tools are available in the current session.
2. codex mcp list still shows these MCP servers as enabled.
3. The tools themselves still work. For example, I can successfully call Context7 tools such as:

• resolve_library_id
• query_docs

1. In an earlier CLI version (0.116.x), the /mcp screen showed Status: enabled and showed the actual tool list for the same MCP setup.

What steps can reproduce the bug?

1. Configure working MCP servers in Codex, for example:

• context7
• openaiDeveloperDocs

1. Start codex-cli 0.117.0.
2. Type /mcp.
3. Observe that the MCP inventory screen omits the Status line and may show Tools: (none) for servers whose tools are actually available.
4. In another shell, run codex mcp list and confirm the same servers are enabled.
5. In the session, use one of the MCP tools successfully (for example Context7 resolve_library_id / query_docs).

What is the expected behavior?

/mcp should show the MCP server status and the actual tool list available in the current session, matching the configured/working MCP inventory.

At minimum, for working servers like context7 and openaiDeveloperDocs, /mcp should not show Tools: (none) when their tools are callable.

What is the actual behavior?

/mcp omits Status and shows Tools: (none) for working MCP servers.

This makes the MCP screen unreliable as a source of truth and makes it look like MCP is broken when it is not.

Additional information

A few extra observations that may help narrow it down:

• codex mcp list still reports the servers as enabled.
• The issue reproduces with non-hyphenated server names, so it does not appear to be the same grouping bug as #15565.
• In logs, Codex also probes resources/list and resources/templates/list, which return -32601 Method not found for some tool-only MCP servers. That part seems fine on its own, but the /mcp UI should still show the available tools when tools/list succeeded.

If helpful, I can provide before/after screenshots from 0.116.x vs 0.117.0 showing the MCP screen difference.