How a Founder Can Write, Publish & Email a Blog Post Without Leaving One Conversation

The problem with publishing a blog as a founder

You write the post. Then you switch to Webflow to create the CMS item, fill in the slug, excerpt, meta title, meta description. Then you open your email tool, stare at the blank campaign editor, write a subject line, try to summarise the post in 3 paragraphs, pick the right list, remember to assign a suppression group, and finally save the draft.

That's four different contexts, two platforms, and about 90 minutes of work that has nothing to do with the actual thinking you did when you wrote the post.

There's a better way. And it requires exactly two tools: Webflow for your site and Autosend for your email — connected to Claude via their MCP servers.

What is MCP and why does it matter here?

MCP (Model Context Protocol) is what allows Claude to directly talk to other tools — not just give you instructions on how to use them, but actually operate them on your behalf. Webflow and Autosend both have official MCP servers, which means Claude can create CMS items, publish blog posts, and set up email campaigns without you ever switching tabs.

Think of it as having an assistant who doesn't just advise you — they actually do the work in the tools you already use.

The flow: one conversation, two platforms, zero context switching

Here's exactly what happens when you set this up properly.

Step 1 — Write your rough draft, paste it into Claude

You don't need to write a polished post. Write your thinking. The core argument, the key points, maybe a rough intro. Paste it into Claude and ask it to review and polish the writing.

Why this step matters: Claude isn't replacing your thinking here — it's handling the editing pass that would normally take you another 30 minutes. It tightens the intro, fixes flow between sections, catches grammar issues, and improves clarity while keeping your voice. You review the output and approve it.

Step 2 — Generate all the publishing metadata in one go

Once the post is approved, ask Claude to generate the URL slug, SEO meta title (under 60 characters), meta description (under 155 characters), and a short excerpt for your blog listing page.

Why this step matters: These four fields get skipped or half-filled by almost every founder publishing their first 20 blog posts. They directly affect whether your post ranks on Google and how it looks in search results and social previews. Claude has the full context of the post and can generate all four accurately in seconds.

Step 3 — Claude creates a draft CMS item in Webflow

Claude calls the Webflow MCP and creates a draft blog post in your CMS collection — title, rich text body, slug, and excerpt all filled in correctly. It doesn't publish yet. The post sits in your Webflow CMS as a draft for you to review, add an image to, and approve before anything goes live.

Why this step matters: Creating a CMS item in Webflow manually means navigating to the collection, creating a new item, mapping every field, and saving. It's tedious and error-prone if you're rushing. Claude does it in one call and gets every field right because it generated the content itself.

Step 4 — Claude checks your Autosend account before touching anything

Before creating the campaign, Claude calls Autosend to fetch your available lists and segments, your verified senders, and your suppression groups. It checks when you last sent a campaign to your newsletter list.

Why this step matters: This is the safety check that most email tools skip. Sending twice in three days because you forgot you already sent something last Tuesday is one of the most common founder email mistakes. Claude surfaces this before creating anything, so you can decide whether to proceed or wait.

Step 5 — You pick a subject line from three options

Claude generates three subject line variants — one curiosity-driven, one benefit-led, one direct — and presents them for you to choose. You pick one, or ask for alternatives.

Why this step matters: The subject line is the single highest-leverage decision in the entire campaign. It determines whether 20% or 45% of your list opens the email. It deserves 60 seconds of conscious thought, not an afterthought typed into a field. Having three options makes the decision fast without making it careless.

Step 6 — Claude creates the Autosend campaign draft

With your subject line chosen, Claude creates the campaign draft in Autosend: HTML email body with a clear CTA linking to the blog post, plain-text version, suppression group assigned, sender set, list targeted. Everything is saved as a draft — nothing is sent.

Why this step matters: The suppression group assignment is the step almost everyone forgets when setting up campaigns manually. Without it, subscribers who've opted out of your newsletter category keep receiving emails, which drives complaints and damages your sender reputation. Claude assigns it automatically because it fetched your suppression groups in Step 4.

Step 7 — You say "publish both" and Claude handles it

One message. Claude publishes the Webflow draft to your live site, confirms the live URL, then verifies that the CTA link inside the Autosend campaign matches exactly. If there's a mismatch — say the slug changed — it catches it before anything goes out.

Why this step matters: Broken CTA links in email campaigns are embarrassing and unfixable once sent. The link check costs Claude zero extra effort and saves you from a reply-all of "hey your link is broken."

Step 8 — You hit Send in Autosend

This is the only step that happens outside the Claude conversation, and it's intentional. Everything going out to your subscribers should have one final human confirmation. You log into Autosend, see the campaign draft exactly as Claude set it up, and hit Send.

Why this step matters: AI doing the grunt work is the right call. AI deciding unilaterally to send to your entire list is not. This boundary — Claude prepares, you send — is what makes the flow trustworthy for a founder who's still building their audience and can't afford a bad email.

What you need to set this up

The one-time setup takes about 10 minutes. You need Claude Desktop installed, Webflow connected as a Connector via OAuth, and Autosend connected at https://mcp.autosend.com/ as a custom Connector. Both use OAuth — no API keys to manage. You also need a verified sender in Autosend and at least one suppression group set up (a "Newsletter" group is enough to start).

Why Autosend specifically

Most email tools at the early-stage price point don't have MCP servers. The ones that do — like Autosend — are the only ones where this entire flow is possible natively without workarounds. Beyond the MCP, Autosend charges by volume sent rather than by contacts stored, which means you can keep your full historical list without your bill growing just because your database does. For a founder who's still building, that's a meaningful difference.

The bottom line

Publishing a blog post and getting the email campaign out the door used to mean 90 minutes of context switching across two platforms. With Claude connected to Webflow and Autosend via MCP, it's one conversation, two drafts, one approval. The thinking is still yours. The execution is handled.