Canva

Canva is a browser-based design tool, and the part of it that belongs in an agent stack is the Canva MCP server: a remote Model Context Protocol endpoint that exposes design generation, editing, library search, asset and brand management, export and commenting as tools an assistant calls in natural language. Canva describes the capability set plainly, including "Design editing: Apply targeted modifications to existing designs through natural language commands".

The tool list is concrete rather than suggestive. generate-design and create-design produce designs, start-editing-transaction and commit-editing-transaction wrap an edit as a transaction, search-designs and get-design-content read the library, and get-export-formats leads to an export. Canva's own best practices page tells integrators to treat results as structured state, not text, and warns that "An edit is a transaction: open it, apply operations, then commit it."

There is no organization-level credential. Canva states that "Canva doesn't support organization level authentication. Each user must authenticate individually with Canva", and that "You can't set up a single 'service account' or application-level authentication that works for all users" (troubleshooting).

That shapes what a platform can build. Each end user needs their own Canva account and must complete an OAuth flow, and the operations available to them match their own permissions on a design or asset (access and permissions). Shared agents are governed explicitly: configuration may be shared, the token may not, and "Cross-user caching of design metadata, Brand Kit data, or prompts is prohibited" (usage policy). Clients also need to allow both canva.com and canva.ai, because the MCP server communicates over the two domains.

Canva splits MCP capability by plan. Design generation, editing, search, exports, comments and asset uploads are listed under "All plans", while "Design resizing to new dimensions, autofill, brand kits, and brand templates" require "Canva Pro and above" (access and permissions). The REST APIs enforce the same split through capabilities: a call made without the right capability fails with a 403 and a message naming what was required, for example Not allowed to access getResizeJob, requires one of capabilities ["resize"] (capabilities).

On top of the plan split sit per-tool ceilings, published as requests per minute. Reads are generally 100 a minute, generation and copying 20, asset upload 30 (tools and rate limits). Generation is also slow by design: Canva recommends a 60 second client timeout for generate-design.

Canva's usage policy states that "Canva's credit model applies to applicable MCP tools (e.g., generate-design)", that partners must surface credit usage in the interface or the tool response "where possible", and that "Apps must not mask or obscure credit consumption" (usage policy). A buyer integrating Canva into an assistant is therefore metering two things at once: the plan that permits the tool, and the credits each generation spends.

The credit allowances themselves, and the plan prices, are published on canva.com, which could not be read for this listing. Every request to the pricing page, the help center and the trust pages returned a Cloudflare human-verification challenge instead of the page, so no figure is quoted here and the price rows stay unanswered rather than guessed.

The reverse direction, other tools appearing inside Canva AI, is deliberately narrow. Canva says "AI Connectors are currently read-only, and let Canva AI pull in real content from a user's connected tools", naming Gmail, Notion and Google Calendar, with scope limited to "Read-only access only, text content only (no images or videos)".

It is also closed to outsiders for now: "We're not currently accepting submissions for connectors developed by third-parties. Right now, Canva builds and maintains all AI Connectors." Vendors who want their data inside Canva AI sooner are pointed at two app intents instead, the Data Connector for tabular data and the URL Expander for pulling content from a pasted link (connectors in Canva AI).

The fit is clear for teams whose brand assets already live in Canva: an assistant can draft a deck or a social post, apply an edit, and hand the user a link to finish the job in the editor, a handoff Canva documents as a required step in its design edit workflow. Building deeper, apps inside the Canva editor, needs engineering: Canva lists "Some knowledge of TypeScript and React" and Node.js among its prerequisites.

Two gaps matter for a procurement review. Canva's own compliance material, retention controls, data residency, single sign-on and any uptime commitment are published on canva.com and were unreadable from here, so this sheet reports them as blocked rather than absent. And the developer usage policy's training restriction, "Canva-sourced data, prompts, outputs, Brand Kit elements, or design structures must not be used to train, fine-tune, evaluate, or improve external AI models", binds the partner building on Canva, not Canva's own model training, so it is not evidence either way about a customer's opt-out.