MCP client timed out at startup

Resolved 💬 2 comments Opened Feb 15, 2026 by eduard-ignatev Closed Feb 15, 2026

What version of Codex CLI is running?

0.101.0

What subscription do you have?

free

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

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

Windows Terminal (WSL)

What issue are you seeing?

⚠ MCP client for `playwright` timed out after 10 seconds. Add or adjust `startup_timeout_sec` in your config.toml:
  [mcp_servers.playwright]
  startup_timeout_sec = XX

⚠ MCP client for `context7` timed out after 10 seconds. Add or adjust `startup_timeout_sec` in your config.toml:
  [mcp_servers.context7]
  startup_timeout_sec = XX

⚠ MCP startup incomplete (failed: playwright, context7)

What steps can reproduce the bug?

Just starting codex

What is the expected behavior?

Successful initialization or meaningful error message

Additional information

config.toml:

[mcp_servers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp", "--api-key", "CONTEXT7_API_KEY"]

[mcp_servers.playwright]
command = "npx"
args = ["@playwright/mcp@latest"]

When I run the command in terminal mannually, it works fine:

npx -y @upstash/context7-mcp --api-key CONTEXT7_API_KEY
WARNING: Using default CLIENT_IP_ENCRYPTION_KEY.
Context7 Documentation MCP Server v2.1.1 running on stdio

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗