Only the first successfully registered MCP server name loads tools; new server names always show 0 tools

Open 💬 1 comment Opened Mar 29, 2026 by todd-niva

What version of Codex CLI is running?

v0.117.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Linux 6.8.12-tegra aarch64 aarch64

What terminal emulator and version are you using (if applicable)?

terminal on macos tahoe

What issue are you seeing?

Only the first successfully registered MCP server name loads tools; new server names always show 0 tools

What steps can reproduce the bug?

Uploaded thread: 019d3a76-695d-73a2-979f-e2f6e77b51d6
Repro:

  • Codex CLI v0.117.0, Linux aarch64 (Jetson AGX Thor)
  • One working SSH MCP server named "lightrag" with 4 tools — works
  • Add a second MCP server with any new name — always 0 tools
  • The second server's protocol is verified correct (initialize, resources/list, tools/list all return valid JSON-RPC)
  • Swapping scripts between names: the "lightrag" name always works regardless of script, any other name always fails
  • Removing "lightrag" and using only the new name: still 0 tools
  • Using codex mcp add instead of manual config: still 0 tools
  • No errors in codex-tui.log — tool discovery fails silently
  • Appears to be invisible cached state tied to the original server name

What is the expected behavior?

additional MCPs should show tools available.

Additional information

can you please add gpt-5.4 pro to codex cli?

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗