Option B — install once, call 'neurodock' from anywhere

npm install -g @neurodock/cli neurodock doctor

@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:

sh
neurodock install-hooks --self-test

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:

sh
neurodock install-hooks --install-daemon --self-test

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:

sh
neurodock install-hooks --uninstall # removes both
export NEURODOCK_GUARDRAILS=off # disables without removing

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

opt-out matrix.
Want to see it work without installing from PyPI/npm at all?

TESTING_LOCAL.md walks through the from-clone path.
</details>
<details>

<summary><strong>Prefer a plugin, a one-click desktop extension, or the MCP Registry?</strong></summary>
The install-all command above is the recommended path. The same servers are

also distributed through three standard channels — all install the identical

local stdio servers, so you can pick whichever fits your client:
Claude Code plugin — bundles the five MCP servers _and_ a set of ND-aware

skills in one step. Requires uv (the servers

run via uvx).

/plugin marketplace add tlennon-ie/neurodock
/plugin install neurodock@neurodock

Claude Desktop extension (.mcpb) — one-click install, no config editing.

One bundle per server under mcpb/; build with

npx @anthropic-ai/mcpb pack mcpb/neurodock-mcp-translation and drag the

.mcpb onto Claude Desktop → Settings → Extensions. Requires uv.

Official MCP Registry — each server ships a

server.json and is published to

registry.modelcontextprotocol.io

under the io.github.tlennon-ie/* namespace, so MCP-aware clients can discover

them directly.
Hosted remote server (no install) — the stateless tools (translation,

guardrail, and decompose) are also served over OAuth at a hosted HTTPS

endpoint, so you can use them with no local install and no uv:

https://mcp.neurodock.org/mcp

In Claude (claude.ai or Desktop) → Settings → Connectors → Add custom

connector → paste that URL → complete the sign-in prompt. The eight stateless

tools appear immediately. An opt-in memory surface (enable_hosted_storage,

connect_byos_storage, record_fact, recall_entity, …) is also exposed but

does nothing until you explicitly enable storage for your signed-in account. The

personal cognitive graph and neurotype profile are never hosted — they stay

on the local install. Full walkthrough: Hosted server.

The hosted remote server is live at mcp.neurodock.org.
</details>
Update

sh
npx --yes @neurodock/cli@latest update

One command. Upgrades all six MCP servers (pip install --upgrade /

uv tool install), refreshes your wired client configs, and

re-registers the optional native-messaging host. Same flags as

install-all (--client, --profile, --installer, --dry-run,

--no-native-host, --yes).

The browser extension auto-updates through the Chrome / Firefox / Edge

store; sideloaded users git pull and rebuild.
> Full-quit Claude after updating so it re-reads its MCP config — same

> as first install.
Just want to re-shape client configs without touching package versions?

Use neurodock sync.
See it in action
The cognitive substrate in a real session — you talk to Claude normally;

under the hood it calls NeuroDock's MCP tools to remember, pace, and decompose.
https://github.com/user-attachments/assets/bcbf65ce-88dd-4f83-8dc1-d56bdde01bed
The browser extension — translating corporate-speak inline on Gmail, Slack,

and the rest, right where you read it, without context-switching back to Claude.
https://github.com/user-attachments/assets/5fa25044-923e-4c25-95bd-f1bd63fb3d6e
> Prefer a written walkthrough? Try the Claude Desktop walkthrough.
Browser extension (optional)
There's also a browser extension that translates corporate-speak inline on

Gmail, Slack, Linear, Notion, GitHub, Google Docs, and Outlook. It calls

the same translation tools the MCP server exposes, but surfaces them

where you'd actually use them — a floating Translate button plus a

right-click menu — so you don't have to context-switch back to Claude

just to decode "let's circle back on this."
You pick the LLM provider. Five options: Ollama (local, default), LM

Studio (local), OpenRouter (including its auto-router), Anthropic, OpenAI.

The API key, if you need one, stays in chrome.storage.local and never

leaves the device.
Store submission is still pending (the listing prep is done; the developer

accounts and screenshots aren't). Until then, load it manually:
1. Build it: pnpm --filter @neurodock/extension-browser run build

2. Chrome / Edge: go to chrome://extensions, turn Developer mode on,

   click Load unpacked, and pick packages/extension-browser/.output/chrome-mv3/.

3. Firefox: go to about:debugging, click This Firefox → Load

   Temporary Add-on, and pick manifest.json inside

   packages/extension-browser/.output/firefox-mv3/.
Full per-provider setup walkthrough lives in

packages/extension-browser/README.md.
What's inside
NeuroDock is built around three pillars. Each pillar is made of small,

independent packages that you can use one at a time or all together.

mermaid
flowchart TB
subgraph cognitive[Cognitive substrate]
chrono[mcp-chronometric<br/>time + sessions]
cgraph[mcp-cognitive-graph<br/>memory]
frac[mcp-task-fractionator<br/>decomposition]
end
subgraph comms[Communication layer]
trans[mcp-translation<br/>tone + meetings]
ext[extension-browser<br/>Gmail, Slack, ...]
end
subgraph safety[Clinical guardrails]
guard[mcp-guardrail<br/>rumination / hyperfocus / sycophancy]
clin[clinical<br/>heuristic library]
end
skills[skills/<br/>six markdown bundles] --> cognitive
skills --> comms
skills --> safety
cli[cli/<br/>install + manage] --> cognitive
cli --> comms
cli --> safety

<details>

<summary>Prefer the directory tree? Open this.</summary>

neurodock/
├── packages/
│ ├── mcp-chronometric/ Time + session + break management
│ ├── mcp-cognitive-graph/ Persistent memory + entity recall (SQLite)
│ ├── mcp-task-fractionator/ Decompose vague goals into atomic tasks
│ ├── mcp-translation/ Corporate-speak translator (MCP + browser ext)
│ ├── mcp-guardrail/ Rumination / hyperfocus / sycophancy detectors
│ ├── skills/ Six SKILL.md bundles activating on phrases
│ ├── extension-browser/ WXT-built Chrome / Firefox / Edge extension
│ ├── native-host/ Optional native messaging host (extension <-> profile.yaml)
│ ├── cli/ npx neurodock init and friends
│ ├── core/ Shared types, profile schema, plugin spec
│ ├── clinical/ Heuristic library for the guardrail server
│ └── evals/ Eval harness + corpus contribution pipeline
├── docs/ Astro Starlight site (deploys to docs.neurodock.org)
├── plugins/ Drop your own plugins here; auto-discovered
└── profiles/ Curated profile presets

</details>

Status
Public preview shipped. All three substrate pillars (cognitive,

communication, guardrails) are built, on main, and installable from

npm + PyPI. Latest substrate tag: v0.7.3.
MCP servers (PyPI)
- neurodock-mcp-chronometric — 5 tools, 22 tests, mypy --strict.

- neurodock-mcp-cognitive-graph — 4 tools, SQLite + sqlite-vec

  - fastembed; 4-rung resolution cascade (exact → alias → fuzzy → embedding).

    Latest patch ships friendlier record_fact errors so wrong-shape input

    no longer leaks raw Pydantic traces.

- neurodock-mcp-task-fractionator — 2 tools, 32 tests; ISO 8601

  duration spec.

- neurodock-mcp-translation — 4 tools, 29 tests; deterministic

  baseline plus LLM refinement envelope.

- neurodock-mcp-guardrail — all three detectors live: rumination,

  hyperfocus, sycophancy (48 tests, public heuristics).

- neurodock-evals — air-gapped harness, 10 seed corpus examples,

  contribution pipeline.

- neurodock-clinical — reserved name; importable detector library

  (currently a stub).
CLI + browser surface (npm)
- @neurodock/cli — 19 verbs across 7 groups: init, install-all,

  examples, doctor, validate, update, sync, uninstall,

  host install/uninstall, profile show/validate, install-hooks,

  plugin add/remove/list/enable/disable/validate. install-hooks

  wires the proactive-guardrail hook into Claude Code and optionally

  registers the standalone daemon.

- @neurodock/core — profile schema and plugin protocol manifests

  (JSON Schema 2020-12).

- @neurodock/native-host — optional Chrome Native Messaging host

  for the extension ↔ profile sync.

- @neurodock/extension-browser — WXT MV3 build for Chrome / Firefox

  / Edge. Seven sites wired. Five real LLM providers: Ollama, LM Studio,

  Anthropic, OpenAI, OpenRouter. Includes the Phase 2 proactive watchdog

  for hyperfocus / late-night / single-host rumination signals.

  Not yet store-published.
Skills + docs
- Six launch skills — adhd-daily-planner, audhd-context-recovery,

  ocd-decision-finalizer (beta), hyperfocus-formatter, visual-organizer,

  asd-meeting-translator.

- Docs site — builds clean (Astro Starlight), deploys to

  docs.neurodock.org.
Still deferred
- Browser-store submissions — Chrome Web Store, Firefox Add-ons, Edge

  Add-ons developer accounts + screenshots; manual step.
How to actually test it right now
TESTING_LOCAL.md — step-by-step guide to running this against your

Claude Desktop, today, from a clone. Takes about 5 minutes.
Documentation
The docs site lives at docs.neurodock.org.

Source is at docs/src/content/docs/. To preview locally:

bash
pnpm --filter @neurodock/docs run dev