onelifevibe

Guide

Add the OneLifeVibe free connector to VS Code

Add the free OneLifeVibe connector to VS Code by defining the Streamable HTTP MCP server https://onelifevibe.com/mcp/free in .vscode/mcp.json.

Updated November 6, 2026

Stack
Visual Studio Code (.vscode/mcp.json)
API
Platform API v1 · Connectors

The code

// .vscode/mcp.json
{
  "servers": {
    "onelifevibe-free": { "type": "http", "url": "https://onelifevibe.com/mcp/free" }
  }
}

The facts it relies on

Related guides

What you are building

You are adding a workspace-level MCP server entry to VS Code. The entry points at the OneLifeVibe free connector, a Streamable HTTP MCP server at https://onelifevibe.com/mcp/free that returns JSON responses, has no server-sent stream, is stateless and needs no sign-in.

Use it when you want read-only OneLifeVibe tools inside the editor. The free connector exposes find_free_tools with a situation or query, list_situations, gift_ideas with an optional max_usd, and list_worlds. It also carries the websites' no-account tools such as senatus_search_dossiers and introworth_attention_price. Nothing changes data, spends money or contacts anyone.

This is the free connector, not the account connector. It does not read a person's own OneLifeVibe data. That distinction matters when you decide what to test and what to keep in a shared workspace.

Before you start

You need a VS Code workspace and MCP support in your VS Code setup. The configuration lives in a .vscode folder at the workspace root, in a file named mcp.json. If the folder does not exist, create it before adding the file.

Use the URL exactly as shown: https://onelifevibe.com/mcp/free. Do not add an Authorization header or a token. The free connector is stateless and has no sign-in, so the entry contains no credentials.

If you were expecting to work with your own OneLifeVibe data, note that the account connector at https://onelifevibe.com/mcp uses OAuth 2.1 with PKCE. Today its 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 use the free connector.

How the code works

The file contains a servers object. Inside it, onelifevibe-free is the local name for this server entry. The name identifies the entry in the configuration; the URL is what VS Code connects to.

The type field is http. That tells VS Code this is an HTTP MCP server, matching the Streamable HTTP transport used by the free connector. There is no command to run, no arguments and no environment block, because the connector is remote and stateless. There is also no headers block, because no sign-in is required.

When VS Code loads the workspace configuration, it reads this server definition and can call the endpoint. Responses come back as JSON rather than through a server-sent stream. Keep the URL exact; a changed path or host points somewhere else and the tools will not be the ones described here.

Testing it

Save .vscode/mcp.json and let VS Code load the configuration. Start with list_situations, which takes no special setup and shows whether the server is reachable. Then call find_free_tools with a situation or query, or call gift_ideas with an optional max_usd.

Check that you get JSON back and that the tool names match the free connector's read-only set. You can also try list_worlds, senatus_search_dossiers or introworth_attention_price. None of these calls should change data, spend money or contact anyone.

If the server does not load or a call fails, check three things: the file is at .vscode/mcp.json in the workspace root, the JSON is valid, and the URL is exactly https://onelifevibe.com/mcp/free. Remove any auth header you added, since the free connector needs none. If calls still fail, check network access to onelifevibe.com from your machine.

Going to production

For a team workspace, commit .vscode/mcp.json so everyone gets the same server entry. The free connector entry contains no secret and no account-specific value, which makes it suitable for a shared repository. Keep the server name onelifevibe-free stable so documentation and local checks refer to the same entry.

The free connector is best for read-only discovery and no-account tools. If a workflow needs a person's own OneLifeVibe data, that is the account connector at https://onelifevibe.com/mcp, which uses OAuth 2.1 with PKCE. Today its sign-in is set up for Meta Muse only, so other MCP clients use the free connector.

Review the file when you change workspaces or move the configuration into another repository. A missing .vscode folder or an incorrect URL is the usual reason the server entry stops working. No credential rotation is needed for this entry because it has no sign-in.

Questions

What URL do I use for the OneLifeVibe free connector in VS Code?

Use https://onelifevibe.com/mcp/free in the .vscode/mcp.json server entry. Set the type to http and keep the URL exact. The endpoint is a Streamable HTTP MCP server with JSON responses, no server-sent stream and no sign-in.

Does the OneLifeVibe free connector need a sign-in?

No. The free connector is stateless and has no sign-in, so you do not add a token or Authorization header. It only exposes read-only tools, and nothing changes data, spends money or contacts anyone.

Can I use the OneLifeVibe account connector in VS Code instead?

The account connector at https://onelifevibe.com/mcp uses OAuth 2.1 with PKCE, but today its sign-in is set up for Meta Muse only. The public client is onelifevibe-muse, and dynamic client registration is open only for the Muse callback hosts. Other MCP clients use the free connector.

Try it against the real API. A free Sandbox key reads the catalogue and the event log at once, no card.

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.