Assistant tool

olv_list_connectors

Lists every OneLifeVibe connector with its category, what an assistant can do there, its MCP address and counts. No account needed.

Updated November 16, 2026

Website
OneLifeVibe hub
Class
Read · no account needed
Returns
connectors[]: id, name, category, tagline, auth, counts {actions, triggers}, mcp_url, page

List every OneLifeVibe connector (no account needed): each website, what an assistant can do there, what it can tell your apps, and its connector address. Optional category.

Where you can call it

Inputs

ArgumentTypeNotes
category optionalnetwork | agents | work | giving | family | love | shopping | sky | civic | business | legacy

Example request

POST https://onelifevibe.com/mcp/free

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "olv_list_connectors",
    "arguments": {}
  }
}

Other hub tools

What it does

olv_list_connectors reads the OneLifeVibe network directory and returns one entry per connector. A connector is one website in the network, and each entry tells you what an assistant can do there and what that site can tell your apps.

It is a Read tool. It changes nothing and gives the same answer for the same arguments, so you can call it when a client connects, when a new question arrives, or on a retry without worrying about side effects.

By default you get the whole directory. Pass the optional category argument to narrow it to one area.

When an assistant should call it

Call it before any other OneLifeVibe tool. The result tells you which connectors exist, what each one covers and the address to add, so an assistant that doesn't know the network can plan instead of guessing.

Typical moments: the user asks which sites are in the network, you have a task and need to know which connector covers it, or you're setting up a client and want the connector addresses to offer. Add a category when the request clearly sits in one area, such as giving, work or family.

Skip it if you already have a fresh list in the conversation. Reuse what you have rather than polling, especially on the free endpoint.

Inputs and an example call

One optional input. category takes a single value: network, agents, work, giving, family, love, shopping, sky, civic, business or legacy. Leave it out to get everything. There are no other arguments.

Send a tools/call to https://onelifevibe.com/mcp/free:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"olv_list_connectors","arguments":{}}}

Put the filter inside arguments, for example "category": "giving". The same tool is served on https://onelifevibe.com/mcp, where it runs with no token or identity.

Let your MCP client send the request. It handles the JSON-RPC framing and the response envelope.

What comes back

The response gives you connectors[], a list of objects. Each one has id, name, category, tagline, auth, counts, mcp_url and page.

counts holds actions and triggers: the number of things an assistant can do on that site and the number of things it can tell your apps about. auth tells you what sign-in that connector expects. mcp_url is the address you add to a client. page is the site itself.

The shape is the same for every connector, so one loop can render the list or pick a match by category and name.

Errors, limits and safety

Read only, and idempotent. Two calls with the same arguments give the same list, and nothing in the reply changes an account.

The account connector never returns account data for this tool, because it is called with no token or identity. Don't read the result as proof that a user is signed in, and don't expect it to describe anyone's own settings.

The free connector is rate-limited. If a call fails or you hit the limit, back off, retry once, and keep the list you already have. A JSON-RPC error carries a code and a message, so log both with the request id. category accepts only the eleven values listed above.

Questions

Do I need an account to list the OneLifeVibe connectors?

No. olv_list_connectors works on the free connector at https://onelifevibe.com/mcp/free with no sign-in, and it returns the network directory the same way on the account connector.

What is mcp_url in the response?

It is the address you add to an MCP client to reach that connector. The auth field next to it tells you what sign-in that connector expects.

Can I filter OneLifeVibe connectors by category?

Yes. Pass category with one of network, agents, work, giving, family, love, shopping, sky, civic, business or legacy. Leave the argument out to get every connector.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.