-
Notifications
You must be signed in to change notification settings - Fork 12.3k
Allow spaces or more symbols in MCP server names #19179
Copy link
Copy link
Open
Labels
configIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesenhancementNew feature or requestNew feature or requestmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) servers
Metadata
Metadata
Assignees
Labels
configIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesenhancementNew feature or requestNew feature or requestmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) servers
Type
Fields
Give feedbackNo fields configured for issues without a type.
What variant of Codex are you using?
CLI
What feature would you like to see?
Hey. Currently the validation for MCP servers warns if name contains anything other than letters, numbers,
_or-. My assumption is this limitation stems from TOML spec, used for Codex config:But TOML also supports quoted keys, like so:
This is useful for a case like shown above - to give more easily readable names to MCP servers. Would you consider expanding the validation to at least support all ASCII characters?
Additional information
codex/codex-rs/cli/src/mcp_cmd.rs
Lines 912 to 918 in f1923a3