Canva’s New MCP Tools Put a Review Step Between Brief and Asset
A brief can be clear, approved and ready to go—and still spend half a day being translated into the right set of assets. Canva’s new MCP tools aim to shorten that trip. Announced September 28, 2026, they let connected workflows create designs and generate or modify images programmatically.
That may help agencies move faster from a request to a first pass. It doesn’t make that first pass final. The useful question is where creative review and client approval stay in the process, especially when a tool can make the production steps feel almost too easy.
From brief to editable design
MCP is a way for an AI assistant or another connected workflow to call tools and carry out tasks in a service. In practical terms, a workflow could take details from a brief and call a design tool, rather than leaving someone to copy the request into a separate interface and start from scratch.
Canva’s new create-design tool generates an editable design using updated models. It replaces the earlier generate-design tool. Canva also introduced get-create-design-async-job, which checks on a design job that’s still underway. That distinction matters for a workflow: a request may start now, while the finished design arrives later.
For an agency, the draw isn’t simply that a design can be made by a tool call. It’s that a brief might lead more directly to a starting layout a designer can open and change. A campaign request, for example, could become a first-pass design for a particular format. The designer would still need to check what the workflow produced, make it fit the brief and decide what deserves to survive into the next round.
Editable is a useful word here, but it shouldn’t be mistaken for approved. A design that can be changed is a workable starting point—not evidence that the hierarchy, copy or brand decisions are right. Automation can get the file onto the table. It can’t know whether the table is the right one.
What the image tools do
The announcement also adds tools for image creation and cleanup. generate-image makes a flat image for a creative workflow, and get-generate-image-job checks on image generation that’s in progress. The result is an image asset, not the same thing as an editable, composed design.
Two other tools reshape an existing image. remove-background removes its background. separate-image-layers splits an image into editable layers, with get-separate-image-layers-job available to check on that operation while it runs.
Those outputs offer different kinds of control. A flat image may be ready to place in a layout, but it doesn’t give a designer separate pieces to adjust. A layered result offers more room to reposition or edit parts. An editable design goes further still by putting the image into a broader composition. That range can help a team choose the right output for the task, rather than treating every generated asset as if it came with the same options.
It also gives reviewers different things to inspect. A generated image needs a check for subject, crop and fit. A removed background needs a close look at the edges. Layers may need checking for missing details or awkward separations. A design needs its own review for layout, message and format. “The tool finished” is a status update, not a quality check.
Where to put the review gate
A sensible agency workflow starts before any tool call: with a brief the team has agreed on. That brief should set the purpose, audience, message, brand constraints and required formats. If the input is vague, the output may be polished and wrong—a particularly efficient way to create more work.
From there, a connected workflow can prepare a first pass: a design, an image, a background-removed asset or a layered version. Then a designer reviews it before it goes anywhere external. That review can cover the layout, copy, image choice, brand fit, technical details and the requested deliverables. The designer can revise the output, discard it or use only the parts that help.
Client review belongs after that internal check and before delivery or publication. The client should still see the version the agency is actually proposing, with the chance to request changes or approve it. Automation may prepare options; it shouldn’t quietly turn “generated” into “signed off.”
A small, low-risk task is a good way for an agency to assess the fit. A team might try one routine format or a simple image-preparation step and note where the workflow saves effort—and where people still need to intervene. That reveals more than a grand pilot that tries to automate an entire campaign at once. Creative judgment tends to get less mysterious when it’s tested on a real task.
What’s still unclear
Canva says it plans to add more examples to the documentation over the coming days and weeks, and improve onboarding over the next couple of weeks. For now, its announcement introduces the tools but doesn’t spell out account requirements or describe review and approval features inside them.
That leaves practical questions for teams to answer before they build around the tools: which accounts can use them, how a team sets up its connected workflow, and what the resulting review process looks like in practice. The announcement doesn’t establish that Canva’s tools provide an in-tool client approval step, so agencies shouldn’t assume they do.
The tools offer a way to move from a brief toward editable designs and prepared image assets through connected workflows. For agencies, the more useful measure won’t be how little human input remains. It’ll be whether the workflow removes repetitive setup while keeping creative review and client sign-off exactly where they belong.