Glossary

Account connector

The account connector is the OneLifeVibe MCP server at https://onelifevibe.com/mcp that acts on a signed-in person's own data with their OAuth token.

Updated November 18, 2026

Also called
signed-in connector

At OneLifeVibe

Related terms

What it means

The account connector is the OneLifeVibe MCP server at https://onelifevibe.com/mcp. An MCP client connects, the person signs in, and the server calls tools against that person's own data using the OAuth token from that sign-in. You may also see it called the signed-in connector.

OneLifeVibe runs a second MCP server, the free connector at https://onelifevibe.com/mcp/free. It needs no sign-in and is read-only. Use the account connector when a call has to touch data that belongs to a specific signed-in person.

How it works

The account connector uses OAuth 2.1 authorization code with PKCE, S256 method. The authorization server issuer is https://accounts.onelifevibe.com/realms/olv, a Keycloak identity provider. The client sends the person to that authorization server, gets an authorization code, and exchanges it with the PKCE code verifier for a token. It then presents the token on calls to https://onelifevibe.com/mcp.

Meta Muse uses the public client onelifevibe-muse, with PKCE and no client secret. Dynamic client registration is open only for the Muse callback hosts. OneLifeVibe requires PKCE with the S256 method for the account connector. The connector also limits each person's tool calls across all Cloudflare locations, so the limit applies across regions, not per server instance.

How OneLifeVibe uses it

OneLifeVibe splits access by server. The account connector at https://onelifevibe.com/mcp handles a signed-in person's own data. The free connector at https://onelifevibe.com/mcp/free handles no-sign-in, read-only use. Today the account connector's sign-in is set up for Meta Muse only, using the public client onelifevibe-muse, and dynamic client registration is open only for Muse callback hosts. Other MCP clients use the free connector.

A platform key is separate. It can call the world catalogue, the tool registry, the network directory tool olv_list_worlds and the event log. GET /tools marks each tool with callable_with_platform_key, so you can check which tools a platform key can call before sending a request.

To work with a person's own data, connect an assistant to the account connector at https://onelifevibe.com/mcp and have the person sign in there. The platform key and the account connector serve different jobs.

Common mistakes

Connecting to https://onelifevibe.com/mcp without a signed-in person is a common error. That endpoint acts with the person's OAuth token, not with a platform key. If you need no sign-in and read-only calls, use https://onelifevibe.com/mcp/free.

Another mistake is treating onelifevibe-muse as a confidential client and sending a client secret. It is a public client with PKCE and no client secret. Use S256 for the code challenge, and do not assume dynamic client registration works for every callback host. Watch the per-person tool call limit too: it applies across all Cloudflare locations, so retries and parallel calls add up.

Questions

What is the difference between the account connector and the free connector?

The account connector at https://onelifevibe.com/mcp acts on a signed-in person's own data using their OAuth token. The free connector at https://onelifevibe.com/mcp/free needs no sign-in and is read-only.

Which OAuth flow does the account connector use?

It uses OAuth 2.1 authorization code with PKCE and the S256 method. The authorization server issuer is https://accounts.onelifevibe.com/realms/olv.

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.