MCP Overview | Blogizi Docs

Blogizi exposes a Streamable HTTP MCP server at https://blogizi.com/api/mcp. Sign in with your Blogizi account (OAuth), or authenticate with the same account API key as the CLI and Public API.

Add as a connector (sign in with Blogizi)

Claude (web, desktop, mobile and Cowork), ChatGPT, Perplexity and any client that supports MCP OAuth only need the URL:

https://blogizi.com/api/mcp

In Claude: Settings → Connectors → Add custom connector, paste the URL. In ChatGPT or Perplexity, add a custom connector with the same URL.
Sign in to Blogizi and click Allow.
Manage or disconnect apps anytime in Dashboard → Account → API → Connected apps.

Claude Code without a header opens the same sign-in in your browser:

claude mcp add --transport http blogizi https://blogizi.com/api/mcp

Connect with an API key

{
  "mcpServers": {
    "blogizi": {
      "url": "https://blogizi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCOUNT_API_KEY"
      }
    }
  }
}

Get the key from Dashboard → Account → API. See Authentication.

Stdio-only clients

If your client only supports stdio MCP, bridge with mcp-remote:

{
  "mcpServers": {
    "blogizi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://blogizi.com/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_ACCOUNT_API_KEY"
      ]
    }
  }
}

Tools

list_projects — list blogs for the account
list_posts — list posts (defaults to published; metadata only)
draft_post — create a new draft (fails if the slug exists); optional scheduledAt
update_post — upsert by slug; omit status to keep draft/published; optional scheduledAt
publish_post — upsert and publish immediately (cancels any schedule)
schedule_post — schedule or unschedule an existing post
upload_post_image — upload cover or inline content image (base64)
get_search_performance — cached Google Search Console stats for a bound project

Pass projectSlug on post tools when the account has more than one project (same rule as blogizi use). For a future go-live, set scheduledAt on draft_post / update_post or call schedule_post — Blogizi publishes at that time; agents should not poll or call publish_post early. After you connect Search Console, agents can call get_search_performance on the same server they publish with — see SEO MCP.

Prefer the CLI for local files

For repo workflows where the agent writes a .md file, prefer blogizi draft/update/publish. Use MCP when the client has no shell or you want direct tool calls.

Coming from WordPress? Connecting an agent to WordPress usually means a WordPress MCP server, application passwords, and plugins. See WordPress MCP alternative for how the Blogizi MCP compares.