Claude Code
One command, then sign in to Blogizi in the browser tab that opens.
claude mcp add --transport http blogizi \
https://blogizi.com/api/mcpPrefer the Blogizi plugin? See the Claude Code guide.
Blogizi's hosted MCP server lets any MCP client draft, update and publish posts on your domain and read Search Console data. Use it from Claude, ChatGPT, Cursor, Codex, Hermes or your own agent. Drafts by default; keep a human in the loop.
MCP (Model Context Protocol) is the open standard that lets AI assistants call outside apps as tools. The Blogizi MCP server turns your blog into those tools, so any MCP client can write, update and publish posts on your own domain.
Tell your agent what to write. It calls the right Blogizi tools for you.
One connection reaches every project on your account.
Hosted, streamable HTTP at one URL. Nothing to run.
publish_post is a separate tool, so nothing goes live by accident.
Upload a cover or inline images with upload_post_image.
Sitemaps, schema, OG images and canonicals on every post, on your own domain.
Seven tools cover the whole job: find the blog, list what's live, draft, add images, update, publish, and decide what to write next.
| What it does | What you'd ask | Plan | |
|---|---|---|---|
| list_projects | Lists the blogs on your account | “Which blogs do I have?” | All |
| list_posts | Lists posts (defaults to published) | “What posts are already live?” | All |
| draft_post | Saves a markdown post as a draft | “Draft a post about our new export feature” | All |
| update_post | Updates a post by slug, same URL | “Update the pricing post with this year's numbers” | All |
| upload_post_image | Uploads a cover or inline image | “Use this screenshot as the cover” | All |
| publish_post | Publishes a post | “Publish the export post” | All |
| get_search_performance | Clicks, impressions, CTR, position and what to write next | “What should I write next?” | Pro |
Copy the link, add it to your AI client, sign in to Blogizi, then ask. Most clients take under a minute.
One command, then sign in to Blogizi in the browser tab that opens.
claude mcp add --transport http blogizi \
https://blogizi.com/api/mcpPrefer the Blogizi plugin? See the Claude Code guide.
Once connected, your agent calls Blogizi tools. Posts land as drafts on your domain and go live only when you approve.
Also try
Connect once. Every blog on your Blogizi account is reachable from any MCP client, on a subdomain or under yourapp.com/blog.
Every client points at the same endpoint. Most sign in with your Blogizi account; a Bearer key is the fallback.
| Capability | How to connect | Command or setting | Auth |
|---|---|---|---|
| Claude | Official directory connector | claude.ai/directory/blogizi | Sign-in |
| Claude Cowork | Same connector, shared with Claude | claude.ai/directory/blogizi | Sign-in |
| Claude Code | One command (or the Blogizi plugin) | claude mcp add --transport http blogizi https://blogizi.com/api/mcp | Sign-in |
| ChatGPT | Custom connector in Developer mode | Settings → Apps & Connectors → Create | Sign-in |
| Cursor | mcpServers JSON | ~/.cursor/mcp.json | Sign-in |
| Codex | codex mcp add | codex mcp add blogizi --url https://blogizi.com/api/mcp | codex mcp login blogizi |
| Hermes Agent | mcp_servers in config.yaml | ~/.hermes/config.yaml | hermes mcp login blogizi |
| NanoClaw | MCP server on one group | ncl groups config add-mcp-server --name blogizi --url https://blogizi.com/api/mcp | Key in the credential vault |
| Claude Desktop | mcp-remote bridge (stdio) | npx -y mcp-remote https://blogizi.com/api/mcp | Sign-in |
| Any other MCP client | The MCP link | https://blogizi.com/api/mcp | Sign-in or Bearer key |
Using an agent that doesn't support MCP, like OpenClaw or Paperclip? Use the Blogizi skill and CLI instead: npx skills add bytemindlab/blogizi-agent, then blogizi login.
get_search_performance returns clicks, impressions, CTR and position compared with the previous period, plus a ranked list of what to write next and which posts Google hasn't indexed yet, so any agent can choose its next post (Pro).
Clients sign in with your Blogizi account, so there's no key to leak. An account key is only for CI and clients without sign-in.
The agent only reaches the blogs on your Blogizi account.
Drafts by default; revoke access anytime in Account → Connected apps.
get_search_performance returns clicks, impressions, CTR and position compared with the previous period, plus a ranked list of what to write next and which posts Google hasn't indexed yet (Pro).
No separate analytics tool to wire up. Any agent connected to Blogizi can read your Search Console data and pick its next post from it.
period last 28 days vs previousclicks 1,284 ▲ 18%impressions 41,900 ▲ 9%avg position 14.2 ▲ 1.6 # write next 1. "markdown blog for saas" pos 13 2. "add blog to nextjs" pos 16 3. "notion to markdown" pos 19 # not indexed: 2 posts
Anything you'd brief a writer on. Name the topic, the keyword and the tone; your agent handles the rest through Blogizi.
draft_post
upload_post_image
get_search_performance, Pro
publish_post
On your own domain, wherever your app is built. Point a subdomain or a /blog path at Blogizi once, then publish from your agent.
Step-by-step setup for each client, all using the same Blogizi account. Plans and the free trial are on the pricing page.
The MCP server is included in every Blogizi plan. Your agent is billed by your AI provider. 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 plansClients sign in with your Blogizi account (OAuth); revoke access in Account → Connected apps. Account API keys, for CI and clients without sign-in, can be regenerated in Account → API.
An MCP server exposes an app to AI assistants as tools. The Blogizi MCP server exposes your blog, so any MCP client can draft, update and publish posts on your own domain.
One endpoint between your agent and a blog that ranks. Connect once, approve the drafts.
Your agents write. Blogizi publishes. Google sends the traffic to your domain.