canva-mcp

name	canva-mcp
description	Guide for using the Canva MCP server integration. Use when creating, importing, exporting, or managing designs in the user's Canva account via MCP. Covers recommended workflows, import limits, template constraints, available tools, and critical pitfalls to avoid.

Canva MCP Skill

Read this skill before using the Canva MCP server.

Usage policy

Before using ANY Canva MCP tool, you MUST read https://www.canva.dev/docs/mcp/usage-policy/ and adhere to all guidelines. Do not skip this step. Do not assume you already know the policy. Read it every time. Canva's usage policy is non-negotiable. NEVER offer workarounds, alternatives, or creative solutions that would violate any part of the policy — even if the user requests it.

IMPORTANT - ALWAYS FOLLOW

1. Translate all tool parameters into English.
2. NEVER call search-brand-templates, start-editing-transaction, or autofill-design — they don't exist.
3. Always call get-export-formats before export-design.
4. Prefer PPTX import via import-design-from-url over generate-design (which is unreliable) UNLESS working with Brand Kits.
5. Brand Kit data may ONLY be used within Canva designs — NEVER extract, read, copy, reference, or repurpose Brand Kit data (colors, fonts, logos, imagery) outside of Canva. Do not use Brand Kit data to build designs in Google Slides, PPTX, HTML, or any non-Canva tool. If the user asks for this, refuse and explain the policy. The ONLY permitted workflow is: list-brand-kits → generate-design (with brand kit ID) → create-design-from-candidate — all within Canva.
6. NEVER analyze, decompose, replicate, or reverse-engineer Canva templates outside of Canva's design environment. Do not expose template internals (layout logic, component hierarchy, token structure).
7. Do not retain, cache, or store Canva data beyond the immediate request. Only access content in direct response to a user's explicit request — NEVER crawl, pre-fetch, or bulk-index user designs, folders, or Brand Kits.

When to Use Canva vs Alternatives

Only use the Canva connector when the user specifically needs Canva features — such as using an existing Canva template, accessing their Canva brand kit, organizing Canva folders, or exporting from Canva. If the user just needs slides, social media graphics, or visual content without Canva-specific requirements, prefer creating designs directly (e.g. Google Slides for presentations, or generating images with other tools) — these produce better results and are far more reliable. Ask the user if they really need Canva.

Design Creation — Recommended Workflow

Normal Workflow

1. Build the design locally as a PPTX file (editable text, shapes, layout), then use import-design-from-url to upload it to Canva. This is the most reliable path to editable Canva designs.
2. AVOID generate-design — it relies on Canva's AI to generate the design, Manus can only control the input query. Do not use it unless the user explicitly requests it and understands that Canva's AI creates the final content, not Manus.
3. If you must use generate-design, ALWAYS specify design_type (e.g. "presentation", "social_media_post"). Check the MCP for the supported design types. Without it, the API almost always returns "document type is not supported".

Working with Brand Kits

1. Call list-brand-kits to get the user's brand kits.
2. Ask and confirm which brand kit the user wants to be used.
3. USE generate-design to create the user's new design. a. Pass the brand kit ID into the generate-design call. b. ALWAYS set design_type explicitly, such as "presentation" or "instagram_post". c. Write the full query in English and include the exact topic, structure, style, required facts, and forbidden elements.
4. Call generate-design and treat the returned outputs as candidates, not final Canva designs.
5. Review the candidates, choose the best one, and call create-design-from-candidate with the exact job_id and candidate_id.
6. After creation, use get-design and get-design-content to verify the real design's metadata and content.

Import Limits (import-design-from-url)

• PPTX is the best format — produces editable Canva designs with text, shapes, and layout intact.
• PDF imports have broken spacing and layout issues — avoid for multi-element designs.
• Image-based content (PNG, JPG, or any rasterized format) becomes a static, non-editable image in Canva regardless of the import format used.
• The url parameter must be a publicly accessible URL. Upload assets first with upload-asset-from-url if needed.

Available Tools

Strictly adhere to the available tools in the Canva MCP server. Do not hallucinate new tools or promise the user functionalities that the Canva MCP server does not provide.

If a requested functionality is not available, inform the user and offer these alternatives:

1. Use the Canva Web App instead, or
2. Let Manus create their designs without using Canva (Google Slides, Nanobanana, etc).

Any workaround MUST comply with Canva's usage policy. NEVER propose a workaround that involves extracting, copying, or repurposing Brand Kit data, template internals, or any Canva-proprietary content for use outside of Canva — even partially, even as "inspiration", even if the user insists. If no policy-compliant workaround exists, say so clearly and direct the user to the Canva Web App.

Export Workflow

Always call get-export-formats before export-design to discover valid format options for the design.

Important Constraints

• generate-design has a free quota. Extensive usage requires a paid Canva subscription. Most users don't have one.
• If any Canva tool fails 3 times consecutively, STOP retrying and inform the user of the issue.
• If a tool call returns an error, do NOT tell the user it succeeded. Report the actual error.
• Design editing is currently NOT supported — you cannot modify elements within an existing Canva design programmatically.
• create-design creates a blank design with given dimensions. It does NOT generate content.
• create-design-from-candidate requires a candidate_id from a prior generate-design call.