Guide3 min read

Codex + Ornold MCP: Browser Automation Setup Guide

Connect OpenAI Codex CLI or desktop app to Ornold MCP. Configure config.toml and automate antidetect browsers with AI.

Apr 17, 2026

One Prompt — Codex Installs Everything

You don't need to write TOML, find your `npx` path, or remember what flags antidetect browsers need. Paste one prompt with your token. Codex reads the public install guide on GitHub, asks you 2 questions, then writes the right config to `~/.codex/config.toml`.

How it works: Ornold publishes a public agent guide at github.com/ornold-ai/ornold-mcp. Codex fetches `AGENTS.md`, learns the install rules, and asks you only what it needs. No manual TOML, no PATH debugging.

Step 1 — Get Your Token

Sign up at mcp.ornold.com
Open the Tokens page
Click Create token, copy the value (starts with `orn_sk_`)

Step 2 — Paste This Prompt into Codex

Open Codex (`codex` CLI or the desktop app — both read the same `~/.codex/config.toml`) and paste:

Install Ornold MCP for me. I'm new to this, so guide me.

1. Fetch and read the official install guide:
   https://raw.githubusercontent.com/ornold-ai/ornold-mcp/main/AGENTS.md

2. Then ask me these questions in plain language:
   a) Which antidetect browser do I use? Options: Linken Sphere, Dolphin Anty, Vision Browser, Wadex, or none yet (just testing).
   b) Which interaction mode do I want? Briefly explain "vision" (AI sees the page like a human, recommended for antidetect) vs "dom" (AI reads HTML, faster but easier to detect). Recommend vision.
   c) If I picked Dolphin Anty or Vision Browser, ask me for the extra credentials (Dolphin API token / Vision token).
   d) Am I using the Codex desktop app or the CLI? (Desktop apps don't inherit terminal PATH — if desktop, you'll need to find absolute npx path.)

3. After I answer, edit ~/.codex/config.toml (create if missing) using the Codex TOML format from AGENTS.md. Fill in my answers as args.
   - If I use the desktop app, run `which npx` first and use the absolute path in the command field.
   My Ornold token is: YOUR_TOKEN

4. Show me the final TOML before saving so I can confirm.

5. Tell me to restart Codex, then verify by calling browser_status.

If anything fails, explain the error in plain language.

Replace `YOUR_TOKEN` with your token. Codex will fetch the guide, ask you a few questions, edit `config.toml`, and confirm.

What Codex Will Ask You

Question 1: Which antidetect browser?

**Linken Sphere** — desktop app, default port `40080`
**Dolphin Anty** — desktop app port `3001` + your API token
**Vision Browser** — cloud, your token (`vx_...`)
**Wadex** — desktop app, default port `8080`
**None** — install without antidetect

Question 2: Vision or DOM mode?

**Vision (recommended)** — AI clicks via screenshots. Antidetect-safe. Required for flow recording.
**DOM** — CSS selectors. Faster but easier to detect. Use only when stealth doesn't matter.
**Both** — two separate servers (advanced).

Question 3: CLI or desktop app?

Desktop apps don't inherit your terminal PATH, so plain `npx` may not work. Codex will run `which npx` and use the absolute path automatically — but you need to confirm which one you're using.

Unsure on mode? Pick **vision**. Unsure on antidetect? Pick **none** — install plain, add antidetect later.

Step 3 — Verify

Restart Codex and ask:

List my connected browsers using browser_list

If your antidetect is running, you'll see profiles. Done.

Already Know What You Want? Skip the Questions

Edit `~/.codex/config.toml` directly:

Linken Sphere + vision (CLI)

[mcp_servers.ornold-browser]
command = "npx"
args = ["-y", "mcp-ornold-browser", "--token", "YOUR_TOKEN", "--linken-port", "40080", "--mode", "vision"]

Linken Sphere + vision (Codex Desktop App)

Run `which npx` in terminal first, then use the absolute path in `command`:

[mcp_servers.ornold-browser]
command = "/Users/yourname/.nvm/versions/node/v20.0.0/bin/npx"
args = ["-y", "mcp-ornold-browser", "--token", "YOUR_TOKEN", "--linken-port", "40080", "--mode", "vision"]

Dolphin Anty + vision

[mcp_servers.ornold-browser]
command = "npx"
args = ["-y", "mcp-ornold-browser", "--token", "YOUR_TOKEN", "--dolphin-port", "3001", "--dolphin-token", "YOUR_DOLPHIN_API_TOKEN", "--mode", "vision"]

Or use the CLI shortcut

codex mcp add ornold-browser -- npx mcp-ornold-browser --token YOUR_TOKEN --linken-port 40080 --mode vision

Tool Approval Policy (optional)

By default, Codex asks before running each tool. To run browser tools without confirming each time, add to `config.toml`:

approval_policy = "on-request"

Public Resources

**GitHub** — github.com/ornold-ai/ornold-mcp — public agent install guide. Codex reads `AGENTS.md` automatically.
**npm** — mcp-ornold-browser
**Dashboard** — mcp.ornold.com

Troubleshooting

**MCP server not loading** — TOML is whitespace-sensitive. Validate with a TOML linter. Common error: missing `=` or wrong quoting.
**Codex Desktop App: `npx not found`** — apps don't inherit terminal PATH. Run `which npx`, paste the absolute path into `command`.
**Codex Desktop App: config not detected** — must be at `~/.codex/config.toml`, not in a project folder.
**Token invalid** — re-copy from mcp.ornold.com.
**Cannot connect to browser** — antidetect must be running, port must match.

What's Next?

Claude Code + Ornold MCP if you also use Claude Code
Parallel browser automation — run 10+ sessions at once
CAPTCHA solving guide — reCAPTCHA, hCaptcha, Turnstile
Vision AI vs CSS selectors — why coordinate clicks beat DOM scraping

Explainer