Two MCP servers — this page is the family one

LovedOne Family MCP

A household key lets an agent read that family's loved ones, members, and inbox. It cannot list another family, and it cannot act as a vendor. Providers use LovedOne Soft MCP with a different key.

This product

LovedOne Family MCP

api.lovedone.app/mcp/v1

Mint keys at Settings → MCP API keys on this site.

The other product

LovedOne Soft MCP

api.lovedone.app/mcp/vendor/v1

One provider key → that agency's client roster. A family key on the vendor URL returns 403 WRONG_SURFACE.

Provider MCP docs

Connect

Using an AI agent? Connect LovedOne in 2 minutes (OAuth, no key to copy). Other MCP clients can use a key:

{
  "mcpServers": {
    "lovedone-family": {
      "url": "https://api.lovedone.app/mcp/v1",
      "headers": {
        "Authorization": "Bearer sk-sand-..."
      }
    }
  }
}

Family tools

  • ping

    Smoke-test tool. Returns pong plus the authenticated caller's uid, tenant, and auth method. No side effects.

  • get_user_profile

    Returns the signed-in user's LovedOne profile: uid, email, tenant type, and any linked family workspace.

  • list_loved_ones

    Lists loved ones in the caller's family workspace: id, name, and Family Inbox address.

  • list_family_members

    Lists people on the caller's family workspace (role, relationship, invite status). Emails are personal data — do not log them in third-party agent traces if you can avoid it.

  • list_inbox_messages

    Lists recent messages in one loved one's Family Inbox (subject, sender, preview). Does not return HTML bodies. Scope: the caller's family workspace only.

  • get_inbox_message

    Returns one Family Inbox message as plaintext (no HTML). Requires messageId from list_inbox_messages. Rejected if the message is not in the caller's workspace.

  • invite_family_member

    Invites a sibling or other family member to this household by email, with role coordinator or viewer. Sends the same LovedOne invite email as the web app. Requires the invite-members permission in this workspace. This is a write.

  • create_provider_code

    Mints a short-lived, single-use LovedOne Soft link code for one loved one in this household. Hand the code to a LovedOne Soft agency so they can link that person as a client. Requires the manage-providers permission in this workspace. This is a write.

  • reply_to_inbox_message

    Sends a plaintext reply to a Family Inbox message using the same from address (family-inbox@m.lovedone.app) and reply-to (the loved one's @lovedone.app inbox) as the LovedOne web app. Requires the reply permission for that loved one. This is a write.

  • onboard_loved_one

    Sets up a loved one on LovedOne from conversation: creates the caller's family workspace on first use (or adds to it), allocates their private @lovedone.app Family Inbox address, and records the caller's authorization attestation. Idempotent — calling again for the same person returns the existing record. Before calling, confirm attestAuthorized with the user in plain words. The loved one's own email is optional and is never emailed automatically. This is a write.

  • get_onboarding_status

    Returns the caller's LovedOne setup state: whether a family workspace exists, which loved ones and @lovedone.app inbox addresses are set up, member counts, and ordered nextSteps. Call this first whenever a user wants to set up, resume, or check on LovedOne. Read-only.

Provider tools (not on this server)

  • ping
  • get_agency_profile
  • list_clients
  • get_client
  • list_visits
  • add_visit_note
  • schedule_visit
  • list_invoices

What this server handles

LovedOne Family MCP is senior tech support and Family Inbox coordination for one household. It does not handle personal health data. Tools return inbox plaintext, never raw HTML. API keys are stored as SHA-256 hashes; every call writes an append-only mcp_audit_log row (tool name, caller, timestamp — not message bodies). We are building toward SOC 2 Type I, then Type II. Full specification: LovedOne Family MCP.