Connect Codex

Run this in your terminal:

codex mcp add birta -- npx -y @birta/cli mcp

If your version of Codex doesn't accept a command there, add the server to its config file instead. Open ~/.codex/config.toml and add:

[mcp_servers.birta]
command = "npx"
args = ["-y", "@birta/cli", "mcp"]

You need Node.js 20 or newer. npx -y @birta/cli mcp fetches the package on first use, so there is nothing to install or update by hand.

There is no sign-in step first. Ask Codex to make you a site or to list your Birta projects. The first request comes back with a link (and a short code) instead of a result — open the link, sign in with the one-time code sent to your email, and confirm access.

Then ask Codex again — the request that was refused runs once access is confirmed. This installation stays authorized afterwards: there is no key to copy and nothing to paste back.

Prefer to get it out of the way first? This command shows the same link and waits for your confirmation:

npx -y @birta/cli login

You never list files for Codex. It names two folders on your computer — your project and, if the site is built, the built site — and hands them over as they are. They go into your site's draft: nothing on your live site changes, and visitors keep seeing the version you published last.

Codex then gives you the draft's own address. Open it, and mark what you want changed straight on the page. Tell Codex you have left remarks, it makes the changes on your computer and hands the folders over again — the draft keeps the same address, so you just refresh the page you already have open.

Go round as many times as you like. When it looks right, say so — Codex publishes the draft, and only then does your site address start serving it. If a check fails, nothing is published: you are told everything that is in the way at once, and the draft stays as it was.

Ask Codex to list your Birta projects. If it can see them, the connection is ready and you can ask it to publish or update a site.