onelifevibe

Glossary

Streamable HTTP

Streamable HTTP is the MCP transport that sends JSON-RPC messages by POST to one endpoint; OneLifeVibe connectors return one JSON answer per tools/call.

Updated November 6, 2026

At OneLifeVibe

Related terms

What it means

Streamable HTTP is a transport for the Model Context Protocol. It gives an MCP client one HTTP endpoint to talk to. The client sends JSON-RPC messages to that endpoint with POST. The server reads the message, handles it, and returns a response. That is the core idea: one endpoint, POST requests, JSON-RPC messages.

MCP uses JSON-RPC 2.0 to name operations such as tools/call. In Streamable HTTP, those messages travel as HTTP request bodies rather than over a separate transport channel. A request carries a method and parameters; a response carries a result or an error. The transport does not change what the method means, only how the message moves between client and server.

How it works

A typical exchange is simple. The client builds a JSON-RPC request for a method such as tools/call, sends it as the body of an HTTP POST to the MCP endpoint, and reads the response body. The response is a JSON-RPC message. For a successful call, the client gets the result. For a failure, it gets an error object, and the HTTP status tells you whether the request reached and was accepted by the server.

Streamable HTTP can also use server-sent events in some MCP setups; that is a server-side choice. OneLifeVibe's connectors do not use an event stream. Because the transport is HTTP, ordinary HTTP tooling applies: timeouts, retries, proxies, and status codes. Keep the request and response bodies as JSON-RPC messages and let the HTTP layer handle delivery.

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. There is no long-lived stream to keep open for a tool call.

The free connector is stateless. Any MCP client that supports remote servers can add https://onelifevibe.com/mcp/free as a custom connector. Because the connector is stateless, each POST should carry the JSON-RPC message the server needs for that call; the client should not rely on the server remembering an earlier request.

Common mistakes

Do not open a server-sent event stream for a OneLifeVibe tool call and wait for events. The connector returns a JSON response to the POST. Do not send one JSON-RPC message to one URL and another message to a different URL; Streamable HTTP uses one endpoint.

Do not assume the free connector keeps session state between calls. If a call fails, inspect the HTTP status and any JSON-RPC error in the response before retrying. A retry repeats the POST and the tools/call, so make sure repeating the operation is what you want.

Questions

What endpoint do I use for the free OneLifeVibe MCP connector?

Add https://onelifevibe.com/mcp/free as a custom connector in any MCP client that supports remote servers. The free connector is stateless and uses Streamable HTTP with JSON responses.

Does OneLifeVibe use server-sent events for MCP?

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.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.