Add the OneLifeVibe free connector to Cursor

What you are building

You are adding a remote MCP server to Cursor. The server is the OneLifeVibe free connector at https://onelifevibe.com/mcp/free. It uses Streamable HTTP and returns JSON responses, not a server-sent event stream. It is stateless and needs no sign-in, so there is no token to paste.

The connector exposes read-only tools: 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 the websites' no-account tools such as senatus_search_dossiers and introworth_attention_price. Nothing changes data, spends money or contacts anyone.

Cursor can look things up while you work without a local MCP process, an API key or an OAuth flow for these calls.

Before you start

You need Cursor and a place for mcp.json. The user-level file is ~/.cursor/mcp.json; a project can use .cursor/mcp.json instead. Pick one location for this entry. No OneLifeVibe key, account or OAuth client is required for the free connector.

Confirm the URL. The free connector is https://onelifevibe.com/mcp/free. Do not swap in https://onelifevibe.com/mcp unless you are working with the account connector, which signs in with 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 use the free connector.

How the code works

The snippet is the whole config. mcpServers is the top-level object Cursor reads. Inside it, onelifevibe-free names this server entry, and its value has one field: url, set to the free connector endpoint. There is no command, args or env block because Cursor is not launching a local process.

Keep the URL exact. The path is /mcp/free, not /mcp. Because the server is stateless, each tool call carries what it needs; you do not manage a session identifier between calls. Because it returns JSON rather than a stream, Cursor gets a complete JSON response per request. No auth header is needed.

Keep onelifevibe-free as shown. When Cursor loads the config, the connector's tools become available: find_free_tools, list_situations, gift_ideas, list_worlds, senatus_search_dossiers and introworth_attention_price. None of them writes, pays or sends messages.

Testing it

Save the file, let Cursor load the config, then open the tools for onelifevibe-free. Start with list_situations; it needs no arguments and confirms that the connection and tool discovery work. Then call find_free_tools with a query or situation and check the JSON result. Try gift_ideas with max_usd to exercise the optional argument.

If the tool list is empty, recheck the JSON shape and the exact URL. A syntax error, a missing mcpServers wrapper or a typo in /mcp/free will stop the server from loading. If a call returns an HTTP error, a 404 usually means the path is wrong; retry after a 5xx. No sign-in means credentials are not the cause.

Going to production

For read-only lookups in Cursor, the free connector is the right endpoint. It has no secret to rotate and no session store to maintain, so the mcp.json entry stays small. If a task needs to change data, spend money or contact someone, this connector cannot do it.

For a person's own data, the account connector is https://onelifevibe.com/mcp. Its OAuth 2.1 and PKCE sign-in is set up for Meta Muse only today. Cursor is another MCP client, so use the free connector here.