The short version
- Two connectors: Canva for the artwork, Mailchimp for the send.
- Add both in Claude, sign in to each once.
- Brief the campaign, let Claude design and draft it, then approve before it ships.
Why Claude + Canva + Mailchimp is the stack that closes the gap
Most email stacks have a hole right in the middle. You can write the copy in one place and send it from another, but the visuals (the hero image, the product graphic, the on-brand banner) live in a separate tool and a separate head. Someone briefs a designer, waits, drops the export into the email tool, and re-checks it on every screen size. That handoff is where campaigns slow down and where "on-brand" quietly slips.
This workflow closes that gap. With the Canva MCP server, Claude can actually design (generate an on-brand graphic, resize it for email and social, and export it) and then turn around and build the Mailchimp campaign with that exact asset. One brief produces the picture and the prose, sized and assembled, instead of a copy doc on one side and a design request on the other.
The piece that makes it safe is a place to look before anything ships. Plainpaper is the board in the middle: each Canva export and the assembled Mailchimp campaign land as typed cards you can see side by side (the hero next to the subject line next to the audience) and approve. The agent does the design and the assembly; you decide what's good enough to send.
What each tool does in this workflow
Four tools, four clear lanes. The workflow is strongest when each one does the job it's best at and hands off cleanly to the next.
The workflow, end to end
Six stages that run from one chat window: Claude designs in Canva, writes and assembles in Mailchimp, and puts every step on the board as it goes.
Claude · Spring edit board
canva · create_design
canva · export_design
mailchimp · create_campaign
Put the hero and the draft campaign on the board for review.
What you'd see: Claude calls Canva to design and export, then Mailchimp to assemble, and drops it all on the board. Nothing is sent yet.
How to connect Mailchimp to Claude
The two halves of this stack do not connect the same way, and it is worth
knowing that before you sit down to wire it up. Canva runs an official
remote MCP server: you point your Claude client at
mcp.canva.com, log in to Canva, done. Mailchimp has no
equivalent for the Marketing API, which is the half that holds your
audiences and campaigns. Its one official MCP server covers Mailchimp
Transactional (Mandrill), the service that sends receipts and password
resets, and it cannot build a campaign. So Mailchimp takes one of these
routes instead, and the first three all end up calling the same Marketing
API.
| Route | What you get | What it asks of you |
|---|---|---|
| A community MCP server Marketing API, runs on your machine | The full campaign surface as tools: create the draft, set the HTML, send a test, schedule, plus audiences, segments, and reports. | You install it and hand it a Mailchimp API key. Nobody at Mailchimp reviews these. |
| A hosted connector Zapier MCP and similar | A smaller set of actions wired to your Mailchimp login, including create campaign, send campaign, and subscriber management. | Nothing to install, but a narrower surface than the API and one more vendor holding the connection. |
| The Marketing API itself straight from Claude Code | Every endpoint Mailchimp publishes, with no MCP server in the middle. Claude Code calls the REST API with the tools it already has. | You work in a terminal, and the key lives in your environment. |
| Mailchimp Transactional MCP the official one | About nine tools at mandrillapp.com/mcp for transactional sending, templates, and delivery troubleshooting. |
Worth knowing it exists so you don't reach for it here. It cannot create or send a marketing campaign. |
Doing it in Claude Code
Claude Code takes both halves. Canva goes on as a remote server, and Mailchimp goes on as a local one that picks its key up from the environment:
claude mcp add --transport http canva https://mcp.canva.com/mcp claude mcp add --env MAILCHIMP_API_KEY=abc123-us8 \ --transport stdio mailchimp -- uvx mailchimp-mcp
That second command runs mailchimp-mcp, one of several
community servers on the MCP registries. Read what a server does before you
give it a key, and prefer the ones that ship a read-only and a dry-run
mode.
You can also skip the Mailchimp server entirely. The Marketing API is plain
REST with basic auth, so Claude Code can call it directly. The data center
suffix on your key (the us8 in abc123-us8) is the
subdomain you talk to:
curl --url 'https://us8.api.mailchimp.com/3.0/campaigns' \ --user "anystring:$MAILCHIMP_API_KEY"
A campaign is three calls: POST /campaigns for the draft with
its audience and subject line, PUT /campaigns/{id}/content for
the HTML that carries your Canva hero, and
POST /campaigns/{id}/actions/schedule once you have approved
it.
About that key. A Mailchimp API key carries everything the login that created it can do. There are no scopes and no per-tool limits, so treat it like a password: generate it under Account, Extras, API keys, keep it out of shared chats, and delete it when you stop using it. If your server offers read-only or dry-run mode, run the first week with both on.
Step by step: from brief to a sent campaign
Connect Claude to Canva, Mailchimp, and a board
Everything runs over MCP. Two of the three connect the same easy way:
the Canva MCP server (the remote server at mcp.canva.com,
which prompts you to log in to Canva) and a Plainpaper board. Mailchimp
takes one of the routes above, so pick that first. Once all three are
wired up, one conversation can design a graphic, write an email, and
put both somewhere you can approve them.
Plan note. Design, editing, search, and export work on every Canva plan. Resizing to new dimensions needs Canva Pro or above; brand kits, brand templates, and autofill are Enterprise features. That's what lets Claude apply your colours, fonts, and logo automatically.
Brief Claude like a designer and a marketer at once
The brief carries further here because it drives both the picture and the prose. Give Claude the goal, the offer, the audience, and the look: the season, the mood, the hero product. The more it knows, the closer the first design lands to something you'd actually send.
We're launching the spring edit to engaged subscribers. Warm, fresh, product-forward. Brief the campaign on the board: goal, the hero product, the angle, and the one thing the email has to do.
Design the visuals in Canva
Now the part that used to be a handoff. Ask Claude to generate the email hero and supporting graphics in Canva from your brand template, resize them for the email and a matching social post, and export them. Each export lands on the board as a Creative card you can actually look at, not a link to chase down later.
Design the email hero in Canva from our brand template, featuring the spring edit. Make a 600px email version and a 1080×1350 Instagram version, export both as PNG, and add each as a Creative card linked to this campaign.
Write the copy and assemble the Mailchimp campaign
With the visuals approved, Claude writes the Mailchimp copy (subject lines, preview text, body) and assembles the campaign with the hero in place, pointed at the right audience. The result is a finished campaign card on the board, not a to-do list of pieces to wire together by hand.
Where the image lives. Canva's export links are only valid for 24 hours, so an email pointing straight at one shows a broken image by next week. Have the export uploaded to Mailchimp's content studio (or held on the board) and referenced from there, so the campaign keeps its own copy.
Build the Mailchimp campaign for engaged subscribers using the approved hero. Two subject lines, short warm body, one clear CTA to the spring edit. Put it on the board as an Email card.
Approve on the board: visuals and copy together
This is the step the handoff used to skip. The hero, the subject line, the body, and the audience sit on one canvas, so you judge them as the reader will see them, together. Tweak the copy or ask for another design pass in plain language, then approve. Only approved cards ship.
The agent can design ten heroes and write the campaign around each in a minute. The board is where one person decides which one is on brand and ready to send.
Send, then pull the results back
Once approved, Claude schedules the send in Mailchimp and later pulls opens, clicks, and conversions back to the board as Result cards. The next campaign starts from "the product-led hero beat the lifestyle one" instead of a blank brief, with design learnings and copy learnings in the same place.
The visuals to generate first
Start with the graphics that carry a campaign and get reused the most. They have the clearest brief and the biggest payoff from being on brand and correctly sized, which makes them the perfect first job for the agent.
- Email hero: the banner at the top of the campaign. Claude builds it from your brand template and sizes it for email width.
- Product feature graphics: clean, on-brand shots of the hero product, generated to match the email's angle.
- Promo & sale graphics: the discount badge or seasonal frame, consistent across every send in a campaign.
- Newsletter section headers: small, repeatable dividers that make a long email scan well.
- Matching social posts: the same design resized to Instagram or story dimensions, so the campaign looks of-a-piece across channels.
How this compares to Canva Magic, Mailchimp AI, and a chatbot
Each tool's built-in AI is good inside its own walls. None of them spans the design-to-send gap or keeps a human approving in the middle.
| Approach | What it's good at | Where it falls short |
|---|---|---|
| Chatbot + manual Canva copy/paste into Mailchimp | Fast copy and ideas; you design and assemble by hand. | The design handoff is still manual, assets scatter, and nothing remembers the campaign. |
| Canva Magic & Mailchimp AI | Strong help inside each tool: generate a design, polish a subject line. | Neither crosses the gap: Canva doesn't build your campaign, Mailchimp doesn't design your hero. |
| Claude + Canva + Mailchimp + Plainpaper | Designs on-brand, writes, and assembles end to end, with lineage and approval. | You set the brief and approve, exactly as intended. |
Pitfalls to avoid
- Letting the agent send. Keep the Mailchimp send behind board approval. An agent that designs and drafts is an asset; one that ships unreviewed is a liability.
- Skipping the brand setup. Without brand templates and a brand kit, Canva designs come out generic. Set those up so "on brand" is automatic, not a correction.
- Forgetting the second size. Always ask for the email and the social size in one go. Re-cropping later is where consistency slips.
- One giant prompt. Brief, then design, then assemble, so each visual and the campaign are reviewable instead of a wall of output.
Key takeaways
- Connect Claude to the Canva MCP server, Mailchimp, and a Plainpaper board over MCP.
- Claude can actually design (generate, resize, and export on-brand visuals in Canva), then assemble the Mailchimp campaign around them.
- Brand templates, brand kits, and autofill (Canva Enterprise) are what make every design land on brand automatically.
- Approve the visuals and the campaign together on the board. The agent designs and drafts; you decide what ships.
- Pull results back so design and copy learnings compound into the next campaign.
Frequently asked questions
Can Claude design in Canva?
Yes. Connected to the Canva MCP server, Claude can generate and edit designs, resize them across formats, search your workspace, and export them as PNG, JPG, PDF, PPTX, or MP4. It works from a plain-language brief and lands the exported visuals on the board for approval before they go anywhere.
Will Claude use my brand kit and templates?
Yes, on the plans that expose them. Canva's brand kits, brand templates, and autofill are available on Canva Enterprise, so Claude can apply your colours, fonts, and logo and fill a template with the right content. A single brief can produce an on-brand hero, banner, and matching social post. Core design, editing, search, and export work on every plan; resizing needs Canva Pro or above.
Can Claude put the Canva designs into a Mailchimp campaign?
Yes. Once the visuals are exported and approved on the board, Claude writes the Mailchimp copy and assembles the campaign with those assets: subject lines, preview text, body, and the images in place. You approve the finished campaign on the board, then Claude schedules the send in Mailchimp.
What Canva plan do I need?
Design generation, editing, search, comments, asset uploads, and exports work on every Canva plan. Resizing a design to new dimensions needs Canva Pro or above. Autofilling brand templates with your content, brand kits, and brand templates are Enterprise features.
Is there an official Mailchimp MCP server?
Not for the Marketing API. Canva runs an official remote MCP server, so that half is a login. Mailchimp's one official MCP server covers Mailchimp Transactional (Mandrill), the service behind receipts and password resets, and it cannot build a campaign. Campaigns and audiences live in the Marketing API, which you reach from Claude through a community MCP server, a hosted connector such as Zapier, or a direct call to the API itself.
Does this work in Claude Code?
Yes. Canva goes on with claude mcp add --transport http canva
https://mcp.canva.com/mcp, and Mailchimp goes on either as a local
MCP server holding your API key or as direct calls to the Marketing API,
which is plain REST with basic auth. Either way Claude Code reaches the
endpoints that create the draft, set its content, and schedule the send.
Will Claude send the campaign without my approval?
No. The workflow is built so the agent only ever drafts. Every Canva visual and the assembled Mailchimp campaign land on the board with the brief and audience that shaped them, and you approve there. Only then does Claude schedule or push the send.
Do I need to know how to write prompts?
Not really. You brief Claude the way you'd brief a designer and a marketer (the goal, the offer, the audience, the look) and steer from there. The board shows you exactly what it produced, so you correct in plain language instead of re-engineering a prompt.
Next step: give the workflow a home
You have the workflow that spans design and send. The piece that makes it safe and repeatable is the board in the middle, where the agent's visuals and campaigns become visible, linked, and approvable. Plainpaper is free to try and connects to your Claude client over MCP in a couple of minutes. Your next campaign can be designed, written, and assembled in one pass.
Keep reading
- Canva MCP server setup guide: the 33 tools, the two-click setup, and the free-versus-Pro gates for brand work.
- Content calendar playbook: pillars with jobs and a month of slots filled with finished, approved posts.
- Ecommerce campaign playbook: the board where the visuals and the emails they belong to live side by side.
- AI image tools for marketing visuals: how Canva scores against Ideogram, Recraft, Pixelcut and Adobe Express.
- Free stock photos for your agent: the photography half, with no API key and no MCP server needed.
- Assets and media in Plainpaper: private storage, asset references, and the placeholder slots that block approval.
- Claude + Mailchimp on its own: the same send workflow without the design layer.