Assistant tool
olv_get_profile
olv_get_profile returns the name and email of the OneLifeVibe account your assistant is connected to. It is a read-only MCP tool and takes no inputs.
Updated November 6, 2026
- Website
- OneLifeVibe hub
- Class
- Read
- Returns
name, email
Show the name and email of the OneLifeVibe account this assistant is connected to.
Where you can call it
- Account connector https://onelifevibe.com/mcp: needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE), scope olv.read. Its sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.
Inputs
| Argument | Type | Notes |
|---|---|---|
| No arguments. | ||
Example request
POST https://onelifevibe.com/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "olv_get_profile",
"arguments": {}
}
}Other hub tools
- olv_list_worlds List the OneLifeVibe worlds
- find_free_tools Find free tools for a situation
- list_situations List the situations the free tools cover
- gift_ideas Gift ideas and small first purchases
- list_worlds List the OneLifeVibe websites
What it does
olv_get_profile is a Read tool on the OneLifeVibe account connector at https://onelifevibe.com/mcp. It looks up the OneLifeVibe account the assistant is connected to and returns two fields: name and email. It changes nothing, and because it is idempotent, calling it again with the same connection gives the same profile data.
The tool belongs to the OneLifeVibe hub at onelifevibe.com, the front door to the OneLifeVibe network and its developer platform. It has no inputs and no plan requirement is listed. The connection needs the person's OneLifeVibe sign-in through OAuth 2.1 with PKCE and the scope olv.read.
When an assistant should call it
Call it when the person asks which OneLifeVibe account is connected, wants their name or email shown, or needs confirmation before you use other account-connected tools. It is the right call for a simple profile check, not for listing worlds or free tools; those are separate tools on the same website.
Do not call it to test whether a connection exists unless you are prepared to handle a failed sign-in. A successful call confirms the connection because the profile comes back from the signed-in account. If you only need public or no-account results, use the free connector path for the no-account tools instead.
Inputs and an example call
It takes no inputs. Send the tool name olv_get_profile and an empty arguments object. The call goes to the account connector endpoint https://onelifevibe.com/mcp, after the OAuth 2.1 with PKCE sign-in and with the scope olv.read.
An example request body: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"olv_get_profile","arguments":{}}}
For Meta Muse, the account connector's sign-in is set up today with the client onelifevibe-muse. Other MCP clients reach the no-account tools through the free connector; the profile call needs the account sign-in because it reads account data.
What comes back
A successful result contains the name and email of the connected OneLifeVibe account. Those are the only fields the tool returns. There is no account ID, plan, world list or token in the response.
Because the tool is read-only, the response does not change any state. You can call it again to refresh the display, and the same connected account returns the same name and email. Treat the email as personal data: show it only where the person needs it and avoid writing it into logs you do not need.
Errors, limits and safety
The main failure to plan for is authentication. If the OAuth 2.1 with PKCE sign-in is missing or expired, complete the sign-in for https://onelifevibe.com/mcp and retry. If the token lacks the scope olv.read, request that scope; a 401 response generally points to missing or expired authentication, and a 403 generally points to insufficient permission.
No inputs means there is no argument validation to handle, and no rate limit or plan restriction is listed for this tool. The tool is not destructive and is safe to retry after fixing the connection. The sign-in setup on the account connector is for Meta Muse today with client onelifevibe-muse; other MCP clients should use the free connector for the no-account tools and the account sign-in for profile data.
Questions
Does olv_get_profile need a OneLifeVibe account?
Yes. It reads the profile of the account the assistant is connected to, and the account connector requires the person's OneLifeVibe sign-in. No plan requirement is listed for the tool.
What does olv_get_profile return?
It returns the name and email of the connected OneLifeVibe account. It returns no other fields and changes nothing.
Which clients can call olv_get_profile?
The account connector at https://onelifevibe.com/mcp needs OAuth 2.1 with PKCE and scope olv.read. Its sign-in is set up for Meta Muse today with client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector.
Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.