Docs
Codex MCP server
Connect blogr to OpenAI Codex with one command. Your coding agent can check rankings, read the content plan and edit drafts while it works on your site.
How it works
Codex is OpenAI's coding agent for the terminal and the IDE. Add blogr as an MCP server and Codex can pull your published articles, topical map and Search Console numbers into the same session where it edits your site's code. That makes jobs like "add internal links to the articles that already rank" or "which blog pages still need a template" one prompt instead of an afternoon.
Codex acts as you, with your team role on each website, and can change only what your role allows.
What you need
- A blogr account. Each website's data is available while its owner has an active plan or trial.
- The Codex CLI or the Codex IDE extension, signed in with ChatGPT or an API account.
Connect Codex
- Add the server:
codex mcp add blogr --url https://blogr.ai/mcp- Sign in. Codex opens blogr in your browser, where you choose Allow access:
codex mcp login blogr- Start Codex and ask "Using blogr, list my websites."
Prefer editing config by hand? The same server in ~/.codex/config.toml:
[mcp_servers.blogr]
url = "https://blogr.ai/mcp"Things to ask Codex
- "Pull my published articles from blogr and check every one has a route and a sitemap entry in this project."
- "Which pages in my topical map are designed but not live yet? Scaffold the templates for them."
- "Find my articles that rank 8 to 20 and suggest internal links from the pages in this repo."
- "Fix the code sample in my newest draft so it runs on PHP 8.4."
What Codex can do
Codex reads without asking. Every tool that changes something is marked as a write, so Codex asks you to confirm before it runs.
| Tool | What it does | Changes data |
|---|---|---|
| list_websites | Your websites, your role on each, and whether each has a plan, a topical map and Search Console. | No |
| get_website_overview | Article counts by status, what is scheduled next, failures, map coverage and the monthly allowance left. | No |
| list_articles | Articles by status, with dates and live links. | No |
| get_article | One article in full: the Markdown body, SEO title, meta description, categories and tags. | No |
| get_topical_map | The map by silo, then each page with its query, search volume, difficulty and current rank. | No |
| get_performance | Search Console clicks, impressions, CTR and position for 7, 28 or 90 days, with top queries and pages. | No |
| get_article_impact | How recent articles are moving in Google week over week. | No |
| list_opportunities | The SEO opportunities blogr found in your Search Console data. | No |
| get_usage | Your plan and this month's article allowance. | No |
| approve_titles | Approves titles onto your publishing schedule, one per slot, the same as the approval tray. | Yes |
| decline_titles | Declines titles that are not written yet. You can approve them again later. | Yes |
| add_article_idea | Adds your own title on the next open slot, like Add title in the app. | Yes |
| reschedule_article | Moves a scheduled article to another day and pins it there. | Yes |
| update_article | Renames a title, or edits a written draft's title, body, SEO fields, categories and tags. | Yes |
What Codex cannot do
- Publish, delete or archive articles. Publishing stays in blogr, so nothing reaches your live site from Codex.
- Start writing an article early. Approved titles are written on their scheduled day, within your monthly allowance.
- See or change billing, website settings, team members, or your publishing connection and its tokens.
An edit to a published article is saved in blogr. The live page changes the next time you publish that article from blogr.
Team roles
Codex follows your role on each website. Viewers can read everything they see in the app, and Codex cannot change anything for them. Editors and admins can approve, decline, add, reschedule and edit through Codex. Owners can do all of it.
Limits
- 120 requests per minute per account, across every assistant you connect.
- 200 changes per account per hour.
- 25 titles added through an assistant per website per day.
Past a limit, Codex gets a message saying so and can try again later. Nothing you do in the app counts toward these limits.
Your data
- Codex receives only what you ask for: your websites, articles, topical map, Search Console performance and opportunities.
- blogr never sees your Codex conversations. For each request it records which tool ran, on which website, whether it worked and how long it took, and deletes that record after 90 days.
- Codex signs in with its own access token, which never includes your password. To disconnect, run codex mcp logout blogr, or remove the server from your Codex config.
Once Codex receives data from blogr, OpenAI handles it under its privacy policy. Read blogr's own privacy policy for what we store.
Troubleshooting
- The browser does not open on login: copy the link Codex prints into your browser. Sign-in finishes on a local callback, so run it on the machine where Codex runs.
- "blogr needs an active plan or trial": start a plan or trial on the account that owns the website.
- "Your role does not allow this": ask the website owner to give you the Editor or Admin role.
- Codex asks you to sign in again: your connection expired after 90 days without use. Run codex mcp login blogr.
Questions
How do I add blogr to Codex?
Run codex mcp add blogr --url https://blogr.ai/mcp, then codex mcp login blogr to sign in.
Does Codex need an API key for blogr?
No. Codex signs in with OAuth in your browser. blogr issues it its own token, and you never paste a password or a key.
Can Codex publish articles?
No. Codex can approve, decline, add, reschedule and edit articles. Publishing stays in blogr.