Claude Cowork + Blogizi

Turn your notes into blog posts with Claude Cowork

  • Add Blogizi as a connector in the Claude desktop app, once
  • Point Cowork at a folder of notes and get drafts on your blog
  • No terminal, no API key, and a weekly routine if you want one
Add to Cowork

Cowork works with the files on your computer and the connectors you add. With Blogizi connected, it turns notes, docs and meeting transcripts into drafts on your own domain. You approve before anything goes live.

Claude mascot turning notes into a blog post on a laptop
6 notes → 1 draft · blog.yourapp.com

How do you connect Blogizi to Claude Cowork?

Connectors are shared across the Claude apps, so adding Blogizi once makes it available in Cowork. It takes about a minute, needs no terminal, and you sign in to Blogizi instead of pasting an API key. After that, you just ask.

1 Connectabout a minute

Add Blogizi from the Claude directory

Connectors are shared across the Claude apps. Add Blogizi from the directory once and it's available in Cowork, chat and on mobile.

Directory connector
# Open claude.ai/directory/blogizi
# Click Connect, sign in to Blogizi, Allow
# Then enable Blogizi in your Cowork task

No URL to paste and no API key. Already added Blogizi in Claude chat? You're done; enable it in Cowork.

2 Askdraft on your blog

Ask Claude Cowork to write the post

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

Read the notes in ~/Documents/launch-notes and turn them into a launch blog post. Save it as a draft on Blogizi.
Read 6 files in launch-notes. Drafted "We just launched: everything new in v2" with 3 screenshots. Saved as a draft. Want me to schedule this every Friday for new notes?
via Blogizi

Also try

Which blogs do I have?Make it shorterPublish it
  1. 1Open the directory: go to claude.ai/directory/blogizi in the Claude app or browser.
  2. 2Connect: click Connect. Or add https://blogizi.com/api/mcp as a custom connector.
  3. 3Sign in to Blogizi: approve access on the Blogizi screen. No API key is created or pasted.
  4. 4Check your blogs: ask Cowork “Which blogs do I have?” It lists every Blogizi project.
  5. 5Write a post: point it at your notes. It drafts the post with images and asks before publishing.

One connector powers every blog you run from Cowork

Connect Blogizi once. From then on Cowork can draft to any of your blogs from the desktop app, 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 way should you connect Blogizi to Cowork?

The directory connector is the default: no terminal, no URL to paste, and it's shared with your Claude account. The custom connector and the plugin exist for people who already use them.

CapabilityDirectory connectorCustom connectorBlogizi plugin
Where you add itclaude.ai/directory/blogizi (shared with your Claude account)Settings > Connectors > Add custom connectorClaude marketplace: bytemindlab/blogizi-agent
Terminal neededNoNoNo
AuthenticationBlogizi sign-in (OAuth)Blogizi sign-in (OAuth)Blogizi sign-in (OAuth)
Draft, publish, imagesYesYesYes
Search ConsoleYes (Pro)Yes (Pro)Yes (Pro)
Best forMost Cowork usersPeople who add connectors by URLPeople who also use Claude Code

All three use the same Blogizi account, blogs and tools. You can switch any time.

What can Claude Cowork do with Blogizi?

Set up a weekly Cowork scheduled task: read Search Console through Blogizi, pick two page-2 queries, draft a post for each, and leave them for your review.

Works with your files

Notes, docs, PDFs and screenshots on your computer become posts.

Scheduled tasks

Run a weekly content routine without opening a terminal.

Drafts by default

Cowork saves drafts; you publish when you're happy.

Images included

Screenshots from your folder are uploaded into the post.

Search Console aware

Cowork can read clicks and queries to decide what to write (Pro).

Nothing to install

No Node, no CLI, no config files. One connector in the Claude app.

How does blogging from Claude Cowork work?

You describe the post in plain language and Cowork handles the Blogizi calls. Here's how a typical conversation goes.

1

Find your blogs

Cowork lists every Blogizi project on your account and picks the one you name.

Example conversation
> Which blogs do I have on Blogizi? Claude Cowork: You have 2 blogs:  - blog.yourapp.com (Acme)  - yourapp.com/blog (Side project)  Which one should I write for?
2

Write from your files

Point it at notes, docs or transcripts. Cowork writes the post, adds images from your folder and saves a draft.

Example conversation
> Turn ~/Documents/launch-notes into a launch post for blog.yourapp.com. Claude Cowork: Read 6 files. Drafted  "We just launched: everything new in v2"  with 3 screenshots. Saved as a draft.
3

Review, publish, repeat

Ask for changes, publish when it's right, and check how posts perform in Search Console (Pro).

Example conversation
> Publish the launch post, then tell me which queries we're on page 2 for. Claude Cowork: Published at blog.yourapp.com/v2-launch.  Page-2 queries this month:  - "notion blog alternative" (pos 14)  - "blog for saas" (pos 17)  Want drafts for both?

One request, a whole week of posts

Ask once and Cowork works through the folder, writes each post with its own images, and saves them all as drafts for review. For example:

Example
> Go through ~/Documents/customer-calls, find  the 3 most common questions, and write a  post answering each one. Use screenshots  from ~/Desktop/product. Draft them on  blog.yourapp.com. Claude Cowork: Done. Read 14 transcripts. Drafts saved:  - "How to import from Notion" (2 screenshots)  - "Can I use my own domain?" (1 screenshot)  - "What happens when my trial ends?"  Review them in Blogizi; say "publish" for any of them.

What is Claude Cowork?

Claude Cowork is Anthropic's agentic assistant for knowledge work in the Claude desktop app. It uses the same agent architecture as Claude Code without a terminal: it works with files on your computer, uses connectors and plugins, runs multi-step tasks, and can repeat them as scheduled tasks. With Blogizi connected, one of those tasks is running your blog.

Claude CoworkClaude CodeClaude (chat)
What it isDesktop agent for knowledge work, in the Claude appTerminal coding agent for developersChat on web, desktop and mobile
How Blogizi connectsDirectory or custom connector, or the pluginBlogizi plugin, skill + CLI, or MCPDirectory connector
Terminal neededNoYesNo
Reads local filesYes, from folders and connected appsYes, from the working directoryUploads only
Recurring runsCowork scheduled tasksHeadless mode in cron or CIAsk each time
Best forFounders and writers with notesRelease posts from codeQuick posts from a chat

Dedicated guides: Blogizi with Claude Code, Blogizi connector for Claude, and the Blogizi MCP server.

How do blog workflows run in Claude Cowork?

Two ways: ask Cowork directly in the desktop app, where it reads your local files and connected apps, or turn the same request into a scheduled task that repeats on a timetable you choose.

Desktop workflow

No terminal needed

Tell Cowork what to write and where the material is. It reads the files, writes the post, uploads the images and saves a draft while you get on with your day.

Claude Cowork
> Turn this podcast transcript into a  blog post with 3 quotes and a summary. Claude Cowork: On it.  1. Read episode-42.txt (48 min)  2. Picked 3 quotes and wrote the summary  3. Saved the draft via Blogizi   Draft: "What we learned shipping v2"  blog.yourapp.com · draft · 1,320 words

Scheduled tasks

A weekly blog routine, no cron server

Make any Cowork task recurring. Each run uses the connectors you've set up, so Blogizi is there every time, and every post waits as a draft for your review.

Claude Cowork scheduled task
"Every Monday at 9am, check Search Consolethrough Blogizi, pick the 2 queries wherewe're on page 2, and draft a post for each.Use notes from ~/Documents/product-notes." Claude Cowork will, on each run:  1. Read Search Console (Pro)  2. Pick 2 near-miss queries  3. Draft a post for each on Blogizi  4. Report back with the draft links

Why Claude Cowork + Blogizi

  • ✓No terminal: Blogizi is a connector in the Claude app, added once
  • ✓Reads notes, docs, PDFs and transcripts from your folders
  • ✓Multi-step in one request: read, write, upload images, draft
  • ✓Scheduled tasks keep the blog moving every week
  • ✓Drafts by default; publishing is always your call
  • ✓Same Blogizi account and blogs as your dashboard and other agents
Blogizi tools Cowork can call
# Your blogslist_projects           your blogs # 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 data

Also works with Claude Code

The same Blogizi account works with any agent that can call MCP tools or run commands. That includes Claude Code, which installs the Blogizi plugin and writes posts straight from your repo.

Claude Code

Anthropic's terminal coding agent

Developers can write the release post from the code they just shipped, and run it headless in CI. Same blogs, same drafts, same dashboard.

Claude Code
> Write a post about the rate-limiting  middleware we just merged and draft it. Claude Code: wrote posts/express-rate-limiting.md  - blogizi draft posts/express-rate-limiting.md ✓

What can I ask Claude Cowork to write?

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

From local files

Notes to post

Turn everything in my launch-notes folder into one launch post.

Scheduled task, Pro

Weekly routine

Every Monday, find a page-2 query in Search Console and draft a post for it.

Repurposing

Transcript to article

Turn this podcast transcript into a blog post with quotes and a summary.

Updates in place

Update with screenshots

Replace the screenshots in my onboarding post with the ones in ~/Desktop/new.

Where can Claude Cowork publish?

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

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

Cowork vs Claude vs Claude Code: which guide do I need?

They're different products and Blogizi works with all of them. This page is for Claude Cowork.

Using another agent? See all agents.

Pricing, security, and troubleshooting

How much does it cost?

The connector and plugin are free. Claude Cowork is billed by Anthropic. 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?

The connector signs in with your Blogizi account (OAuth). No API key is created or pasted. Revoke it anytime in Account → Connected apps.

Something not working?

  • ✓Blogizi tools missing in a task: enable the connector for that task.
  • ✓Scheduled task didn't run: check the task's schedule and that the Blogizi connector is still enabled.
  • ✓Wrong blog: tell Cowork which project to use by name.

Frequently asked questions

Open claude.ai/directory/blogizi, click Connect and sign in to Blogizi. Connectors are shared across the Claude apps, so Blogizi is then available in Cowork; enable it in your task. You can also add https://blogizi.com/api/mcp as a custom connector. No terminal or API key is involved.

Give Cowork your notes

Give Cowork your notes. Get drafts on your own domain.

Add to Cowork

Ready to get started?

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