LovedOne Family MCP

What LovedOne Family MCP MCP server does

LovedOne Family MCP MCP server connects an MCP-compatible AI client to a LovedOne family workspace. A workspace can include loved ones, family members, private Family Inbox addresses, incoming messages, and care events. The server provides read access to these records and selected actions for coordinating family communication.

The service is hosted by LovedOne rather than implemented in the repository. Its live endpoint is https://api.lovedone.app/mcp/v1, using Streamable HTTP and JSON-RPC 2.0. The registry name is app.lovedone/family-inbox; the project formerly used com.joinsandwich/care-circle.

How it works

Authenticate with either a LovedOne MCP API key or OAuth 2.1. API keys are created in the LovedOne inbox settings and sent as a bearer token. OAuth uses authorization code flow with PKCE and dynamic client registration. Available OAuth scopes include profile:read, care_circle:read, and care_circle:write.

Read operations are limited to the family workspace associated with the authenticated account or key. The ping tool can verify the connection and returns the caller UID, tenant, and authentication method without PHI. Profile, workspace, loved-one, member, inbox, and care-event tools provide the records an agent can inspect.

Write operations require an owner or coordinator. For OAuth, they also require the care_circle:write scope. API keys use the workspace role rather than this OAuth scope check.

Setup and configuration

Add the hosted endpoint to an MCP client and provide an authorization header such as Bearer YOUR_LOVEDONE_KEY. Cursor and Claude Code can connect directly over HTTP. Claude Desktop can use the mcp-remote bridge with the endpoint and an AUTH_HEADER environment value.

A typical connection uses:

• URL: https://api.lovedone.app/mcp/v1
• Header: Authorization: Bearer YOUR_LOVEDONE_KEY
• API key location: LovedOne inbox settings under MCP keys

LovedOne Family MCP MCP server does not require a locally running process or repository checkout. Revoke keys from the same settings area when access is no longer needed.

Tools and capabilities

The available tools support these workflows:

• Check authentication with ping.
• Retrieve the signed-in profile and linked workspace with get_user_profile.
• List loved ones and their Family Inbox addresses with list_loved_ones.
• Review family roles, relationships, and invitation states with list_family_members.
• Browse recent inbox subjects, senders, categories, and previews with list_inbox_messages.
• Read one inbox message as plain text with get_inbox_message.
• Review recent care events for one loved one or the whole workspace with list_care_events.
• Invite a family member as a coordinator or viewer with invite_family_member.
• Mint a short-lived Soft provider link code for a loved one with create_provider_code.
• Send a plaintext reply with reply_to_inbox_message.

Limitations and notes

LovedOne Family MCP MCP server can return protected health information. Inbox subjects, previews, message bodies, and other family records may contain health information from doctors, pharmacies, insurers, or attorneys. Use a client whose retention and training policies are acceptable for this data.

A key can read the entire associated family workspace, so it should not be shared. Viewer accounts remain read-only. Provider codes are short-lived, and replies may contain PHI. The separate LovedOne Soft and planned LovedOne Pipe endpoints are different services and are not part of this family inbox server.