Add the OneLifeVibe free connector to Claude Code

What you are building

You are registering a remote MCP server with Claude Code CLI. The server is the OneLifeVibe free connector at https://onelifevibe.com/mcp/free. It speaks Streamable HTTP, returns JSON responses rather than a server-sent stream, keeps no session state, and requires no sign-in.

Its own tools are read-only: find_free_tools takes a situation or query, list_situations lists situations, gift_ideas takes an optional max_usd, and list_worlds lists worlds. It also carries no-account website tools such as senatus_search_dossiers and introworth_attention_price.

The account connector at https://onelifevibe.com/mcp is a different server; today its OAuth 2.1 and PKCE sign-in is set up for Meta Muse only, so Claude Code uses the free connector.

Before you start

You need a working Claude Code CLI installation and outbound access to onelifevibe.com. No OneLifeVibe account is required, so there is no token to store or OAuth callback to register.

Pick the local server name before you run anything. The code on the page uses onelifevibe-free, which is a label in your Claude Code configuration, not part of the URL. Use the URL ending in /free; the /mcp path is the account connector.

How the code works

The first command uses claude mcp add with the http transport, the server name onelifevibe-free, and the free connector URL. The http transport matches the server: Streamable HTTP with JSON responses, not a stdio process or a server-sent event stream.

No authentication flags, headers, or environment variables are needed because the connector is stateless and has no sign-in. Each tool call stands alone; there is no session to refresh.

The second command, claude mcp list, shows registered MCP servers and their tools. Use it to confirm the name and URL were accepted and the free connector tools are visible.

Testing it

Run claude mcp list first. You want to see onelifevibe-free and the free connector tools. If the server is missing, re-run the add command and check the name and URL for typos.

Then call a read-only tool. Ask Claude Code to run list_situations, or find_free_tools with a situation or query. Try gift_ideas with the optional max_usd, and list_worlds. Responses should be JSON. Because the connector is stateless, a failed call can be retried without cleaning up a session.

If something fails, check the URL first: it must be exactly https://onelifevibe.com/mcp/free, including /free. Confirm the transport is http, not stdio or sse, and that Claude Code can reach onelifevibe.com. There is no token to rotate and no OAuth callback to fix.

Going to production

Treat the free connector as a read-only lookup path in your Claude Code workflow. Its tools cover situations, free-tool searches, gift ideas with an optional max_usd, worlds, and no-account website tools such as senatus_search_dossiers and introworth_attention_price. They do not change data, spend money, or contact anyone.

Keep the server name and URL in your project setup notes so every developer registers the same endpoint. The connector is stateless: no credentials to distribute or rotate for the free server, and no session state to expire.

If you later need a person's own OneLifeVibe data, the account connector at https://onelifevibe.com/mcp uses OAuth 2.1 and PKCE. Today that sign-in is set up for Meta Muse only, with the public client onelifevibe-muse and dynamic client registration open only for the Muse callback hosts. Other MCP clients, including Claude Code, continue with the free connector.