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
Copy file name to clipboardExpand all lines: packages/burger-mcp/README.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,6 @@ This is the Burger MCP server, exposing the Burger API as a Model Context Protoc
18
18
This server supports the following transport types:
19
19
20
20
-**Streamable HTTP**
21
-
-**SSE** (legacy protocol, for backward compatibility)
22
21
-**Stdio** (currently only supported when starting the server locally with `npm start:local`)
23
22
24
23
The remote server is deployed with [Azure Functions](https://learn.microsoft.com/azure/azure-functions/functions-overview).
@@ -56,9 +55,6 @@ First, you need to start the Burger API and Burger MCP server locally.
56
55
4. Put `http://localhost:3000/mcp` in the URL field and click on the **Connect** button.
57
56
5. In the **Tools** tab, select **List Tools**. Click on a tool and select **Run Tool**.
58
57
59
-
> [!NOTE]
60
-
> This application also provides an SSE endpoint if you use `/sse` instead of `/mcp` in the URL field.
61
-
62
58
## Development
63
59
64
60
### Getting started
@@ -73,7 +69,7 @@ You can run the following command to run the application server:
73
69
npm start
74
70
```
75
71
76
-
This will start the application server. The MCP server is then available at `http://localhost:3000/mcp`or `http://localhost:3000/sse`for the streamable HTTP and SSE endpoints, respectively.
72
+
This will start the application server. The MCP server is then available at `http://localhost:3000/mcp` for the streamable HTTP endpoints.
77
73
78
74
Alternatively, you can run the MCP server with stdio transport using:
0 commit comments