lindly

Connect lindly to your smart-home hub via MCP

5 steps3 min read
  1. In this guide
  2. 1.Check your hub speaks MCP
  3. 2.Add lindly's MCP server to your hub
  4. 3.Grant per-kid, per-scope access
  5. 4.Read your baby's status into automations
  6. 5.Log events from a button or voice command

Because lindly exposes its data over the Model Context Protocol (MCP), any smart-home hub that can act as an MCP client can connect to your Home — reading your baby’s current status into an automation, or logging an event when you press a button or speak a command.

A note on scope. “Smart-home hub” is our reading of a still-provisional idea, so treat this as a worked example rather than a fixed integration. We use Home Assistant here because it has documented MCP client support today; the exact hubs we officially support will firm up over time. The MCP endpoint itself (mcp.lindly.app) goes live at launch.

1. Check your hub speaks MCP

Your hub needs to be able to act as an MCP client — to connect out to an MCP server and use its tools. Home Assistant, for example, can do this. If your hub can’t yet, you can still bridge through an assistant that can (see the AI assistant guide).

2. Add lindly’s MCP server to your hub

Point your hub’s MCP client at lindly’s server URL (mcp.lindly.app). The server supports dynamic client registration and PKCE, so your hub can discover the sign-in endpoints and complete an OAuth login without any manual key wrangling. You sign in as yourself.

3. Grant per-kid, per-scope access

As with any lindly MCP connection, consent is granular: you choose which Home, which child or children, and which scopes the hub may use. For a smart-home setup you’ll often want read-only access — enough to surface status, nothing that can write to your log. If you do want the hub to log events, grant the write scope deliberately.

4. Read your baby’s status into automations

With read access, your hub can call lindly’s read tools inside automations:

  • get_kid_summary — announce status on a smart speaker: “Mia has been asleep for 40 minutes; last feed two hours ago.” Great for a morning routine or a nursery dashboard.
  • list_active_reminders — light up a hallway lamp softly when a reminder is active, so a gentle “it’s been a while — all good?” has an ambient cue instead of a phone buzz.
  • list_recent_events and list_kids — feed a dashboard tile or a status card.

Everything the hub reads is scoped to what you granted, and it runs as you.

5. Log events from a button or voice command

If you granted the write scope, a physical button or a voice command can call log_event — tap a nursery button to log a diaper change, or say “log a nap” to start one. log_event is flagged as a write, goes through the same validation and per-child access checks as the app, and is idempotent, so a double-press won’t create a duplicate. The entry is stamped to your identity automatically.

Start read-only, add writing only where you want it, and keep the grant as tight as the job needs. That’s the whole idea: your baby’s timeline, available to the tools you already live with — on your terms.