Wee HoursConnect your AI assistant
Wee Hours records facts. Your assistant interprets them: totals, patterns, a summary before the pediatrician visit, or "when should we expect the next feed?". It connects to your log over MCP (Model Context Protocol), an open standard supported by Claude, ChatGPT and many other tools.
Your server URL
…
The same for every household. Your sign-in or token decides whose log the assistant sees.
Pick how to connect
Assistants that support sign-in (OAuth) need only the URL: you sign in with your Wee Hours account and approve access. For tools that don't, create a personal access token and paste it in.
- In Claude (web or desktop), open Settings → Connectors and choose Add custom connector.
- Name it Wee Hours and paste the server URL above.
- Choose Connect. Sign in with the account you use in the app, then choose Allow.
- In a chat, turn on the Wee Hours connector and ask something like “When did the baby last eat?”
- In ChatGPT, open Settings → Apps & Connectors. Custom connectors need Developer mode, under Advanced settings.
- Choose Create, name it Wee Hours, paste the server URL above and pick OAuth for authentication.
- Sign in with the account you use in the app, then choose Allow.
- Add the connector to a chat and ask away.
ChatGPT moves these menus around. If they've changed, look for “connectors” or “MCP” in its settings.
Create a token on your account page, then run:
claude mcp add --transport http wee-hours MCP_URL \
--header "Authorization: Bearer wh_your_token"Most clients (Cursor, Windsurf, VS Code, Zed and others) take a JSON entry like this one. Create a token on your account page and put it in place of wh_your_token.
{
"mcpServers": {
"wee-hours": {
"url": "MCP_URL",
"headers": { "Authorization": "Bearer wh_your_token" }
}
}
}The transport is Streamable HTTP. Clients that support only stdio can connect through a bridge such as mcp-remote.
Read or write
A token is read-only unless you allow logging when you create it. A read-only assistant can answer questions but can't change the log. With write access it can also add entries, undo them and resolve duplicates, exactly as you could in the app. Every entry it makes is marked as coming from that assistant.
Assistants connected by sign-in get write access. You can disconnect them, or revoke a token, at any time on your account page or in the app under Settings → AI agents.
What your assistant can do
| Tool | What it does | Access |
|---|---|---|
get_status | The one-line status (last feed, next side, last diaper, sleep), who's on duty and any duplicates to resolve | read |
list_children | Every child (name, birth date, age, bottle size), the tracked categories and the caregivers | read |
get_baby_profile | One child's name, birth date, enabled categories and household settings | read |
list_event_types | The kinds of entries and their fields | read |
list_events | Entries in a time range, optionally filtered by type | read |
log_event | Add an entry, validated exactly like the app | write |
undo_event | Undo an entry (it stays in history as undone) | write |
resolve_duplicate | Merge a duplicate or keep both | write |
import_events | Bring in history from another tracker's export (dry run first; re-runs skip what's already there) | write |
undo_import | Take a whole import back | write |
set_tracking | Turn tracking categories on or off for the household | write |
Things to ask
- “How many wet diapers in the last 24 hours?”
- “Make a table of feeds since Monday with total ml per day.”
- “Summarize this week for our pediatrician visit tomorrow.”
- “How long are her night stretches getting?”
- “Log a bottle, 90 ml, at 4:15.” (needs write access)