Codex
Use a Codex session with terminal and file-editing access to prepare Ark. Ordinary chat without those permissions cannot perform local installation.
Recommended Setup
Section titled “Recommended Setup”- Send the guided setup request, naming Codex and your actual execution host.
- Approve setup changes and enter keys privately when prompted.
- Review
ark-seedin/mcpor your edition’s MCP settings.
The agent resolves paths and uses the installed client’s registration mechanism. Once configured, Codex starts Ark automatically.
Manual configuration and scope options
Choose the Scope
Section titled “Choose the Scope”- User/global:
${CODEX_HOME}/config.toml, normally~/.codex/config.toml. - Project:
<project>/.codex/config.toml, loaded only for trusted projects.
codex mcp add writes user/global configuration in the repository’s documented
workflow; it is not the project-only registration command. Do not change
project trust automatically or delete a competing same-name entry. Clients
sharing the same Codex configuration do not need duplicate registrations.
Complete the shared prerequisites. Registration scope does not change where Ark’s checkout or private credentials live.
Global CLI Registration
Section titled “Global CLI Registration”Check codex mcp add --help. In a Bash/POSIX shell:
UV="/absolute/path/to/uv"CHECKOUT="/absolute/path/to/ark-mcp"ENV_FILE="/absolute/path/to/private/ark-mcp/.env"
codex mcp add ark-seed \ --env "ARK_MCP_ENV_FILE=$ENV_FILE" \ --env MCP_TRANSPORT=stdio \ --env MCP_AUTH_MODE=local \ -- "$UV" --directory "$CHECKOUT" run --locked --no-sync python -m ark_mcpAll variable values are non-secret absolute paths. Use host-native quoting on Windows rather than pasting Bash continuations into PowerShell.
TOML Configuration
Section titled “TOML Configuration”For project-only setup, merge this into the trusted project’s
.codex/config.toml. The same table can instead be placed in the user/global
file; choose one intended scope:
[mcp_servers.ark-seed]command = "/absolute/path/to/uv"args = [ "--directory", "/absolute/path/to/ark-mcp", "run", "--locked", "--no-sync", "python", "-m", "ark_mcp",]
[mcp_servers.ark-seed.env]ARK_MCP_ENV_FILE = "/absolute/path/to/private/ark-mcp/.env"MCP_TRANSPORT = "stdio"MCP_AUTH_MODE = "local"Preserve unrelated tables and comments. Never put provider keys in env.
Project configuration with machine-specific absolute paths is not a portable
team setup and should not be committed automatically.
Verify
Section titled “Verify”Run the discovery-only check and confirm the tools you need appear. Continue with Your First Tool Call. Finish active jobs before reconnecting; a new local process does not inherit the previous process’s in-memory queue.
See Integrations, Claude Code, Getting Started, Tools, and Configuration.
Official Sources
Section titled “Official Sources”Sources consulted for MCP setup on 2026-11-10. CLI/IDE/app support must still be checked in the actual target client.