LovedOne Family MCP

app.lovedonev0.3.0更新于 Oct 7, 2026

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

已验证Streamable HTTP可网页运行Productivity & WorkflowCommunication & Collaboration

概览

AI 生成的概览

让助手读取家庭照护收件箱与记录、汇总消息、邀请家人、生成服务方代码并发送回复。

功能
连接到面向照护年长父母家庭的 LovedOne Family Inbox 服务。读取类工具可列出被照护者、家庭成员、收件箱消息和照护事件，并以纯文本获取单条消息。写入类工具可通过电子邮件邀请家庭成员、生成短期服务方链接代码，并向收件箱消息发送纯文本回复。
适用场景
适合已在使用 LovedOne 收件箱的家庭，让助手汇总来自医生、药房、保险公司或律师的来信、了解各人负责的事项，或起草并发送回复。若不使用 LovedOne 则无需添加。
运行要求
远程 Streamable HTTP 端点，无需本地安装包。需要 LovedOne MCP 密钥，以 Bearer 形式放在 Authorization 请求头中；写入类工具也可用带 care_circle:write 范围的 OAuth 2.1。写入类工具还需要所有者或协调者角色。
安装前请注意
收件箱内容可能在主题、预览和正文中包含受保护的健康信息，因此只连接你信任其处理这些数据的客户端，并先查看其数据保留与训练设置。Authorization 密钥可读取整个家庭工作区，请勿分享，并在用完后撤销。邀请、服务方代码和回复工具会写入并发送数据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 LovedOne Family MCP，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

来源：README.md，提交 663071c

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v0.3.0最新Oct 7, 2026