Codex local setup (stdio)
Neotoma with Codex · Local setup where Neotoma is configured in Codex on the same machine.
Need a remote MCP URL for sandboxes (HTTP with OAuth)? See Codex remote setup (HTTP with OAuth).
Setup
Paste this prompt into Codex. 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.The agent writes to .codex/config.toml (project-level) or ~/.codex/config.toml (user-level). Codex discovers the MCP server from your config automatically.