Glossary
Mcp-Session-Id
An optional MCP header that ties requests to a server-side session. OneLifeVibe does not use sessions, so it never issues or requires one.
Updated November 12, 2026
- Standard
- Model Context Protocol specification
- Also called
MCP sessions
At OneLifeVibe
- Protocol versions 2025-03-26 through 2026-07-28. There are no sessions (Mcp-Session-Id) and no batches.
Related terms
What it means
Mcp-Session-Id is an HTTP header defined by the Model Context Protocol. It is optional. Some MCP servers use it to attach a request to a session, which is a server-side grouping of related requests. The value is created by the server, not by the client. A client treats it as an opaque string and sends it back unchanged when the server expects it.
Sessions are useful when a server needs continuity across calls: setup done once, state reused later. Not every MCP server works that way. The header appears only when a server chooses to manage sessions. If a server does not use sessions, there is no session ID to issue, store, or expire.
How it works
When a server supports sessions, it can return Mcp-Session-Id in a response. The client records the value and includes it on later requests to the same server. The server uses it to find the matching session. The exact lifetime and meaning of the session belong to the server; the protocol does not promise a fixed timeout or a particular storage model.
Over Streamable HTTP, this fits the normal request and response flow. Each HTTP request still carries its own method, headers, and JSON-RPC payload. The session header adds a link between requests; it does not change the payload. If the header is missing or no longer valid, a session-aware server may reject the request. Handle that as a normal HTTP error and read the status and body before you retry.
How OneLifeVibe uses it
OneLifeVibe does not use Mcp-Session-Id. The assistant connector supports MCP protocol versions 2025-03-26 through 2026-07-28, and those versions are served without sessions and without batches. No session ID is issued, so there is no header to store, replay, or expire.
For your client, that means every request stands on its own. Do not gate calls on a session ID coming back, and do not build retry or connection logic around one. If your MCP client is written for servers that use sessions, make sure it can run against a server that does not. A missing Mcp-Session-Id from OneLifeVibe is expected, not an error.
Common mistakes
The main mistake is assuming every MCP server has sessions. The header is optional, and OneLifeVibe does not use it at all. Sending a stored ID from another server will not create a session, and waiting for one will hold up your client.
Another mistake is treating the header as authentication. Mcp-Session-Id is not an OAuth token or an API key. A session ID does not prove who the caller is, so do not use it in place of an access token.
Finally, do not confuse no sessions with no state anywhere. A session ID is one way to tie requests together. OneLifeVibe does not use that way. Build against the behavior the connector documents, and handle the absence of Mcp-Session-Id as normal.
Questions
Does OneLifeVibe support MCP sessions?
No. OneLifeVibe serves MCP protocol versions 2025-03-26 through 2026-07-28 without sessions and without batches, so it does not issue or require Mcp-Session-Id.
Should I send Mcp-Session-Id to OneLifeVibe?
No. There is no session ID to send back, and the connector does not use one. If your client requires a session header, it needs to handle servers that do not use sessions.
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.