Error text / 报错原文
waitForMcpConnections timeoutMCP connection timed outserver connection timeout
What it means
The Code Mode or agent runtime waited for MCP servers but not all connections became ready before the timeout.
Most common causes
- Remote server slow OAuth flow
- Network or tunnel latency
- Server cold start
- Misconfigured callback host
Fastest fix
- Reproduce the smallest failing case outside the agent.
- Confirm auth, session, and transport before changing app code.
- Disable unrelated tools or servers and retry once.
- Capture the exact timestamp, client version, and raw error text.
Safe fix
- Keep secrets in environment variables or the platform secret store.
- Use least-privilege scopes and read-only tools by default.
- Add validation around manifests, schemas, and callback URLs.
- Document the working local and production configuration.
What not to do
- Do not paste OAuth tokens or session IDs into public logs.
- Do not bypass TLS, CSP, or permission prompts as a permanent fix.
- Do not enable every MCP tool globally just to make one task pass.
Diagnostic commands
node --version npx wrangler --version curl -I "$MCP_SERVER_URL"