myDayLog_
sign in start logging

// daily tag logger · per-user MCP

Log the day.
Let your AI read it.

A short checklist you close out every night — yes or no, sometimes a number — behind a personal MCP endpoint your assistant reads. No streaks, no scores. An honest ✗ counts exactly as much as a ✓.

start logging → how it works

free · sign in with email · myday.qphgldn.top

01 // three states, honestly

✓

yes

It happened. Numeric tags may carry an amount — a yes with no value means happened, amount unrecorded. Never zero.

✗

no

It didn’t. Neutral, never failure — a day of eleven ✗ is exactly as complete as a day of eleven ✓. One tap closes out the rest of the day as ✗, with undo.

·

blank

Unknown. No row is stored, and it is never read as a no. Blanks are the only debt — coverage is answered / expected, not a score.

days are local calendar dates in your own timezone — chosen at sign-up, never shifted

02 // connect an assistant

Every account gets its own MCP connector URL — the token is the credential, scoped to you alone. Paste it into Claude as a custom connector and your assistant can log days, find the gaps, and correlate what you logged against physiological data held elsewhere.

claude — connectors
$ claude mcp add mydaylog https://myday.qphgldn.top/mcp \
--header "Authorization: Bearer mdl_••••••••"
✓ connected
> call get_context
{ timezone: "Europe/London", tags: 11, open_days: 3 }
Log today’s checklist Find unfinished days Correlate a tag against external data

ships as prompts in the connector’s menu — no setup beyond the paste

03 // yours, portable

install

A PWA — open it on your phone and add to home screen. Chromeless, built for the sixty-second nightly close-out.

export

/export.csv and /export.json — the designed escape hatch. Every row you own, one request.

isolate

Tags, entries, timezone, token — everything is per-user. The MCP token is stored hashed; regenerating it kills the old URL immediately.

Close out today.

Eleven questions take about a minute. The data compounds.