Glossary

initialize

The first MCP request, where client and server agree on a protocol version and capabilities. OneLifeVibe's MCP server expects it before tool calls.

Updated November 12, 2026

Standard
Model Context Protocol specification
Also called
MCP handshake

At OneLifeVibe

Related terms

What it means

initialize is the first request in a Model Context Protocol session. A client sends it to a server, and the two sides agree on a protocol version and on the capabilities each side supports. That agreement sets the ground rules for the requests that follow.

It is a control request, not a tool call. You do not use initialize to fetch data or run an action. You use it to establish that the client and server can talk to each other before you list or call tools.

How it works

MCP uses request and response messages. The client opens with initialize, the server answers with the agreed version and its capabilities, and the client can then move on to methods such as tools/list and tools/call. ping is there for a simple check that the server is reachable.

The version and capability agreement matters because clients and servers are built separately. If both sides know what the other supports, later requests do not have to guess. Notifications are one-way messages, so they do not use the same request and response pattern as initialize.

How OneLifeVibe uses it

OneLifeVibe runs a Streamable HTTP MCP server at https://onelifevibe.com/mcp/free. It returns responses in the HTTP body, is stateless and requires no sign-in. The endpoint's methods are initialize, ping, tools/list and tools/call. Clients start with initialize, then use tools/list to see the tools and tools/call to run one. resources/list answers with an empty list. Notifications are accepted with 202.

Because the endpoint is stateless, there is no stored session for a later request to resume. Send initialize first, then send each request with what it needs. Do not wait for a session cookie or a sign-in step from the server.

Common mistakes

The usual mistake is to treat initialize as optional and send tools/call first. In MCP, initialize is the first request; use it to agree on version and capabilities before any tool call. Another mistake is to expect initialize to return tools or data. It does not; tools/list and tools/call do that.

On OneLifeVibe, do not expect resources/list to return items. It answers with an empty list. Do not treat a 202 for a notification as a normal response body. And do not assume the stateless endpoint keeps state from the initialize request; later calls stand on their own.

Questions

Does the OneLifeVibe MCP endpoint require sign-in for initialize?

No. https://onelifevibe.com/mcp/free is stateless and requires no sign-in. Send initialize first, then tools/list or tools/call.

What methods does the OneLifeVibe MCP server support?

The endpoint's methods are initialize, ping, tools/list and tools/call. resources/list answers with an empty list, and notifications are accepted with 202.

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.