Glossary

Custom connector

A custom connector is a remote MCP server you add by URL. OneLifeVibe's free one at https://onelifevibe.com/mcp/free needs no sign-in.

Updated November 13, 2026

Also called
custom MCP connector

At OneLifeVibe

Related terms

What it means

A custom connector is a remote MCP server that a person adds to their assistant by URL. It is also called a custom MCP connector. MCP, the Model Context Protocol, is the protocol the assistant and the server use to exchange requests and responses. The custom part means you supply the server address yourself. The remote part means the server runs somewhere else and the client connects to it over the network. You use one when the MCP server you want is reachable at a URL and your client lets you add remote servers.

How it works

The client connects to the URL and speaks MCP to the server. In most remote setups that means HTTP requests carrying JSON-RPC messages. The client asks what the server offers, then calls the tools or other capabilities it needs. A stateless server does not keep a session between requests, so each request has to carry the context the server needs.

If the server requires OAuth, the client runs the authorization flow and sends the resulting credential. A server that needs no sign-in skips that step. When something fails, check the URL, the client's connection status and the error returned by the server before changing your code.

How OneLifeVibe uses it

OneLifeVibe uses the term for its remote MCP server at https://onelifevibe.com/mcp/free. Add that URL as a custom connector in an MCP client that supports remote servers. The free connector is stateless, so there is no server-side session to resume between calls. It also works with no sign-in, which means you can test the connection without an account step. The same URL is the endpoint the client should use; keep the path exactly as written.

Common mistakes

One common mistake is pasting a local launch command into a field that expects a remote server URL. A custom connector is the remote case, so the client needs an address it can reach over the network. Another is expecting the free OneLifeVibe endpoint to remember state between requests. It is stateless, so do not design a flow that depends on session data living on the server. Check that your client supports remote MCP servers and that the URL is exact before you debug anything else.

Questions

What URL do I use for the OneLifeVibe custom connector?

Use https://onelifevibe.com/mcp/free. It works as a custom connector with no sign-in.

Does the OneLifeVibe free connector keep session state?

No. It is stateless, so each request is handled without a server-side session between calls.

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.