Remote URL/SSE MCP still broken for agent (~12 months) + workaround

Support Bug Reports
4

Hey, thanks for the detailed report and for linking the previous threads.

This is a known bug. It’s a regression in the V2 MCP connection handler. Cursor tries Streamable HTTP POST, and when an SSE-only server returns 404, the fallback to SSE doesn’t trigger. More details here: Cursor fails to fall back from Streamable HTTP to SSE transport for remote MCP servers

The team is aware, and your report helps with prioritization. There’s no ETA yet.

For a workaround, mcp-remote gets around this by forwarding SSE over stdio:

{
  "mcpServers": {
    "neo4j-memory": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://your-mcp-server/sse"]
    }
  }
}

About “Server not approved, disabling”, that’s not a bug, it’s a security feature. Servers in the project .cursor/mcp.json need manual approval in Cursor Settings > MCP. If you want to avoid that step, move the config to the global ~/.cursor/mcp.json.

Let me know if you need anything else.