codex - 💡(How to fix) Fix Allow spaces or more symbols in MCP server names [1 participants]

TL;DR

The validation for MCP server names may need to be updated to support quoted keys as per the TOML spec, allowing for more flexible naming conventions.

Guidance

• Review the TOML specification to understand the supported characters for quoted keys.
• Consider updating the validation in mcp_cmd.rs to allow for quoted keys with ASCII characters.
• Verify that the updated validation does not break existing functionality or introduce security vulnerabilities.
• Test the updated validation with example use cases, such as the provided "Postgres MCP - Production - Read Only" server name.

Example

[mcp_servers."Postgres MCP - Production - Read Only"]
...

This example demonstrates how quoted keys can be used to create more readable MCP server names.

Notes

The current limitation may be due to the interpretation of the TOML spec, and updating the validation may require careful consideration of potential security implications.

Recommendation

Apply workaround by updating the validation to support quoted keys, as this would provide more flexibility in naming MCP servers while following the TOML spec.