docs: define dual websocket and sse transport support
This commit is contained in:
1 parent
6dde1cc3a3
commit
8d34634506
1 file changed
+3
-2
@@ -12,8 +12,9 @@ The `mcp-memory` system runs as a **single, continuously running background daem
|
||||
The daemon uses the `axum` and `rust-mcp-axum` crates, binding to `0.0.0.0:3000` to serve the network.
|
||||
|
||||
### Standard MCP Endpoints
|
||||
* `GET /sse`: The Server-Sent Events (SSE) endpoint. Antigravity clients connect here to keep a one-way pipe open for receiving pushed responses and event notifications from the server.
|
||||
* `POST /messages`: The JSON-RPC endpoint. Clients use this to send tool calls and resource reads up to the server.
|
||||
* `GET /ws`: The WebSocket endpoint for efficient, low-latency, full-duplex JSON-RPC communication (preferred for proxies and the UI dashboard).
|
||||
* `GET /sse`: The Server-Sent Events (SSE) endpoint. Antigravity clients connect here to keep a one-way pipe open for receiving pushed responses.
|
||||
* `POST /messages`: The JSON-RPC endpoint. Clients use this to send tool calls and resource reads up to the server when connected via SSE.
|
||||
|
||||
### Custom Integration Endpoints
|
||||
* `GET /`: The Brain Monitor live HTML dashboard (returns real-time metrics UI).
|
||||
|
||||
Reference in new issue
Block a user