NeuroDock Chronometric — Claude Code MCP server: setup
This MCP server gives an agent time context, session markers, and break checks. It fits workflows where passing time is easy to miss.
claude mcp add neurodock-mcp-chronometric -- uvx neurodock-mcp-chronometricWhat NeuroDock Chronometric does
NeuroDock Chronometric exposes tools for time-aware work: get_time_context, mark_session_start, mark_session_end, request_break_if_needed, and idle_status. A new session marker closes an earlier open session automatically, while explicit start and end calls keep the session state clear.
Session data lives in memory in the developer preview. Restarting Claude means an open session is treated as closed when mark_session_start runs next. The server uses MCP stdio and reads ~/.neurodock/profile.yaml; tests can point to another profile with NEURODOCK_PROFILE_PATH.
idle_status requires consent through privacy.os_idle_consent: true. The operating-system idle probe currently returns None on every platform, so this tool cannot yet detect inactivity itself.
What it helps with
- read the current time context
- mark when a work session begins
- close an earlier session on a new start
- ask whether a break is needed
- check idle state after consent
Example prompts for the agent
- Show my current time context with
get_time_context. - Mark the start of this work session using
mark_session_start. - Check whether I should take a break with
request_break_if_needed.
How to install NeuroDock Chronometric
Platform CLI
claude mcp add neurodock-mcp-chronometric -- uvx neurodock-mcp-chronometricuvx runs the command named after the package; if the README names another one, use uvx --from neurodock-mcp-chronometric <command>
Platform CLI
codex mcp add mcp-chronometric -- uvx neurodock-mcp-chronometricuvx runs the command named after the package; if the README names another one, use uvx --from neurodock-mcp-chronometric <command>
Config file
{
"mcpServers": {
"mcp-chronometric": {
"command": "uvx",
"args": [
"neurodock-mcp-chronometric"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from neurodock-mcp-chronometric <command>
Config file
{
"servers": {
"mcp-chronometric": {
"type": "stdio",
"command": "uvx",
"args": [
"neurodock-mcp-chronometric"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from neurodock-mcp-chronometric <command>
Platform CLI
gemini mcp add mcp-chronometric uvx neurodock-mcp-chronometricuvx runs the command named after the package; if the README names another one, use uvx --from neurodock-mcp-chronometric <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about NeuroDock Chronometric
How do I install NeuroDock Chronometric in Claude Code?
Run claude mcp add neurodock-mcp-chronometric -- uvx neurodock-mcp-chronometric. Claude Code will then have the MCP server configured.
What does NeuroDock Chronometric do?
It gives an agent tools for time context, session start and end markers, break requests, and idle-state checks.
What does idle_status need to work?
Set privacy.os_idle_consent: true in ~/.neurodock/profile.yaml. The OS probe still returns None on every platform in v0.0.2.
