# SSE Support Removed: Moving to Streamable HTTP MCP-Server

We have officially **removed support for Server-Sent Events (SSE)** in our Streamable HTTP MCP-Server implementation.

SSE was previously used to deliver real-time updates to clients, but as our platform has evolved, we have shifted our focus to more robust and flexible streaming technologies.

> **What does this mean?**  
> - SSE server URLs are now **deprecated** and will no longer be supported in RapidMCP.  
> - We recommend all users transition to our new streaming endpoints, which offer improved performance, reliability, and compatibility with a wider range of clients and use cases.

* * *

### FYI

We have officially moved our default position from **SSE (Server-Sent Events)** to **Streamable HTTP servers**. This is the new direction the MCP world is moving towards.

- **No action is needed from you right now.**  
- We will continue to support SSE for a long period until all clients have transitioned.

If you'd like to know more or need help with the migration, **feel free to ping me!**

* * *

We've added support for Streamable HTTP and also SSE. Long story short, MCP protocol has made a decision to remove SSE support but all of the client apps have needed to update to the latest protocol.

If you update, you'll need to change the RapidMCP url from `/see` to `/stream` - this will be the ideal way going forward so you're on the target protocol.

* * *

All that said, we still support old protocol. So `/sse` should still work as expected.

Let me know if you need a head with this.

* * *

**tldr:**  
change this:

```
{
   "RapidMCP": {
      "url": "http://localhost:4000/mcp/xxxxx/sse",
    },
}
```

to this:

```
{
   "RapidMCP": {
      "url": "http://localhost:4000/mcp/xxxx/stream",
      "headers": {
        "api-key": "xxxx"
      }
    },
}
```