LovedOne Family MCP server

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.

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.

• 📚 Docs: docs.lovedone.app/mcp-family · inbox.lovedone.app/agents
• 🌐 Endpoint: https://api.lovedone.app/mcp/v1 (Streamable HTTP, JSON-RPC 2.0)
• 🔑 MCP key: sign in, then go to inbox.lovedone.app/settings/mcp-keys
• 🗂️ Registry name: app.lovedone/family-inbox (formerly com.joinsandwich/care-circle)
• 📄 Listing file: server.json

⚠️ 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.

that client's data-retention and training settings first.

• Only connect LovedOne to an AI client you trust with that data, and check

revoke it at inbox.lovedone.app/settings/mcp-keys when you're done.

• A key can read your whole family workspace. Don't share it, and

and, for OAuth, the care_circle:write scope. Viewers stay read-only.

• Write tools (invite, provider codes, replies) need an owner/coordinator

Authentication

inbox.lovedone.app/settings/mcp-keys and send it as Authorization: Bearer .

• API key (supported): create a key at

https://inbox.lovedone.app (authorization code + PKCE, dynamic client registration). Public scopes: profile:read, carecircle:read, and carecircle:write. Write tools require care_circle:write on OAuth tokens; API keys skip the scope gate and use workspace role.

• OAuth 2.1: LovedOne runs an OAuth authorization server at

Connect

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

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

Claude Code:

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

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

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

Shortened. The full README is on GitHub.