OpenClaw local setup (stdio)

Neotoma with OpenClaw · Local setup where Neotoma runs on the same machine via stdio.

Need OpenClaw on another machine or HTTP to a tunneled MCP URL? See OpenClaw remote setup (HTTP).

Setup

Paste this prompt into an agent tool (for example Claude Code, Codex, or Cursor) to install Neotoma. The agent handles npm install, initialization, and MCP configuration.

Code snippet

Copy the exact snippet shown below.

Read https://neotoma.io/install and carry me through the install-first Neotoma flow.

Use only `neotoma` commands (especially `neotoma doctor --json` and `neotoma setup --tool <my_tool> --yes`). Do NOT run `python3 -c`, `grep -r`, `ls`, `cat`, `jq`, `find`, `which`, `node -e`, or arbitrary `npm run <script>`. Everything you need to introspect state is in `neotoma doctor --json`. If you hit a permission prompt for anything other than `neotoma *` or `npm install -g neotoma`, stop and ask me to widen the allowlist instead of improvising an alternative command.

Install, activate it with my data, and configure my current tool for robust ongoing use.

After installation, add Neotoma to your OpenClaw configuration file and restart OpenClaw to pick up the new MCP server.

Back to Neotoma with OpenClaw · Install guide · MCP reference