Doable for Codex
Codex's CLI loads MCP tools from your project's .mcp.json. Drop Doable in via `npx doable-cli setup`, then say "deploy this" or run /deploy, Codex calls Doable's MCP tools to bundle, build, and ship your project.
1. Install (one-time, in your project directory)
npx -y doable-cli setup --codex
2. Deploy (in Codex)
Type /deploy or use natural language:
Doable's MCP tool descriptions lead with these trigger phrases so Codex routes intent to /deploy without command-style invocation.
Codex and Claude Code share the project-level MCP config format. One setup command configures both; switching between editors mid-session keeps Doable available either way.
Codex runs in a terminal, Doable's structured tool responses parse cleanly into Codex's reasoning, and the deploy URL pops out as a JSON field your shell scripts can grab.
doable.login opens a browser device-code flow from inside Codex. After you approve once, every project on this machine deploys without re-auth.
No .codex.toml tweaks, no environment variables, no flags. Codex sees the Doable MCP tools the same way it sees its built-in tools.
The local CLI loads MCP tools from .mcp.json, Doable works there. The cloud-hosted Codex variant has its own MCP loading; if it loads project-level .mcp.json, Doable works there too. We test against the local CLI primarily.
No, different tools. Doable's MCP works with Codex (the OpenAI Agentic CLI). For Copilot you'd use the Doable CLI directly via `doable deploy`.
Codex MCP config is project-level by design. Run `npx doable-cli setup` once per project, or once in a parent directory if your projects share a common root.
No credit card. Or try with any GitHub URL without signing up.