---
title: "Codex integration with Bolta"
description: "Connect Codex to Bolta with codex mcp add and a browser sign-in. Turn release notes into LinkedIn and X drafts, then approve them yourself. Setup steps and honest limits."
canonical_url: "https://bolta.ai/integrations/codex"
markdown_url: "https://bolta.ai/integrations/codex.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Codex integration with Bolta

Source: https://bolta.ai/integrations/codex
Last updated: 2026-11-21

Connect Codex to Bolta with codex mcp add and a browser sign-in. Turn release notes into LinkedIn and X drafts, then approve them yourself. Setup steps and honest limits.

## Summary

Turn what you ship into social drafts from Codex, with your yes before anything posts

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Turn a release note or CHANGELOG.md entry into a LinkedIn and an X draft the day you ship
- Read the last week of git log and draft a build-in-public thread for review
- Keep one Codex session coding while a second one drafts the launch posts in parallel
- Have a script call codex exec to save a weekly draft batch for your team to review
- Check which recent posts did best before Codex suggests what to write next
- Set up a weekly routine from the terminal that drafts posts and waits for your approval

## Limitations and boundaries

- Confirmed: Codex's official docs describe adding a remote MCP server by URL, with a browser sign-in through codex mcp login. Bolta's connection uses exactly that standard route.
- Confirmed: Codex finds skills in folders that contain a SKILL.md file, so the optional Bolta skill is a normal skill for it.
- Not confirmed: nobody at Bolta has run a full draft, review and schedule cycle through Codex yet. Treat the first run as a test and check each result.
- Not confirmed: Bolta's skills README lists npx skills add for Codex CLI, marked not tested. We have not run that install for Codex ourselves.
- Not confirmed: a Bearer API key through bearer\_token\_env\_var, and any Codex-specific plugin entry for Bolta. Sign-in is the path to use.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Check what you need

You need a Bolta account with at least one brand, and Codex installed. Run codex in a terminal to confirm it starts. Codex's MCP docs say the CLI, the IDE extension and the desktop app share this configuration, so the same entry should apply if you use those instead.

## Add Bolta to Codex

Run codex mcp add bolta --url https://mcp.bolta.ai/mcp. Or open ~/.codex/config.toml, keep what is already there, and add \[mcp\_servers.bolta\] on one line and url = "https://mcp.bolta.ai/mcp" on the next, then save.

## Sign in to Bolta

Run codex mcp login bolta. A Bolta page opens in your browser. Sign in and tick the brands this connection may reach. One connection is one organization, and it can only reach the brands you tick.

## On a machine with no browser

Run codex mcp login bolta --no-browser. Codex prints a link. Open it on any computer, sign in, then paste the full address you land on back into the terminal.

## Check that Codex sees Bolta

Run codex mcp list and look for bolta. Or start codex and type /mcp to see the active servers.

## Add the Bolta skill

Optional, and it helps Codex follow your voice, your review list and the approval rule. Run npx skills add boltaai/bolta-skills --skill bolta and choose Codex if it asks. Codex looks for skills in .agents/skills inside a repo or ~/.agents/skills for your user.

## Start a new session

Close any open Codex session and start a new codex one so it picks up the server and the skill.

## Test with a read-only question

Ask: What is waiting for my yes in Bolta? Allow the tool call if Codex asks. This reads your review list and changes nothing.

## Try a first draft

Ask: Write three LinkedIn drafts from CHANGELOG.md and save them as drafts. Do not schedule anything. Then approve the exact text in Bolta or in chat. If a Codex command is not found, check Codex's own MCP docs, since command names can change between versions.

## Turn a changelog or git log into drafts

Codex already has your repo open, which makes it a good starting point for launch posts. Point it at the file or the commit range and ask for drafts. 1. Name the source: Say which file or range to read, for example CHANGELOG.md, the release notes for v2.0, or the last week of git log. 2. Say where it goes: Name the network and the brand if you ticked more than one, for example a LinkedIn post for the Acme brand. 3. Ask for a draft, not a post: Add save it as a draft, do not schedule. Codex saves it in Bolta and shows you the text. 4. Approve the exact text: Edit it in chat or in Bolta. Only when you say yes does it get a time or go out.

## Headless runs with codex exec

Codex has a non-interactive mode, codex exec, for scripts and scheduled jobs. It should be able to call Bolta the way a normal session does once the server is added and signed in on that machine, but we have not run that. Use it to draft or to send work to team review only. Bolta's house rule for unattended runs is no auto-publishing. Sign in once with codex mcp login bolta on the machine that runs the job. Use --no-browser on a server. Codex's docs say exec runs in a read-only sandbox by default and expects a Git repository, and that project-defined MCP servers load only for trusted projects. Keep Bolta in your user ~/.codex/config.toml and read the non-interactive page before you wire it into CI.

## The skill, and which brand Codex uses

The MCP connection gives Codex the tools. The skill and your brand choice shape how it uses them. Question: Do I need the skill?; Answer: No. Codex can use Bolta without it. The skill teaches it your voice, your review list and the approval rule. | Question: Where does Codex look for skills?; Answer: .agents/skills in a repo, or ~/.agents/skills for your user. You can call one with $ or from /skills. | Question: Which brands can it reach?; Answer: Only the brands you ticked at sign-in. One connection is one organization. | Question: How do I use another brand?; Answer: Name the brand in your request. To add one later, run codex mcp login bolta again and tick it.

## One session codes, another drafts

Codex can run more than one session, so the launch post does not have to wait for the feature to finish. Keep the coding session on the branch. Open a second codex session in the same repo just for the announcement. In the second session, ask it to read the diff or CHANGELOG.md and save drafts. It does not need to touch your code. Both sessions use the Bolta connection you already signed in. Each one needs to be started after you added the server. If you would rather not mix the two, keep a separate folder that holds only the Bolta skill and your notes on tone.

## User config or project config

Codex reads MCP servers from a user file and, in a trusted project, from the project too. Which one you pick decides who gets Bolta. Codex's docs say project-defined MCP servers load only for trusted projects. The entry on this page holds only the Bolta server address. Each person signs in themselves with codex mcp login bolta. File: ~/.codex/config.toml; Who sees it: You, in every project; Good for: A founder with one Bolta organization who drafts from any repo | File: .codex/config.toml in a trusted project; Who sees it: Anyone who opens that project and trusts it; Good for: A team that wants the same brand on a shared repo

## What not to hand Codex to post about

A repo holds more than release notes. Codex can read a lot, so tell it what is safe to talk about. Name the file or range to read. Leave out private branches, security fixes not yet shipped and customer names in commit messages. Ask for the customer-facing change, not the internal reason. Commit messages are written for developers. Read every draft before you say yes. Codex can summarise a commit wrongly, and Bolta checks the post against your brand rules but not against your code.

## What is tested and what is not

The connection is the standard Codex route for a remote MCP server, and the commands on this page come from Codex's own documentation. What we have not done is run a complete draft, review and schedule cycle through Codex. Claude Code is the most tested coding-agent path for Bolta. If you want the proven route today, use that. If you prefer Codex, expect to check each step the first time.

## Is Codex the same as ChatGPT, and do I use the same Bolta setup?

No. Codex is OpenAI's coding agent for the terminal, IDE and desktop app. ChatGPT is the chat app with its own Bolta page. Use the setup on this page for Codex.

## Do I need an API key to connect Codex to Bolta?

No. The recommended route is a browser sign-in: run codex mcp login bolta and tick the brands to share. Codex can also read a token from an environment variable, but we have not tested that against Bolta, so use sign-in.

## Can Codex publish to my social accounts without my approval?

No. A post only gets a time or goes out after you say yes to its exact text. Codex should show you the text first, and if it tries to skip that, Bolta refuses or keeps the post in review. Your role and Safe Mode still apply.

## How do I connect Codex when I am on a server with no browser?

Run codex mcp login bolta --no-browser. Codex prints a link, you open it on any computer and sign in, then paste the full address you land on back into the terminal.

## Can I run Bolta from codex exec in a script or CI?

It should work once the server is added and signed in on that machine, but we have not tested it. Keep unattended runs to saving drafts or sending to team review. Do not set them up to publish on their own.

## Which brands can Codex reach, and how do I add another one?

Only the brands you ticked at sign-in, since one connection is one organization. With more than one ticked, say which brand a draft is for, for example the side project and not the main one. To add another, run codex mcp login bolta again and tick it.

## Do I need the Bolta skill if the MCP connection already works?

No, the connection is enough to start. The skill helps Codex use your voice, your review list and the approval rule more consistently. Install it with npx skills add boltaai/bolta-skills --skill bolta and start a new session.

## Does it cost extra to use Codex with Bolta?

We have not confirmed Codex's pricing or which plans include it, so check OpenAI's pages. Plan limits and credit use for what you draft are shown in Bolta.

## Is this tested end to end?

Not yet. The connection follows Codex's documented route, but no one has run a full draft, review and schedule cycle through Codex. Claude Code is the most tested path.

## What can Codex not do through Bolta?

Anything your Bolta role does not allow. Viewers cannot approve or publish, and Safe Mode and client sign-off still apply on top. A network you have not connected is out of reach too.

## Can Codex in the IDE or desktop app use Bolta, or only the terminal?

Codex's MCP docs say the ChatGPT desktop app, Codex CLI and IDE extension share this configuration, so the entry you add once should show up in each. We have only described the terminal commands here, so check /mcp in the one you use.

## Why did Codex say it cannot schedule my post?

Usually because nobody has said yes to the exact text yet, or your role in Bolta does not allow it. Bolta refuses on purpose in those cases. Approve the draft, or ask an owner or admin if it is a role limit.

## codex mcp list does not show bolta

The entry did not save. Re-run codex mcp add bolta --url https://mcp.bolta.ai/mcp, or check that \[mcp\_servers.bolta\] and the url line are in ~/.codex/config.toml, then start a new session.

## Codex says the command is not found

Command names can change between Codex versions. Update Codex, or check the MCP page in Codex's official docs for the current wording.

## The sign-in page does not open

You may be on a machine with no browser. Run codex mcp login bolta --no-browser, open the printed link elsewhere, and paste the full address you land on back into the terminal.

## Codex cannot see my new brand

A connection only reaches the brands you ticked at sign-in. Run codex mcp login bolta again and tick the new one.

## Codex does not use the Bolta skill

Start a new codex session after installing it. Check the skill folder is in .agents/skills (in a repo) or ~/.agents/skills, and call it with $ or pick it from /skills.

## It saved a draft but nothing was posted

That is the design. A saved draft waits for your yes. Approve the exact text in Bolta or in chat, and only then will it get a time or go out.

## Codex is not ChatGPT

Codex is OpenAI's coding agent for the terminal, IDE and desktop app, and you add Bolta in its config. ChatGPT is the chat app, and it has its own Bolta setup. Use the page that matches the tool you actually open.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/chatgpt](https://bolta.ai/integrations/chatgpt)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Related page: /integrations/gemini](https://bolta.ai/integrations/gemini)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Codex official website](https://developers.openai.com/codex)
