You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server will start on port 3000. You can test the initialization and tool listing:
34
34
35
-
### Server supporting with SSE via GET (`server/standaloneSseWithGetStreamableHttp.ts`)
35
+
### Server supporting SSE via GET (`server/standaloneSseWithGetStreamableHttp.ts`)
36
36
37
37
An MCP server that demonstrates how to support SSE notifications via GET requests using the Streamable HTTP transport with Express. The server dynamically adds resources at regular intervals and supports notifications for resource list changes (server notifications are available through the standalone SSE connection established by GET request).
38
38
@@ -46,9 +46,10 @@ The server will start on port 3000 and automatically create new resources every
46
46
47
47
### Server with JSON response mode (`server/jsonResponseStreamableHttp.ts`)
48
48
49
-
This is not recommented way to use the transport, as its quite limiting and not supporting features like logging and progress notifications on tool execution.
50
49
A simple MCP server that uses the Streamable HTTP transport with JSON response mode enabled, implemented with Express. The server provides a simple `greet` tool that returns a greeting for a name.
51
50
51
+
_NOTE: This demonstrates a server that does not use SSE at all. Note that this limits its support for MCP features; for example, it cannot provide logging and progress notifications for tool execution._
52
+
52
53
#### Running the server
53
54
54
55
```bash
@@ -101,8 +102,7 @@ SESSION_ID=$(curl -X POST \
101
102
echo"Session ID: $SESSION_ID
102
103
103
104
```
104
-
105
-
Once thre is a session we can send POST requests
105
+
Once a session is established, we can send POST requests:
0 commit comments