MCP Server Issue
Resolved 💬 5 comments Opened Nov 1, 2025 by aaron-peng-01 Closed Jan 17, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the VS Code extension are you using?
0.4.35
What subscription do you have?
Business
Which IDE are you using?
VS Code
What platform is your computer?
Darwin 25.0.0 arm64 arm
What issue are you seeing?
- If one of all MCP Servers' tools' names is not qualified, it seems that the rest tools will not be registered.
- Also, codex is dead not due to network issues but because of mcp server connections. I mean, codex should be dependent from mcp servers, because they're just extensions. If a tool's name is not qualified, codex is always re-connecting 5/5, then fail.
What steps can reproduce the bug?
- config a set of mcp severs, with one of the tools' name is not qualified. (there's a space in it)
- sometimes, codex is dead and re-connecting.
- if codex is not dead, you'll find some tools can be used, but some not.(could be listed, but can't be used)
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I mean if the tools are registered in some kind of sequence? If one tool fails to be registered, the tools after it won't be registered?
What do you mean by "qualified"?
Illegal name, not among[a-zA-Z0-9-_]. It seems like this.
Closing out old bugs.