How do I add Blogizi to Cursor?

Paste the Blogizi server block into ~/.cursor/mcp.json (or .cursor/mcp.json for one project), restart Cursor and sign in to Blogizi. Or install the skill with npx skills add bytemindlab/blogizi-agent and the CLI with npm install -g blogizi.

Is there a Blogizi plugin in the Cursor Marketplace?

Not yet. Use the MCP server or the skill + CLI; both reach the same blogs and tools.

Do I need an API key?

No. The MCP server signs in with your Blogizi account and blogizi login uses your browser. An API key header is optional, for setups where sign-in isn't possible.

MCP for no terminal and the Search Console loop. Skill + CLI if you want posts as markdown files in the repo with local images auto-uploaded.

Can Cursor write posts without me watching?

Cursor needs to be open for its Agent to run. Batch a week of drafts in one prompt, or use Codex or Claude Code in CI for unattended runs.

Does it publish automatically?

No. Drafts by default; publishing is a separate step you approve.

Cursor doesn't see the Blogizi tools. What should I check?

Check the JSON in mcp.json, make sure the server is enabled in Cursor's MCP settings, restart Cursor, and mention Blogizi in your prompt.

Which Blogizi plan do I need?

Any plan publishes. Search Console needs Pro or Agency. Every plan starts with a 7-day trial for $0.

Cursor + Blogizi

Publish blog posts from Cursor

Add the Blogizi MCP server to Cursor in one JSON block
Cursor's Agent writes the post from the code you have open
Drafts land on your blog; publish when you're ready

Cursor's Agent writes the post and publishes it through the Blogizi MCP server, or the Blogizi CLI in Cursor's terminal. Great for changelogs, tutorials and docs-style posts written next to the code they explain.

Cursor mascot writing a blog post on a laptop

Draft saved · blog.yourapp.com

How to install Blogizi in Cursor

Two routes: add the Blogizi MCP server to .cursor/mcp.json (fastest, no terminal), or install the Blogizi skill and CLI so the Agent drafts from markdown files. Both take under a minute.

1 Connectunder a minute

Add the Blogizi MCP server

Paste into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor's Agent then calls the Blogizi tools directly.

MCP server

{
  "mcpServers": {
    "blogizi": {
      "url": "https://blogizi.com/api/mcp"
    }
  }
}

Cursor opens Blogizi sign-in the first time it connects; no key in the file. Prefer a key? Add "headers": { "Authorization": "Bearer YOUR_ACCOUNT_API_KEY" } and keep the file out of git.

2 Askdraft on your blog

Ask Cursor to write the post

Once connected, Cursor calls Blogizi tools. Posts land as drafts on your domain and go live only when you approve.

Write a tutorial on how our webhook retries work using the open files, and draft it on Blogizi.

Drafted "Reliable webhooks: retries with exponential backoff". Included 3 snippets from src/webhooks/retry.ts. Saved as a draft. Publish?

via Blogizi

Also try

List my blogsAdd a sequence diagramPublish it

1Add Blogizi: paste the server into ~/.cursor/mcp.json, or run npx skills add bytemindlab/blogizi-agent.
2Sign in: restart Cursor and sign in to Blogizi when it connects (or run blogizi login for the CLI).
3Check: ask the Agent “List my Blogizi blogs”.
4Ask: tell the Agent what to write and which keyword to target. It drafts the post on your domain.

One MCP server puts every blog in your editor

Set up your blogs in Blogizi once, then draft to any of them from Cursor's Agent panel, on a subdomain or under yourapp.com/blog.

list_projects
list_posts
draft_post
update_post
publish_post
upload_post_image
get_search_performance

Which install route should I pick?

MCP for most people: no terminal, and the same link works in Claude and ChatGPT. The skill + CLI if you want posts as markdown files in the repo.

Capability	Blogizi MCP server	Skill + CLI
Install	Paste the server into .cursor/mcp.json	npx skills add bytemindlab/blogizi-agent + npm install -g blogizi
What it adds	The six Blogizi MCP tools	The Blogizi skill and the blogizi CLI in the terminal
Authentication	Sign in to your Blogizi account; no key stored	blogizi login in the browser, or BLOGIZI_API_KEY
Images	upload_post_image	Relative paths auto-uploaded on draft
Search Console	Yes (Pro)	Not in the CLI
Best for	Most people; same link works in Claude and ChatGPT	Posts as markdown files in the repo

There's no Blogizi plugin in the Cursor Marketplace yet; both routes reach the same blogs and tools.

What can Cursor do with Blogizi?

With Search Console connected, Cursor's agent can pull your page-2 queries over MCP and write a post for each, using the code in your workspace.

Next to the code

Write tutorials from the files open in your editor, with real snippets.

Changelog posts

Summarise what shipped on a branch into a readable post.

Project or global

Configure Blogizi per project or for every workspace.

Images included

Cover and inline images upload with the post.

Update in place

Fix a post and re-push it to the same URL.

Search Console

Find the queries you're on page 2 for and write for them (Pro).

What is Cursor?

Cursor is an AI code editor by Anysphere. Its Agent can edit files, run terminal commands and call MCP tools, which is how it writes and publishes blog posts on your own domain with Blogizi.

Editor native

The Agent runs inside the editor you already code in. No extra app.

Skills & MCP

Cursor extends its Agent with MCP servers and skills. Blogizi ships both.

Autonomous Agent

It chains reading code, writing, uploading images and drafting without manual steps.

Is Cursor the same as Claude Code or Codex?

No. Cursor is an editor with a built-in Agent. Claude Code and Codex are coding agents you run in the terminal. All three can publish to Blogizi.

	Cursor	Claude Code	Codex
Made by	Anysphere	Anthropic	OpenAI
Where it runs	Inside the Cursor editor	Terminal, VS Code, JetBrains	Terminal, IDE extension, cloud
How Blogizi connects	MCP in mcp.json, or skill + CLI	Blogizi plugin, skill + CLI, or MCP	Blogizi skill + CLI, or MCP server
Headless automation	No; Cursor must be open	claude -p in scripts and CI	codex exec in scripts and CI
Best for	Writing posts while you code	Release posts from code, CI	Release posts from code, CI

Dedicated guides: Claude Code + Blogizi, and Codex + Blogizi.

How does Blogizi work in Cursor?

Add the Blogizi server to mcp.json and the Agent discovers the Blogizi tools. Or install the Blogizi skill, which teaches the Agent the Blogizi CLI it runs in the integrated terminal.

✓Global (~/.cursor/mcp.json) or per project (.cursor/mcp.json)
✓Sign in to Blogizi when Cursor connects; no key in the file
✓CLI commands run in Cursor's integrated terminal
✓Works with any model you pick in Cursor
✓Drafts by default; publish is a separate step

Install in Cursor

# Option A: ~/.cursor/mcp.json{  "mcpServers": {    "blogizi": { "url": "https://blogizi.com/api/mcp" }  }} # Option B: skill + CLI, in the terminalnpx skills add bytemindlab/blogizi-agentnpm install -g blogizi && blogizi login # Then, in the Agent panel> List my Blogizi blogs

How to write a post from the Cursor Agent panel

Ask in the Agent panel while you work. Cursor reads your code, writes the post and drafts it through Blogizi, and you keep coding in another tab.

From the Agent panel

One prompt, grounded in your code

Point the Agent at the files the post is about. It writes the markdown with real snippets and saves a draft on your blog.

Cursor Agent

> Summarise this branch's changes into a  changelog post and draft it on Blogizi. Agent: Read 9 changed files on feat/webhooks.  Drafted "What's new: reliable webhooks"  (820 words, 2 snippets) via draft_post.  Saved as a draft on blog.yourapp.com.

Parallel Agent tabs

Blog and build side by side

Open more than one Agent tab. One writes the post, one checks what to write next, one keeps refactoring; each runs on its own.

Multiple Agent tabs

# Tab 1 — write the post> Write a tutorial for the open file and draft it # Tab 2 — what to write next (Pro)> Which queries am I on page 2 for?  Suggest three posts # Tab 3 — keep coding> Refactor the auth module to use JWT

Why Cursor + Blogizi

✓Write the post right next to the code it explains
✓Real snippets from your workspace, not invented ones
✓Global or per-project setup in mcp.json
✓Your own domain, with SEO handled on every post
✓Drafts by default; you publish when it's right
✓Same blogs and dashboard as your other agents

Blogizi tools the Agent can call

# Your blogslist_projects           every blog you run # Writingdraft_post              save a draftupdate_post             edit in place, same URLupload_post_image       cover + inline imagespublish_post            go live, when you say so # Growth (Pro)get_search_performance  Search Console clicks, queries

Can Cursor write blog posts on a schedule?

Cursor needs to be open for its Agent to run. Batch the work into one prompt while you're there, or hand recurring posts to an agent that runs headless.

Batch drafts from one prompt

Ask the Agent for a week of posts from a folder of notes or a list of merged PRs, and get them all as drafts.

Unattended runs

For recurring posts, run the same Blogizi setup headless with Codex (codex exec) or Claude Code (claude -p) in CI.

Scoped, revocable access

MCP signs in with your Blogizi account and only reaches your blogs. Revoke it anytime in Account → Connected apps.

What can I ask Cursor to write?

Anything you'd brief a writer on. Name the topic, the keyword and the tone; Cursor handles the rest through Blogizi.

From your editor

Tutorial

Write a tutorial for the open file and draft it.

Release notes

Changelog

Summarise this branch's changes into a changelog post.

Needs Search Console (Pro)

Near-miss query

Find a page-2 query and write the post for it.

Repurposing

Docs to post

Turn README.md's setup section into a getting-started post.

Where can Cursor publish?

On your own domain, wherever your app is built. Point a subdomain or a /blog path at Blogizi once, then publish from Cursor.

Next.js
Lovable
Vercel
Webflow
Framer
Replit
Bolt
v0
Astro
subSubdomain
/b/blog path
↪Any reverse proxy

Related Blogizi guides for AI agents

The 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.

Pricing, security, and troubleshooting

How much does it cost?

The MCP server, skill and CLI are free. Cursor is billed by Cursor. 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 plans

How is access secured?

MCP signs in with your Blogizi account, so no key sits in mcp.json. If you use an API key header instead, keep it in the global file and out of git. Revoke access anytime in Account → Connected apps.

Something not working?

✓Server shows red in Cursor settings: check the JSON and restart Cursor.
✓Agent doesn't use the tools: mention Blogizi in your prompt.
✓Skill not found: restart Cursor after npx skills add.

Frequently asked questions

Cursor is an AI code editor by Anysphere. Its Agent can edit files, run terminal commands and call MCP tools, which is how it writes and publishes posts with Blogizi.

Write the post where the code lives

Add Blogizi to Cursor once and let the Agent turn what you shipped into drafts on your own domain.

Add to Cursor

Ready to get started?

Your agents write. Blogizi publishes. Google sends the traffic to your domain.