Codex cannot handshake with WebStorm MCP server (SSE endpoint), initialize fails
Resolved 💬 3 comments Opened Feb 13, 2026 by NookieGrey Closed Feb 14, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
Codex Desktop cannot connect to the webstorm MCP server even though WebStorm MCP is running and reachable.
Handshake fails during initialize.
Environment
- Date: February 14, 2026
- OS: macOS
- IDE: WebStorm MCP Server
2025.3.2 - Codex config path:
/Users/nookiegrey/.codex/config.toml - MCP server config:
[mcp_servers.webstorm]url = "http://127.0.0.1:64342/sse"
Steps to Reproduce
- Start WebStorm with MCP server enabled on port
64342. - Configure Codex MCP server as:
url = "http://127.0.0.1:64342/sse"
- Call MCP API from Codex (for example
list_mcp_resourcesfor serverwebstorm).
Expected
Codex completes initialize handshake and can list resources/tools.
Actual
Codex fails during handshake with:Unexpected content type: None, when send initialize request
Additional Diagnostics
GET http://127.0.0.1:64342/ssereturns200 OKwithtext/event-stream.GET http://127.0.0.1:64342/mcpreturns404.POST /message?sessionId=...returns202 Accepted.- Direct MCP stdio initialize against WebStorm runner returns valid:
serverInfo.name = "WebStorm MCP Server"serverInfo.version = "2025.3.2"
Suspected Cause
Codex appears to treat the configured URL as streamable HTTP transport, while WebStorm exposes SSE transport (/sse + /message?sessionId=...), leading to protocol mismatch at initialize.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Codex 26.212.1823
Error still exist
Codex doesn't support SSE transports for MCP servers. This mechanism is deprecated in the MCP standard, replaced by streaming HTTP. We don't have plans to add support for SSE.