mcpField
N
NeuroDock Chronometric

NeuroDock Chronometric

Local
neurodock.orgProductivity18Updated 18w ago
RepositoryVisit website

About NeuroDock Chronometric

NeuroDock Chronometric is an in-memory MCP server for time, session, and break management, intended for neurodivergent professionals. It provides time context, session markers, break prompts, and a consent-gated idle status tool; the OS idle probe is currently a stub.

Key features

  1. 01当前时间上下文
  2. 02会话开始与结束标记
  3. 03按需休息提醒
  4. 04经同意的空闲状态查询

Use cases

  1. 01检查当前时间背景
  2. 02记录工作会话的起止
  3. 03判断是否需要休息
  4. 04在授权后查询空闲状态

MCP support

It communicates over MCP stdio and provides five tools for time context, session tracking, break requests, and idle status.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "tlennon-ie-neurodock-mcp-chronometric": {
      "command": "uvx",
      "args": [
        "neurodock-mcp-chronometric"
      ]
    }
  }
}
Run commanduvx neurodock-mcp-chronometric

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypineurodock-mcp-chronometric0.1.0

Tools

5

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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

uv add neurodock-mcp-chronometric
# or
pip install neurodock-mcp-chronometric

Use as an MCP server

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

{
  "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

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:

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

Development

uv sync --all-packages --all-extras
uv run pytest packages/mcp-chronometric/tests/ -v
uv run ruff check packages/mcp-chronometric/
uv run ruff format --check packages/mcp-chronometric/
uv run mypy --strict packages/mcp-chronometric/src/

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.