Shipping a Content Calendar with Claude and MCP

Most solo creators and small teams hit the same wall: they have ideas, but the work of turning each idea into platform-specific posts is the part that quietly eats Sunday afternoons. The Pub Studio MCP server flips that around. Hand Claude a brief, and Claude drafts the calendar, the variants, and the schedule itself.

The shape of the workflow

The flow is simple once you've wired it up:

You write a short brief in your own words. "Five posts about our new pricing page, friendly tone, one of them a thread."
Claude calls the Pub Studio MCP tools to fetch your brand voice, recent posts, and the connected channels.
Claude proposes a draft calendar with platform-specific copy for each slot.
You review in Pub Studio's UI like any other scheduled post.

Nothing is auto-published. Claude is the drafter, Pub Studio is the scheduler, and you are the editor.

Why MCP and not a chat box

A chat box can produce a great post in isolation. The hard part is getting a post that fits your voice, references your product, and slots into a calendar that already has eight things in it for next week.

MCP gives Claude structured access to your existing context — past posts, brand voice notes, audience tags, scheduled queue. The drafts come back already aware of what's around them.

What's worth setting up

A few things make the workflow much smoother:

Voice notes: a short doc Claude can read describing tone, common phrases, things you never say.
Channel rules: per-channel constraints like character limits, hashtag policy, and whether links are allowed.
Audience map: which segments live on which platform.

None of this is required to start. But every piece you add makes the next draft sharper.

What's next

We'll cover MCP server configuration in a follow-up post. For now: connect Claude to Pub Studio, ship a week's worth of drafts in an afternoon, and keep your Sunday.