Installation
The one-liner
Section titled “The one-liner”npx --yes @neurodock/cli@latest install-all30-second TL;DR
Section titled “30-second TL;DR”That one command installs the five NeuroDock MCP servers from PyPI (via uvx), detects which MCP-aware clients you have (Claude Desktop, Claude Code, Cursor), and writes the server registration block into each of their config files. Then you restart your client and the tools appear.
This is the developer preview (@neurodock/cli v0.5.0). The substrate is at v0.2.1 and all five MCP servers are live on PyPI.
Per-client configuration
Section titled “Per-client configuration”The installer writes these snippets for you. They are shown here so you can verify what landed, or hand-edit if you skipped install-all.
Every MCP-aware client uses the same mcpServers block; the only thing that varies is where the config file lives.
Claude Desktop reads claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
After install-all, you should see:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}Restart Claude Desktop after install (full quit — see callout above).
Claude Code reads MCP server configuration from .claude/settings.json (project-local) or the global equivalent. install-all will offer to register the servers globally; you can decline and add per-project later.
The registration block is the same shape:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}Cursor reads MCP configuration from ~/.cursor/mcp.json (global) or .cursor/mcp.json in any project folder. install-all writes the global file:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}Restart Cursor after install.
Perplexity’s desktop app (Comet) is gaining MCP support; check Perplexity’s MCP docs for the current configuration path. When supported, the block shape is the standard MCP form:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}install-all does not auto-detect Perplexity yet. Paste the block manually into whatever location Perplexity documents.
OpenClaw is an open-source MCP-aware client. NeuroDock’s substrate is vendor-neutral — any client that speaks the MCP stdio protocol works. Consult OpenClaw’s documentation for the exact config file path and paste the registration block:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}install-all does not auto-detect OpenClaw yet — contributions welcome at github.com/tlennon-ie/neurodock.
Hermes Agent supports the standard MCP stdio protocol. Consult Hermes’s documentation for its config file location, then paste:
{ "mcpServers": { "neurodock-chronometric": { "command": "uvx", "args": ["neurodock-mcp-chronometric"] }, "neurodock-cognitive-graph": { "command": "uvx", "args": ["neurodock-mcp-cognitive-graph"] }, "neurodock-task-fractionator": { "command": "uvx", "args": ["neurodock-mcp-task-fractionator"] }, "neurodock-translation": { "command": "uvx", "args": ["neurodock-mcp-translation"] }, "neurodock-guardrail": { "command": "uvx", "args": ["neurodock-mcp-guardrail"] } }}install-all does not auto-detect Hermes yet — contributions welcome.
Verify the install
Section titled “Verify the install”neurodock doctordoctor checks: profile is readable and schema-valid, all five MCP servers start, embedding backend is reachable. Failures are explained with the next action to take.
Prerequisites
Section titled “Prerequisites”- Node.js 22 or newer. Check with
node --version. - Python 3.11 or newer. Check with
python --version. uvfor Python workspace management. Install from astral.sh/uv.uvxis the per-tool launcher that ships withuv.- An MCP-aware client. Claude Desktop, Claude Code, or Cursor. The substrate is vendor-neutral; any client that speaks MCP works.
Optional but recommended for local-first embeddings:
- Ollama with the
nomic-embed-text-v1.5model pulled. The cognitive graph falls back tofastembed-pyif Ollama is unavailable.
Manual install (from a clone)
If you’d rather build from source, or you want to hack on the substrate:
git clone https://github.com/tlennon-ie/neurodock.gitcd neurodockpnpm installuv syncBoth workspaces install in parallel — Node packages via pnpm, Python packages via uv.
Then run the installer from the clone:
npx neurodock initThe installer:
- Detects your installed MCP clients.
- Writes a default profile to
~/.neurodock/profile.yaml(you will be prompted fordisplay_nameandneurotypes). - Registers the five substrate MCP servers with each detected client.
- Prints a summary of what was changed.
Preview before writing
Section titled “Preview before writing”npx neurodock init --dry-run--dry-run prints every file that would be created or modified without touching anything. Useful for review, useful for CI.
What’s next
Section titled “What’s next”- Run your first skill —
/morning-briefin Claude Desktop, end-to-end. - Edit your profile — turn on or off skills, set thresholds, change consent gates.
- Read the substrate concept page — what those five MCP servers actually do.