NeuroDock Chronometric

io.github.tlennon-iePublished by GitHub account tlennon-iev0.1.0Updated Nov 3, 2026

Externalises time-of-day, session boundaries, and break prompts for time-blind users.

Overview

AI-generated overview

Local MCP server that gives an assistant time-of-day context, session start/end markers, break prompts and idle status for time-blind users.

What you can do
  • Read the current time context and session boundaries
  • Mark a session as started or ended, with a new start auto-closing any prior open session
  • Ask whether a break is needed and get a break prompt
  • Check idle status, gated by consent in the local profile
When to use it
Useful for time-blind or neurodivergent users who want an assistant to keep track of time of day, session boundaries and break reminders during a working session. It is an early developer preview, so it suits experimentation rather than dependable long-term tracking.
Requirements
Runs locally over stdio, installed from PyPI with uv or pip and launched via uv run. Needs a local profile file at ~/.neurodock/profile.yaml, whose path can be overridden with NEURODOCK_PROFILE_PATH. No authentication or API keys are declared.
Before you install
Session state is in-memory only in this preview, so restarting the client loses open sessions and they are treated as auto-closed. The OS idle probe is a stub that returns nothing, and idle status only proceeds when consent is enabled in the profile. It reads a local profile file, so review what that file contains before pointing the server at it.

Installation

In SourceWeft

  1. Open NeuroDock Chronometric in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

neurodock-mcp-chronometric

Time, idle, and break management as an MCP server. Part of NeuroDock — a local-first cognitive substrate for neurodivergent professionals.

Version: 0.0.2 (developer preview, in-memory).

Install

sh
uv add neurodock-mcp-chronometric# orpip install neurodock-mcp-chronometric

Use as an MCP server

Add to your ~/.claude.json (Claude Code) or claude_desktop_config.json (Claude Desktop):

json
{  "mcpServers": {    "neurodock-chronometric": {      "command": "uv",      "args": ["run", "neurodock-mcp-chronometric"]    }  }}

Status

v0.0.x implements the five tools specified in ADR 0001 — chronometric tool design:

ToolStatus
get_time_contextimplemented
mark_session_startimplemented; auto-closes prior open session
mark_session_endimplemented
request_break_if_neededimplemented
idle_statusimplemented; consent-gated, OS probe is a stub

Session state is intentionally in-memory for the v0.0.x preview — a single Claude session typically ends with an explicit mark_session_end so durable storage is not on the hot path. SQLite-backed session history is planned for v0.1.0 per ADR 0001; until then, restart Claude and any open session is treated as auto-closed on the next mark_session_start.

The OS idle probe is intentionally a no-op stub in v0.0.2: the consent gate is the hard correctness property, and the probe itself returns None on every platform until per-platform implementations and tests land.

References

Running

sh
uv run neurodock-mcp-chronometric

The server speaks the MCP stdio transport.

Profile

Reads ~/.neurodock/profile.yaml. Override with NEURODOCK_PROFILE_PATH (used in tests). Fields consumed in v0.0.2:

yaml
privacy:  os_idle_consent: true # required for idle_status to perform the OS probechronometric:  zones: {} # reserved for v0.1.x profile-declared zone overrides

Development

sh
uv sync --all-packages --all-extrasuv run pytest packages/mcp-chronometric/tests/ -vuv run ruff check packages/mcp-chronometric/uv run ruff format --check packages/mcp-chronometric/uv run mypy --strict packages/mcp-chronometric/src/

Source: packages/mcp-chronometric/README.md at commit 2d9cac6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts