Codex + Blogizi
Codex writes the markdown post and publishes it with the Blogizi CLI or MCP server. Keep one session coding and let another write about what you shipped. Drafts by default, live when you approve.
Codex connects to Blogizi two ways: install the Blogizi skill (which drives the Blogizi CLI), or add the Blogizi MCP server with codex mcp add. Both take a minute, and you can use both.
Two commands add the Blogizi skill and CLI. Sign in once and Codex can reach every blog on your account.
npx skills add bytemindlab/blogizi-agent
npm install -g blogizi
blogizi login # approve in your browser
blogizi use your-project # only if you have several blogsThe CLI auto-uploads relative images in your markdown. In CI, set BLOGIZI_API_KEY instead of blogizi login. Restart Codex after installing the skill.
Once connected, Codex calls Blogizi tools. Posts land as drafts on your domain and go live only when you approve.
Also try
Sign in once. From then on Codex can draft to any of your blogs from the terminal, on a subdomain or under yourapp.com/blog.
Pick the skill when you want the Blogizi CLI in your repo and in scripts. Pick MCP for sign-in with no CLI and Search Console in the session. Both reach the same blogs.
| Capability | Blogizi skill (CLI) | Blogizi MCP server |
|---|---|---|
| Setup | npx skills add bytemindlab/blogizi-agent, then npm install -g blogizi | codex mcp add blogizi --url https://blogizi.com/api/mcp |
| Authentication | blogizi login (browser) or BLOGIZI_API_KEY in CI | codex mcp login blogizi (browser, no API key) |
| Where Codex loads it | The installed Blogizi skill, which drives the CLI | ~/.codex/config.toml under [mcp_servers.blogizi] |
| Images | Relative paths in your markdown upload on draft | upload_post_image tool |
| Search Console | Not in the CLI | get_search_performance (Pro) |
| Best for | Posts as files in your repo; scripts and CI | No CLI install; the growth loop in-session |
You can install both; Codex uses whichever fits the request.
Add the Blogizi MCP server to Codex and it can read Search Console, find page-2 queries and write a post for each, grounded in your codebase.
Codex quotes the code it can see, so examples match what you actually shipped.
Posts are .md files in your repo before they're drafts. Diff them like code.
One Codex session builds, another writes the post about it.
Relative image paths are uploaded when the post is drafted.
blogizi update re-pushes edits to the same post. No duplicate URLs.
Find the queries you're on page 2 for and write a post for each (Pro).
Codex finds your blog, reads the code, writes the post and drafts it through Blogizi. You describe what you want in plain language; here's how a typical session goes.
Codex lists the blogs on your Blogizi account and picks the one you name.
> Which Blogizi blogs do I have? Codex: You have 2 blogs: - blog.yourapp.com (Acme) - yourapp.com/blog (Side project) Ran blogizi use acme.
Describe the post and point at the code. Codex writes the markdown with real samples and drafts it.
> Write a post about the webhook retry logic in src/webhooks, target "webhook retries", and draft it. Codex: Wrote posts/webhook-retries.md (1,240 words, 3 code samples). blogizi draft posts/webhook-retries.md ✓
Ask for edits, re-push to the same URL, and publish when it's right. With MCP, check Search Console too (Pro).
> Shorten the intro, update the draft, then publish it. Codex: Updated posts/webhook-retries.md. blogizi update ✓ (same slug) blogizi publish webhook-retries ✓ Live at blog.yourapp.com/webhook-retries
Yes. Ask once and Codex writes each post with its own code samples and images, and drafts them all for review. For example:
> Write release notes for v2.4 from the merged PRs, a tutorial for the new webhooks API using code from src/webhooks, and a benchmarks post from bench/results.json with a table. Draft all three on blog.yourapp.com. Codex: Done. Drafts saved: - "What's new in v2.4" (12 PRs, 3 screenshots) - "Webhooks in 10 minutes" (4 code samples) - "v2.4 benchmarks: 38% faster cold starts" Review them in Blogizi; say "publish" for any of them.
Codex is OpenAI's coding agent. It runs as the Codex CLI in your terminal, as an IDE extension, and in the cloud. It reads your codebase, runs commands in a sandbox with approval rules you set, loads skills and calls MCP servers, which is how it writes and publishes posts with Blogizi.
Codex runs in your terminal or IDE. Tell it what to write and it handles the Blogizi steps.
Commands run in a sandbox with approval rules you set, so publishing only happens when you allow it.
Run several Codex sessions at once: write a post in one terminal while you keep building in another.
No. Both are made by OpenAI, but ChatGPT is the chat assistant and Codex is the coding agent. They reach Blogizi through different doors.
| Codex | ChatGPT | Claude Code | |
|---|---|---|---|
| Made by | OpenAI | OpenAI | Anthropic |
| Where it runs | Terminal, IDE extension, cloud | chatgpt.com and its apps | Terminal, VS Code, JetBrains |
| How Blogizi connects | Blogizi skill + CLI, or MCP server | Custom MCP connector | Blogizi plugin, skill + CLI, or MCP |
| Reads your repo | Yes | No | Yes |
| Headless automation | codex exec in scripts, CI or cron | Ask each time | claude -p in scripts |
| Best for | Release posts and tutorials from code | Writing by conversation | Release posts and tutorials from code |
Dedicated guides: ChatGPT + Blogizi, and Claude Code + Blogizi.
Codex finds Blogizi two ways. The Blogizi skill is installed with npx skills add and teaches Codex the Blogizi CLI. The Blogizi MCP server is added with codex mcp add and stored in ~/.codex/config.toml. Either way, Codex learns the tools and chains them for you.
# Install the Blogizi skill + CLInpx skills add bytemindlab/blogizi-agentnpm install -g blogiziblogizi login # Or add the Blogizi MCP server insteadcodex mcp add blogizi --url https://blogizi.com/api/mcpcodex mcp login blogizi # Then ask, interactively or headless$ codex "list my Blogizi blogs"$ codex exec "draft a post about the last release"
Use codex exec to run a prompt non-interactively from a script, CI job or cron entry. Codex loads the Blogizi skill or MCP tools, reads the repo, and drafts the post; you review the draft in Blogizi.
Interactive, or headless with codex exec
Tell Codex what to write from your terminal. The same prompt works with codex exec for unattended runs; keep a human reviewing the drafts.
# Interactive$ codex "Write a post about the JWT refactor and draft it on Blogizi" # Headless, e.g. in CI after a release tag$ codex exec "Summarize the changes since the last tag into a release post and draft it on Blogizi with docs/cover.png as the cover" Codex: Done. 1. Read 14 commits since v2.3.0 2. Wrote posts/release-v2-4.md 3. blogizi draft posts/release-v2-4.md ✓
Keep coding while Codex writes
Run more than one Codex session at once. One terminal builds the next feature, another writes the post about the last one; each runs on its own.
# Terminal 1 — write the post$ codex "Write a post about the webhooks retry logic in src/webhooks and draft it" # Terminal 2 — check what to write next (MCP, Pro)$ codex "Which queries am I on page 2 for? Suggest three posts" # Terminal 3 — keep coding$ codex "Add rate limiting to the public API"
# Accountblogizi login approve in the browserblogizi use <project> pick a blog # Postsblogizi draft <file.md> save a draft, upload imagesblogizi update <file.md> same slug, same URLblogizi publish <slug> go live, when you say so # In CIBLOGIZI_API_KEY=... instead of blogizi login
Blogizi works with any agent that can run commands or call MCP tools. That includes Anthropic's Claude Code, Cursor, and anything else that can run the Blogizi CLI or connect to the Blogizi MCP server.
by Anthropic
Install the Blogizi plugin from the Claude marketplace and Claude Code writes posts from your repo the same way. Same blogs, same drafts, same dashboard.
> Write a post about the rate-limiting middleware we just merged and draft it. Claude Code: wrote posts/express-rate-limiting.md - blogizi draft posts/express-rate-limiting.md ✓
Anything you'd brief a writer on. Name the topic, the keyword and the tone; Codex handles the rest through Blogizi.
From your diff
Changelog
MCP, Pro
Data post
On your own domain, wherever your app is built. Point a subdomain or a /blog path at Blogizi once, then publish from Codex.
Next.js
Lovable
Vercel
Webflow
Framer
Replit
Bolt
v0
AstroThe same Blogizi account works with every agent below, through the Blogizi MCP server or the Blogizi CLI. Plans and the free trial are on the pricing page.
ChatGPTThe chat-app route for OpenAI users who aren't in a terminalClaude CodeThe same workflow with Anthropic's terminal coding agent
CursorWrite posts from the Cursor editor with the Blogizi MCP server
MCP ServerThe MCP endpoint Codex, ChatGPT, Claude and Cursor connect to
ClaudeOfficial directory connector
Claude CoworkDirectory connector on your desktopThe skill, CLI and MCP server are free. Codex is billed by OpenAI. Blogizi starts with a 7-day trial for $0, then plans run from $9/month. The Search Console loop needs Pro or Agency.
Compare Blogizi plansblogizi login keeps its token in ~/.blogizi/config.json; the MCP route signs in through your browser. In CI, BLOGIZI_API_KEY lives in a secret. Never put a key in the repo.
Codex is OpenAI's coding agent. It runs as the Codex CLI in your terminal, as an IDE extension and in the cloud, reads your codebase, runs commands in a sandbox, and can load skills and call MCP servers. That's how it writes and publishes blog posts with Blogizi.
Install Blogizi once and let a second Codex session turn what you shipped into drafts on your own domain.
Your agents write. Blogizi publishes. Google sends the traffic to your domain.
