Integrations
Codex
Add Ulika to OpenAI's Codex with one command. It edits only its own block in config.toml, installs an optional skill, backs up first, and uninstalls cleanly.
Last updated
Codex is OpenAI's terminal coding agent. One command adds the Ulika MCP server, and a small skill that teaches Codex how to use it, to your Codex setup. After a restart you can tell Codex Connect my site to Ulika. In your project's settings, under Integrations, Codex appears with the description "OpenAI's terminal coding agent. One command adds Ulika to Codex."
Install#
Run this once in your terminal:
npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz codex installIf the CLI is installed globally, it is ulika codex install. In the Integrations list, Set up on Codex shows the same command with a Copy the Codex setup command button, the line "Run this once in your terminal, then restart Codex." and, below it, "Or tell Codex: “Connect my site to Ulika”". The Codex row never shows Connected: Codex runs on your computer, and Ulika cannot see whether the command was run.
Then restart Codex and ask it: Connect my site to Ulika. The CLI prints the same reminder when it finishes:
✓ Added Ulika to Codex (/Users/you/.codex/config.toml)
Runs npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz mcp
Restart Codex, then ask it: Connect my site to UlikaThe first time Codex starts the server, npx may need to download the CLI, which is why the entry gives it a 60-second start-up timeout (Codex's default is 10).
What it changes#
config.toml#
Codex reads MCP servers from config.toml in its home folder: ~/.codex/config.toml, or $CODEX_HOME/config.toml when the CODEX_HOME environment variable is set. The installer adds one block, and only that block:
# Managed by `ulika codex install`. Remove with `ulika codex uninstall`.
[mcp_servers.ulika]
command = "npx"
args = ["-y", "https://ulika.co/cli/ulika-cli-0.7.1.tgz", "mcp"]
startup_timeout_sec = 60How it treats your file:
Text edit, nothing else touched. Your comments, ordering, line endings and every other server survive byte for byte. If the block is already there it updates only the three keys Ulika owns (
command,args,startup_timeout_sec). Any other key you added to theulikablock, and sub-tables such as[mcp_servers.ulika.env], are left alone.Idempotent. Installing the same version again changes nothing and makes no backup. After a new CLI version, run install again to move the pinned address forward; it reports Updated Ulika in.
Backup first. Before changing an existing file it saves a timestamped copy next to it, named like
config.toml.ulika-backup-2026-10-10T12-00-00-000Z. The three most recent backups are kept.Atomic and safe. The new file is written to a temporary name and renamed into place. A symlinked
config.toml(for example one managed by a dotfiles tool) stays a symlink. A file that does not exist yet is created readable only by you.Refuses when unsure. If the file is written in a way it cannot edit safely, it changes nothing and says why (see Problems).
The skill#
Unless you pass --no-skill, it also writes ~/.agents/skills/ulika/SKILL.md, which is where Codex looks for user-level skills. The skill is named ulika and tells Codex how to use Ulika. In short, it tells the agent to:
Ask only for the site's address, run
ulika connect https://their-site.com(or callconnect_sites), and never ask you for local files, a repository, a project name or a token.Treat your approval as the consent, because the approval page says what happens, and give you the editor link when the site is live.
Use the single Activate link only when a site really needs you, never the GitHub pull request.
Use
connection_statusandscan_siteto check things, and the code tools only when you ask for code changes, telling you the change is a local draft.Never publish or deploy for you.
The file carries a marker comment saying it is managed by ulika codex install. If a SKILL.md already exists there without that marker, it is yours and is left alone; the installer reports that it left that file alone because Ulika does not manage it.
Options#
| Option | Effect |
|---|---|
--no-skill | Only edit config.toml; do not install the skill. |
--dry-run | Show what would change; write nothing. The output starts with "Would have:". |
--force | Edit or remove a ulika entry that Ulika did not create. A backup is saved first, and your other settings in that entry are kept. |
--yes | Needed only when installing from an Ulika address other than the official one. |
--server <origin> | Install from a different Ulika instance. Must be an https origin with no path, query, fragment or credentials (http is accepted only for localhost). |
--json | One JSON object with ok, status (added, updated, unchanged or dry-run), configPath, action, backupPath, skillPath, skillAction, skillError, server, tarball and warning. |
Using Ulika from Codex#
Once installed, Codex has Ulika's MCP tools. The usual conversation:
You: "Connect my site to Ulika." Codex asks only for your site's address if you did not give it.
Codex shows you one approval link and code. You approve once in the browser. See Connect with an AI agent.
Codex follows the batch and reports the live sites with their editor links, and anything that needs you.
Uninstall#
npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz codex uninstallThis removes the [mcp_servers.ulika] block, every [mcp_servers.ulika.*] sub-table and the marker line, after saving a backup. If you added settings of your own inside the block, it tells you: "That included settings you added: ...". It also removes the skill, but only if it still carries the managed marker. If Ulika was never set up it says "Ulika was not set up in <path>. Nothing to remove." A ulika entry that Ulika did not create is not removed unless you pass --force.
Problems#
| Message | Cause and fix |
|---|---|
"config.toml already defines ulika in a way Ulika cannot edit safely" (an inline ulika = { ... }, a dotted ulika.* key, or mcp_servers as an inline table) | Editing it automatically could create a duplicate key that stops Codex from starting. Edit or remove that entry yourself, then run the command again. |
| "config.toml has a [mcp_servers.ulika] table that Ulika did not create." | The block has no Ulika marker, so it is treated as yours. Run again with --force to update only command, args and startup_timeout_sec. A backup is saved first. |
| "config.toml could not be read safely, so nothing was changed" | A syntax the installer will not guess about (for example [[mcp_servers.ulika]], a duplicate [mcp_servers.ulika], an unterminated string). Fix that spot or edit the file by hand. |
| "Could not read config.toml" | The file exists but cannot be read. Check its permissions. |
| "The Codex config is done, but the skill could not be written" | The server entry was installed, but writing ~/.agents/skills/ulika/SKILL.md failed. Fix the folder permissions and run install again, or skip the skill with --no-skill. |
| "<origin> is not the official Ulika server" | You passed a non-official --server. Re-run with --yes if you trust it. |
| "Usage: ulika codex install or ulika codex uninstall" | Exit code 2. The action was missing or misspelled. |
For the underlying exit codes see CLI errors and exit codes. Install and uninstall exit 0 on success and 1 on a failure to update the config; usage and server-address mistakes exit 2.
Was this page helpful?