LovedOne Family MCP

app.lovedonev0.3.0Updated Oct 7, 2026

Family inbox: read records; invite, reply, mint codes. API key or OAuth care_circle:write.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant read a family care inbox and records, summarize messages, invite family members, mint provider codes, and send replies.

What it does
Connects to the LovedOne Family Inbox service for families caring for an aging parent. Read tools list loved ones, family members, inbox messages, and care events, and fetch a single message as plain text. Write tools invite a family member by email, mint a short-lived provider link code, and send a plaintext reply to an inbox message.
When to use it
Useful when a family already keeps a LovedOne inbox and wants an assistant to summarize incoming mail from doctors, pharmacies, insurers, or attorneys, track who is handling what, or draft and send replies. Not needed if you do not use LovedOne.
Requirements
Remote Streamable HTTP endpoint; no local package. Requires a LovedOne MCP key sent as the Authorization header in Bearer form, or OAuth 2.1 with the care_circle:write scope for write tools. Write tools also need an owner or coordinator role.
Before you install
Inbox content can include protected health information in subjects, previews, and bodies, so only connect a client you trust with that data and check its retention and training settings. The Authorization key can read the whole family workspace; do not share it and revoke it when done. Invite, provider-code, and reply tools write and send data.

Installation

In SourceWeft

  1. Open LovedOne Family MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "family-inbox": {
      "type": "http",
      "url": "https://api.lovedone.app/mcp/v1"
    }
  }
}

README

LovedOne MCP servers

This repo lists LovedOne's Model Context Protocol servers in the official MCP Registry. All three live under the app.lovedone/* namespace, which is lovedone.app written backwards.

ServerRegistry nameEndpointStatus
LovedOne Family Inboxapp.lovedone/family-inboxhttps://api.lovedone.app/mcp/v1Live
LovedOne Soft MCPapp.lovedone/softhttps://api.lovedone.app/mcp/vendor/v1Live
LovedOne Pipe MCPapp.lovedone/pipehttps://api.lovedone.app/mcp/pipe/v1 (planned)Not live yet

The public provider directory is a separate server, com.joinsandwich/directory (https://www.joinsandwich.com/api/mcp, no key needed). It isn't part of this repo.

This is a public listing repo (README, server.json files, LICENSE). The MCP servers are hosted at the endpoints above; their source is not in this repo.

LovedOne Family Inbox

The family inbox MCP for LovedOne, the family inbox for people caring for an aging parent. Each loved one gets a private @lovedone.app address for doctors, pharmacies, insurers, and attorneys, and every message lands in one inbox the whole family can see. This MCP lets an AI assistant summarize your own family's inbox and care records, invite family, mint provider codes, and reply to messages.

⚠️ Health information

LovedOne inboxes hold mail from doctors, pharmacies, and insurers, so responses can contain protected health information (PHI), including in message subjects, previews, and bodies.

  • Only connect LovedOne to an AI client you trust with that data, and check that client's data-retention and training settings first.
  • A key can read your whole family workspace. Don't share it, and revoke it at inbox.lovedone.app/settings/mcp-keys when you're done.
  • Write tools (invite, provider codes, replies) need an owner/coordinator and, for OAuth, the care_circle:write scope. Viewers stay read-only.

Authentication

  • API key (supported): create a key at inbox.lovedone.app/settings/mcp-keys and send it as Authorization: Bearer <key>.
  • OAuth 2.1: LovedOne runs an OAuth authorization server at https://inbox.lovedone.app (authorization code + PKCE, dynamic client registration). Public scopes: profile:read, care_circle:read, and care_circle:write. Write tools require care_circle:write on OAuth tokens; API keys skip the scope gate and use workspace role.

Connect

Cursor (~/.cursor/mcp.json or .cursor/mcp.json):

json
{  "mcpServers": {    "lovedone": {      "url": "https://api.lovedone.app/mcp/v1",      "headers": { "Authorization": "Bearer YOUR_LOVEDONE_KEY" }    }  }}

Claude Code:

bash
claude mcp add --transport http lovedone https://api.lovedone.app/mcp/v1 \  --header "Authorization: Bearer YOUR_LOVEDONE_KEY"

Claude Desktop (claude_desktop_config.json, via the mcp-remote bridge):

json
{  "mcpServers": {    "lovedone": {      "command": "npx",      "args": [        "-y", "mcp-remote", "https://api.lovedone.app/mcp/v1",        "--header", "Authorization:${AUTH_HEADER}"      ],      "env": { "AUTH_HEADER": "Bearer YOUR_LOVEDONE_KEY" }    }  }}

Then ask: "Summarize this week's messages in Mom's inbox and who's handling each one."

Tools

Read tools are scoped to the key owner's family workspace. Write tools need an owner/coordinator and OAuth care_circle:write when the caller is OAuth.

ToolWhat it does
pingSmoke test: returns the caller's uid, tenant, and auth method. No PHI.
get_user_profileThe signed-in user's profile and linked family workspace.
list_loved_onesLoved ones on the workspace: id, name, and Family Inbox address.
list_family_membersPeople on the workspace: role, relationship, invite status.
list_inbox_messagesRecent messages in one loved one's inbox (subject, sender, category, preview). May contain PHI.
get_inbox_messageOne message as plain text. May contain PHI.
list_care_eventsRecent care events, for one loved one or across the workspace.
invite_family_memberWrites. Invites a sibling or other family member by email (coordinator or viewer).
create_provider_codeWrites. Mints a short-lived Soft provider link code for one loved one.
reply_to_inbox_messageWrites. Sends a plaintext reply to a Family Inbox message. May contain PHI.

LovedOne Soft MCP

The developer MCP for care agencies on LovedOne Soft. One key covers one agency. Agents and developers can read the agency's clients, visits, and invoices, log visit notes, and schedule visits. A note on a client who is linked to a LovedOne family inbox is copied into that family's inbox. Auth is an agency API key or OAuth (profile:read, care_circle:read, care_circle:write).

  • 🌐 Endpoint: https://api.lovedone.app/mcp/vendor/v1 (Streamable HTTP, JSON-RPC 2.0)
  • ℹ️ Path note: the live Soft MCP is /mcp/vendor/v1, not /mcp/soft/v1 (that path is not an MCP route today). Family inbox is /mcp/v1, not bare /mcp.
  • 🔑 MCP key: sign in at soft.lovedone.app, then go to Settings → MCP keys
  • 📚 Docs: docs.lovedone.app/mcp-vendor · soft.lovedone.app/agents
  • 🗂️ Registry name: app.lovedone/soft
  • 📄 Listing file: soft/server.json

A family key on this endpoint (or an agency key on the family endpoint) is rejected with HTTP 403 WRONG_SURFACE.

⚠️ Visit notes can contain health information. The same rules as the family inbox apply: use a trusted client and revoke keys you no longer need.

Cursor:

json
{  "mcpServers": {    "lovedone-soft": {      "url": "https://api.lovedone.app/mcp/vendor/v1",      "headers": { "Authorization": "Bearer YOUR_SOFT_KEY" }    }  }}

Claude Code:

bash
claude mcp add --transport http lovedone-soft https://api.lovedone.app/mcp/vendor/v1 \  --header "Authorization: Bearer YOUR_SOFT_KEY"
ToolWhat it does
pingSmoke test: returns the caller's uid, tenant, and auth method. No PHI.
get_agency_profileThe agency: id, name, slug, plan, and the caller's role.
list_clientsThe agency's clients, and whether each is linked to a family inbox.
get_clientOne client plus recent visits and notes. May contain PHI.
list_visitsVisit and note events, for the agency or one client. May contain PHI.
add_visit_noteWrites. Logs a note on a client; copies it to a linked family inbox. OAuth needs care_circle:write.
schedule_visitWrites. Creates a scheduled visit for a client. OAuth needs care_circle:write.
list_invoicesInvoices the agency issued to families (amounts, status).

LovedOne Pipe MCP (coming later)

LovedOne Pipe MCP will connect LovedOne to healthcare systems, bringing partner events from EHR and EVV systems into a family's care record.

  • 🚧 Status: not live. https://api.lovedone.app/mcp/pipe/v1 is the planned endpoint and does not answer yet. Don't add it to a client.
  • 🗂️ Registry name (reserved): app.lovedone/pipe
  • 📄 Listing file: pipe/server.json, which won't be published until the endpoint is live.

Links

Source: README.md at commit 663071c

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.3.0LatestOct 7, 2026