tlennon-ie/neurodock

A cognitive substrate that remembers, paces, and refuses. Built with neurodivergent professionals, not for them.
5-second TL;DR
- **What it does:** gives Claude a memory of your work, a sense of time, a refuse-rumination guardrail, and a translator for corporate ambiguity.
- **Who it's for:** neurodivergent people — self-ID only, no diagnosis required, no gatekeeping.
- **How to install:** one command, below.
NeuroDock plugs into Claude Desktop / Claude Code / Cursor (any MCP-aware
client). Local-first by default. No telemetry. AGPL-3.0-or-later.
How it fits together
You chat with Claude exactly like normal. Under the hood, Claude calls
NeuroDock's local MCP servers; they read and write your local store; the
result flows back into Claude's reply.
Everything runs on your laptop. Nothing leaves your machine unless you
explicitly turn on a cloud option.
Install
One command. It pip-installs the five MCP servers (plus the neurodock-evals
harness), wires Claude Desktop / Claude Code / Cursor, and drops a starter
profile at ~/.neurodock/profile.yaml.
Then, **in any conversation**, try one of:
Claude calls the MCP tools under the hood; you just talk.
> ### 🛑 First-time gotcha: full-quit Claude before testing
>
> Claude only reads its MCP config at startup. **Closing the window is not
> enough.** This is the #1 silent failure people hit.
>
> - **macOS:** Cmd + Q (or Claude menu → Quit Claude).
> - **Windows:** right-click the Claude icon in the system tray → **Quit**.
> - **Linux:** kill the process (pkill -f Claude or quit from the tray).
>
> Then reopen Claude and try one of the prompts above.
Requires Python 3.11+ and Node 22+. Works on macOS, Linux, Windows.
> **Why @latest?** If you previously ran npm install -g @neurodock/cli,
> npx will silently reuse that older global install instead of fetching the
> current version — and old versions don't have install-all. The @latest
> tag forces npx to resolve against the npm registry every time. Same reason
> we use it on update.
Want to install it step-by-step instead?
NeuroDock ships across two registries: the Python **MCP servers** (MCP =
Model Context Protocol — the standard that lets Claude call local tools)
on PyPI, and the user-facing **CLI** on npm. The CLI wraps everything else.
**1. Install the six MCP servers**
**2. Wire them into your MCP-aware client**
Detects Claude Desktop, Claude Code, or Cursor and writes the server
entries automatically.
**3. Restart Claude** (full quit, not close-window — see the callout above).
**About the neurodock command** — it lives on npm as @neurodock/cli,
**not** on PyPI. The pip install step gives you the MCP server binaries
that Claude calls over stdio; the CLI is separate. Two ways to run it:
@neurodock/cli exposes: init, doctor, validate, update, sync,
uninstall, host install, host uninstall, profile show,
profile validate, install-all, install-hooks, examples,
plugin add/remove/list/enable/disable/validate.
Proactive guardrails (optional, recommended)
By default NeuroDock waits for you to ask. That's the wrong shape — an
ND user in hyperfocus is the one least likely to remember to run a
break tool. One command flips it:
This wires a small Python script (bundled, stdlib-only — no extra
install needed) into Claude Code's hook system. It then runs silently
on every tool call and auto-fires the chronometric / rumination /
sycophancy heuristics when patterns trip. You get a one-line stderr
banner on the next prompt — never blocked, always dismissible.
For host-agnostic coverage (catches you working in the terminal at
02:00 too), add the standalone daemon:
That registers a per-user autostart entry (HKCU Run on Windows,
LaunchAgent on macOS, systemd --user on Linux). The daemon polls
every 5 min and surfaces OS-native notifications.
Opt out anytime:
The browser extension carries its own equivalent (Phase 2 watchdog) —
it's enabled by default and toggleable from chrome.storage.local via
the popup Settings tab.
See docs/.../proactive-guardrails for the design behind this and the