Glossary
Streamable HTTP with JSON responses
An MCP transport where each POST returns one plain JSON answer, with no event stream to keep open, for tool calls that finish in one reply.
Updated November 20, 2026
- Standard
- MCP Streamable HTTP transport
- Also called
Streamable HTTP JSON mode,JSON response mode
At OneLifeVibe
- Both OneLifeVibe connectors use Streamable HTTP with JSON responses and no server-sent event stream: every tools/call is one POST that returns one JSON answer.
What it means
Streamable HTTP with JSON responses is an MCP transport mode. The client sends an HTTP POST, and the server sends back one plain JSON answer. There is no server-sent event stream to keep open after the reply.
That keeps the exchange clear: one request, one response body. Use it when you want a tool call to finish as a normal HTTP round trip rather than a long-lived connection. The transport is still MCP, so the payloads follow the MCP message format and tools/call keeps its usual meaning.
How it works
The client sends an HTTP POST containing an MCP message. The server handles it and returns JSON in the response body. The client reads that body and decides what to do next. No separate stream is opened for the answer, so you are not tracking events across messages.
Because it is HTTP, normal status codes still matter. A 2xx response can carry a JSON-RPC result, and an error can arrive as an HTTP error or as a JSON-RPC error in the body, depending on the server. Read both before you retry, and do not assume a dropped POST means the tool did not run.
How OneLifeVibe uses it
Both OneLifeVibe connectors use Streamable HTTP with JSON responses and no server-sent event stream. Every tools/call is one POST that returns one JSON answer. You do not need an SSE client or a reconnect loop to call a tool.
The practical result is a direct request and response path. Send the tools/call POST, read the JSON answer, and continue. If you already have an HTTP client that handles JSON, you have the transport piece you need. Keep your error handling around the POST and the JSON body, because that is where the outcome appears.
Common mistakes
The most common mistake is treating the response as server-sent events. There is no event stream in this mode, so an SSE parser will wait for data that never arrives. Read the response body as JSON instead.
Another mistake is expecting more than one answer from a single tools/call. Each tools/call is one POST and one JSON answer. If you need another call, send another POST. Also check the HTTP status and the JSON body before you retry; a failed request and a JSON-RPC error are not the same thing, and retrying without reading the body can hide the cause.
Questions
What does Streamable HTTP with JSON responses mean in MCP?
It means the client sends an HTTP POST and gets one plain JSON answer back. No server-sent event stream stays open after the reply. The transport is MCP Streamable HTTP in JSON response mode.
Do OneLifeVibe connectors use server-sent events?
No. Both OneLifeVibe connectors use Streamable HTTP with JSON responses and no server-sent event stream. Every tools/call is one POST that returns one JSON answer.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.