<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/zh/neotoma-with-codex-connect-local-stdio
  Generated: 2026-04-28T13:35:39.312Z
-->
# Codex local setup (stdio)

[Neotoma with Codex](/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)](/neotoma-with-codex-connect-remote-http-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 `neotoma` commands for status and setup. If Neotoma is already installed, start with `neotoma doctor --json`; otherwise install it and run `neotoma setup --tool <my_tool> --yes`.

Avoid ad-hoc shell introspection or arbitrary repo scripts. Then activate Neotoma 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.

[Back to Neotoma with Codex](/neotoma-with-codex) · [Install guide](/install) · [MCP reference](/mcp)