MCP server configurations updated with 30-second timeout

Initial package downloads can take longer than anticipated, frequently exceeding the default 10-second timeout enforced by Codex. To prevent connection failures on the first run, a 30-second startup timeout is now applied to all newly generated MCP server configurations within the CLI.

This extended window provides sufficient time for npx to complete initial downloads without throwing timeout errors. The developer documentation is updated to reflect this configuration as the recommended standard for all client setups, ensuring more reliable server initialization out of the box.