Nestling

Name: Nestling
Author: kparmesar

@kparmesar

About Nestling

Nestling is an MCP server that lets you log and query your baby's daily routine. Feeds, sleep, nappy changes, and diary entries through natural conversation with Claude or any MCP-compatible AI assistant. Logged through the Nestling app for iOS and Android.

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "nestling": {
      "command": "bun",
      "args": [
        "run",
        "nestling-mcp"
      ],
      "cwd": "/absolute/path/to/nestling-ts",
      "env": {
        "NESTLING_API_TOKEN": "your-token-from-nestling-app",
        "NESTLING_TIMEZONE": "Europe/London"
      }
    }
  }
}

Tools

Discovery: what data sources and tools are available

Account profile (email, user ID)

Baby roster (`id` is passed to every other tool)

Baby details (nickname, birth date, etc.)

Sleep sessions for a baby in a date range

Feeding entries (breast, bottle, solids) in a date range

Nappy/diaper entries in a date range

Diary/journal entries in a date range

Log a new sleep session (start + end time)

Log a new feed (breast, bottle, solids, expressing)

Log a new nappy/diaper change

Log a new diary/journal entry

Overview

What is Nestling?

Nestling is a TypeScript client, CLI, and MCP server for the Nestling baby tracking app. It reads and logs sleep, feed, nappy, and diary data from your Nestling account via terminal, library, or AI assistants like Claude and ChatGPT.

How to use Nestling?

Install globally with bun add -g nestling-ts, then run nestling login to authenticate and use CLI commands like nestling sleep history. For MCP integration, point Claude or ChatGPT at the nestling-mcp binary (stdio or HTTP mode). The library is imported as import { Nestling } from "nestling-ts".

Key features of Nestling

CLI and library for reading and logging baby data
MCP server for AI assistants (Claude, ChatGPT, etc.)
Create-only writes – cannot update or delete entries
Supports sleep, feed, nappy, and diary entries
HTTP or stdio transport for MCP
User-scoped authentication with Supabase Row Level Security

Use cases of Nestling

Log a sleep session from the terminal: nestling sleep log --start "yesterday 8pm" --end "today 6:30am"
Query feeding history for the last two days: nestling feed history --days 2
Let an AI assistant read and log baby data via MCP tools
Automate baby tracking with scripts using the TypeScript library
Self-host a remote MCP endpoint for multiple users

FAQ from Nestling

What does Nestling do that the Nestling app cannot?

Nestling provides a programmatic interface (CLI, library, MCP) to read and log data, but it is create-only — it cannot update or delete existing entries.

What are the dependencies to run Nestling?

Bun 1.3+ (the package is raw TypeScript, not Node-compatible), a Nestling account, and an API token generated from the app (Settings → Data → API Token).

Where does my data live when using the MCP server?

In stdio mode, credentials stay on your machine. In HTTP mode, you can self-host or use the hosted endpoint (https://mcp.nestling-app.com/mcp). All data is stored in Supabase with Row Level Security per user.

What transport modes does the MCP server support?

Two modes: stdio (default, for local tools like Claude Desktop) and HTTP (for remote clients like ChatGPT custom connectors).

How is authentication handled?

Authentication uses an API token passed via environment variable (NESTLING_API_TOKEN) or config file. The token is used to bootstrap a short-lived Supabase session (auto-refreshed after 1 hour). No service keys are used.