
npx skills add bytemindlab/blogizi-agent
npx skills add bytemindlab/blogizi-agent
·
npx skills add bytemindlab/blogizi-agentDraft and publish markdown posts to your Blogizi blog.
This README is the primary documentation for the CLI: install, usage, public API reference, and local development. Site docs: blogizi.com/docs/cli-publishing.
AI coding agents should write (or edit) the .md file themselves, then call blogizi draft / blogizi update / blogizi publish. See SKILL.md.
The hosted MCP server at https://blogizi.com/api/mcp supports OAuth, so most clients only need the URL and sign in with Blogizi on first use. The Claude plugin (plugins/blogizi/.mcp.json), .cursor-plugin/mcp.json and gemini-extension.json register it that way.
The Claude plugin (blogizi) lives in plugins/blogizi, and this repo's .claude-plugin/marketplace.json lists it. It contains:
plugins/blogizi/skills/blogizi/SKILL.md, a copy of SKILL.md; run npm run sync:skill after editing SKILL.md) that tells Claude how to write a post as markdown with frontmatter and publish it with the Blogizi CLI.plugins/blogizi/.mcp.json) that connects Claude to the hosted Blogizi MCP server at https://blogizi.com/api/mcp. You sign in with your Blogizi account (OAuth) the first time a tool is used.blogizi CLI from npm (npm install -g blogizi), whose full source is in src/ of this repo.blogizi.com: the post's markdown, frontmatter and any images you choose to upload, plus your Blogizi sign-in token. Search Console data is read from Blogizi, which stores it for your project.~/.blogizi/config.json (mode 600) after blogizi login. Disconnect any time with blogizi logout or in Dashboard → Account → API → Connected apps.From the Claude community marketplace, once listed, or straight from this repo:
/plugin marketplace add bytemindlab/blogizi-agent
/plugin install blogizi@blogizi-agentLocal test:
claude plugin validate --strict plugins/blogizi
claude --plugin-dir plugins/blogizinpm install -g blogiziFrom source (see Development):
git clone https://github.com/bytemindlab/blogizi-agent.git
cd blogizi-agent
npm install
npm run build
npm link # optional: expose `blogizi` globally from this checkoutVerify:
blogizi --version
blogizi --helpblogizi loginThis opens Blogizi in your browser and shows a code like BCDF-GHJK. Check that it matches, click Approve, and the CLI is signed in. No API key to copy. Sessions refresh automatically; disconnect any time in Dashboard → Account → API → Connected apps, or run blogizi logout. On a remote machine, blogizi login --no-browser prints the URL to open elsewhere.
Prefer an API key? Copy your account API key from Dashboard → Account → API and run:
blogizi auth YOUR_ACCOUNT_API_KEYIn CI, skip the config file and set environment variables instead:
export BLOGIZI_API_KEY=YOUR_ACCOUNT_API_KEY
export BLOGIZI_PROJECT=your-project-slug # optionalOrder of precedence: blogizi login session → blogizi auth key → BLOGIZI_API_KEY. BLOGIZI_PROJECT overrides the stored active project.
blogizi use your-project-slug
# or in one step:
blogizi auth YOUR_ACCOUNT_API_KEY --project your-project-slugWith a single project, the API picks it automatically — you can skip blogizi use.
Credentials are stored in ~/.blogizi/config.json (file mode 600). After blogizi login it holds an OAuth access token and a rotating refresh token; after blogizi auth it holds your API key:
{
"apiKey": "…",
"apiUrl": "https://blogizi.com",
"projectSlug": "your-project-slug",
"authMethod": "api_key"
}Check what the CLI is using with blogizi status. Treat the file like a password. Never commit it to git or paste its contents into chat logs.
# Save as draft in the dashboard (not live)
blogizi draft ./posts/go-chi-middleware.md
# Schedule a draft for later (project timezone if no Z/offset)
blogizi draft ./posts/go-chi-middleware.md --scheduled-at "2026-10-26T09:00"
# or set scheduledAt in frontmatter, then:
blogizi draft ./posts/go-chi-middleware.md
# Update an existing post by slug (keeps draft/published unless frontmatter sets status)
blogizi update ./posts/go-chi-middleware.md
blogizi update ./posts/go-chi-middleware.md --scheduled-at "2026-10-27T14:30"
blogizi update ./posts/go-chi-middleware.md --unschedule
# Publish live immediately (cancels any pending schedule)
blogizi publish ./posts/go-chi-middleware.mddraft forces status: draft; publish forces status: published and clears any schedule. update sends upsert: true and only changes status when the file sets status explicitly — otherwise the post keeps its current visibility. A future scheduledAt keeps the post as a draft until Blogizi publishes it at that time.
blogizi use another-project-slug| Command | Description |
|---|---|
blogizi login [--project <slug>] [--no-browser] | Sign in through the browser (OAuth device flow) |
blogizi logout | Sign out and revoke this device's session |
blogizi status (alias whoami) | Show auth method, active project and reachable blogs |
blogizi auth <apiKey> [--project <slug>] | Save account API key (and optional project) |
blogizi use <projectSlug> | Set active project for draft/update/publish |
blogizi draft <file> [--scheduled-at <when>] | Save a local .md file as a draft (auto-uploads relative images; optional schedule) |
blogizi update <file> [--scheduled-at <when>] [--unschedule] | Update an existing post by slug (upsert) |
blogizi publish <file> | Publish a local .md file live (cancels schedule) |
blogizi upload <file> --slug <post> | Upload a cover or content image; prints URL / markdown |
blogizi draft path/to/post.md → review in the dashboard.blogizi update path/to/post.md (same slug).blogizi publish path/to/post.md.Posts are markdown with YAML frontmatter (same shape as Write in Markdown):
---
title: "How we built our auth flow"
description: "A short meta description"
keyword: "indie app authentication"
slug: how-we-built-our-auth-flow
status: "draft"
date: "2026-08-07"
readingTime: 0
wordCount: 0
# Optional per-post CTA (overrides project branding when title + button label + URL are set)
ctaTitle: "Ship this workflow on your domain"
ctaSubtitle: "Drafts by default — publish when you confirm."
ctaButtonLabel: "Start free trial"
ctaButtonUrl: "https://blogizi.com/#pricing"
# Optional per-post sidebar CTA (sticky card beside the post; overrides the project sidebar CTA when title + button label + URL are set)
sidebarCtaTitle: "Publish from your repo"
sidebarCtaText: "Agents write, Blogizi hosts the SEO blog."
sidebarCtaBullets:
- "🚀 Set up in minutes"
- "Drafts first, publish when you confirm"
sidebarCtaButtonLabel: "Start free trial"
sidebarCtaButtonUrl: "https://blogizi.com/#pricing"
# Optional schedule (draft until then). ISO with Z/offset is absolute;
# naive YYYY-MM-DDTHH:mm uses the project timezone (Settings → General).
# scheduledAt: "2026-10-26T09:00"
# scheduledAt: null # clear a schedule on update
---
Your markdown content here.The CLI recalculates readingTime / wordCount on parse and strips a duplicate H1 that matches title when present. Omit CTA fields to keep the project default (or existing values on blogizi update).
scheduledAt in frontmatter, or pass --scheduled-at on draft / update (CLI flag wins).Z/offset (absolute UTC), or naive YYYY-MM-DDTHH:mm interpreted in the project timezone.draft until Blogizi publishes it (do not poll or run publish early).update, omit scheduledAt to leave the schedule unchanged; set scheduledAt: null (or --unschedule) to clear it.blogizi publish always goes live immediately and cancels any pending schedule.Base URL: https://blogizi.com
Account-scoped API key (authorizes all projects you own), or an OAuth access token from blogizi login / a connector (same permissions):
Authorization: Bearer YOUR_ACCOUNT_API_KEYOAuth 2.1 metadata lives at https://blogizi.com/.well-known/oauth-authorization-server (authorization code + PKCE, dynamic client registration, client ID metadata documents, refresh-token rotation, and the device grant used by the CLI).
Optional project selector when you have multiple projects (any one of these):
X-Blogizi-Project: your-project-slugOr in the JSON body: projectSlug, project, or projectId.
With a single project, the server selects it automatically.
Get or regenerate the key in the dashboard (session auth):
GET /api/account/keys
POST /api/account/keysPOST /api/posts
Content-Type: application/json
Authorization: Bearer YOUR_ACCOUNT_API_KEY
X-Blogizi-Project: your-project-slugBody
| Field | Type | Notes |
|---|---|---|
title | string | Required |
slug | string | Required; URL path segment |
description | string | Optional meta description |
keyword | string | Optional focus keyword |
content | string | Markdown body (without frontmatter) |
ctaTitle | string | Optional per-post CTA title |
ctaSubtitle | string | Optional per-post CTA subtitle |
ctaButtonLabel | string | Optional per-post CTA button label |
ctaButtonUrl | string | Optional per-post CTA button URL |
sidebarCtaTitle | string | Optional per-post sidebar CTA title |
sidebarCtaText | string | Optional per-post sidebar CTA paragraph |
sidebarCtaBullets | string[] | Optional per-post sidebar CTA bullet points (max 6) |
sidebarCtaButtonLabel | string | Optional per-post sidebar CTA button label |
sidebarCtaButtonUrl | string | Optional per-post sidebar CTA button URL |
scheduledAt | string | null | Optional future publish time (ISO or naive local in project timezone). Future → draft + schedule; null clears; omit leaves unchanged on upsert |
frontmatter | object | Optional; merged metadata (CTA keys also read from here) |
status | "draft" | "published" | Visibility (published publishes immediately and cancels any schedule) |
projectSlug | string | Optional alternative to the header |
upsert | boolean | If true, update an existing post with the same slug instead of failing (blogizi update and the Obsidian plugin) |
Per-post CTA shows when ctaTitle, ctaButtonLabel, and ctaButtonUrl are all set. The per-post sidebar CTA works the same way with sidebarCtaTitle, sidebarCtaButtonLabel, and sidebarCtaButtonUrl (and shows even when the project sidebar CTA is off; style and image come from the project). On upsert, omit a CTA field to keep the existing value. Response data.scheduledAt is UTC ISO when scheduled; queue ids are never returned.
Success response (simplified):
{
"data": { "slug": "how-we-built-our-auth-flow", "...": "..." },
"project": { "id": "…", "slug": "your-project-slug" },
"created": true
}Public URL pattern: https://{projectSlug}.app.blogizi.com/{postSlug}
GET /api/account/projects
Authorization: Bearer YOUR_ACCOUNT_API_KEY{
"data": [
{ "id": "…", "name": "My Blog", "slug": "my-blog" }
]
}GET /api/projects/{projectId}/posts
POST /api/projects/{projectId}/posts
Authorization: Bearer YOUR_ACCOUNT_API_KEYPOST accepts the same create payload as /api/posts (project implied by the path).
Update/delete by post id is currently dashboard session auth only:
PATCH /api/projects/{projectId}/posts/{postId}
DELETE /api/projects/{projectId}/posts/{postId}GET /api/sites/{projectSlug}/posts?page=1&limit=10&tag=optional
GET /api/sites/{projectSlug}/search?q=query
POST /api/sites/{projectSlug}/analytics
GET /api/resolve-domain?host=blog.example.comcurl -sS -X POST https://blogizi.com/api/posts \
-H "Authorization: Bearer $BLOGIZI_API_KEY" \
-H "Content-Type: application/json" \
-H "X-Blogizi-Project: your-project-slug" \
-d '{
"title": "Hello from curl",
"slug": "hello-from-curl",
"description": "Posted via the public API",
"keyword": "blogizi api",
"content": "This post was created with curl.\n",
"status": "draft"
}'Machine-oriented overview: blogizi.com/llms.txt.
git clone https://github.com/bytemindlab/blogizi-agent.git
cd blogizi-agent
npm install| Script | Description |
|---|---|
npm run build | Compile TypeScript → dist/ and mark the bin executable |
npm run dev | Run the CLI via tsx without building (tsx src/index.ts) |
npm start | Run the compiled dist/index.js |
Examples:
npm run build
node dist/index.js --help
npm run dev -- draft ./posts/example.md.claude-plugin/plugin.jsonThis project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
Copyright (c) 2026 Blogizi.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/blogizi-cli to learn what the "Blogizi CLI" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx skills add bytemindlab/blogizi-agentnpm install -g blogiziThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/blogizi-cli)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "blogizi-cli" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.