Verify your Canva MCP integration

MCP Inspector⁠(opens in a new tab or window) is a browser-based MCP client for connecting to a server, listing tools, and inspecting raw requests and responses. Use it as a known-good reference: if Inspector returns the expected result and your app doesn't, the fault is in your integration. If Inspector fails too, it's upstream.

• An AI application integrating the Canva MCP.
• An MCP client registered with Canva, authenticated using OAuth.
• The Canva MCP server URL: https://mcp.canva.com/mcp.

List tools from your client rather than assuming a fixed set.

1. Start MCP Inspector (requires Node.js v22.7.5 or later):

   npx @modelcontextprotocol/inspector@latest

   SHELL

   Copy

2. Set Transport to Streamable HTTP, enter https://mcp.canva.com/mcp, select Connect, and sign in to Canva.

3. Open Tools, then select List Tools.

   

4. Call a read tool such as search-designs. Confirm it succeeds and returns the expected response. Compare the response with the same call from MCP Inspector.

   

If a step fails, see Troubleshooting.

If your AI application behaves differently from MCP Inspector, use Inspector as your known-good reference implementation. Reproduce the same tool call in Inspector with the same arguments, then compare the raw request and response. This will help you determine whether the issue is in your integration or upstream.

• Inspector succeeds, your app fails → The issue is likely in your integration (request formatting, response parsing, or job vs direct response handling).
• Inspector and your app fail in the same way → The issue is likely upstream. Check error.code on the job object when present.
• Responses differ → Compare field names carefully. For example:
  • Use id rather than design_id.
  • Download links are returned in urls[] not download_url.
  • Editable element_ids come from start-editing-transaction, not get-design-content.
  • The job identifier is job.id.
• URLs don't load → Export and media.canva.com URLs are signed and expire (see export-design and get-design-pages). design.canva.ai thumbnails may need redirects resolved before rendering in an <img> (see generate-design).

Compare your application’s responses against the documented example responses for each tool. Confirm the response structure, required fields, and any asynchronous job handling match the documentation.

• search-designs
• get-design-content
• get-design-pages

• generate-design
• create-design-from-candidate

Open a transaction → apply operations → commit. Edits stay in draft until commit.

• start-editing-transaction
• perform-editing-operations
• commit-editing-transaction

• upload-asset-from-url
• export-design

• Invalid input fails cleanly (no hang/crash).
• Full round-trip: create → open → edit → commit → export; export reflects the commit.
• Per-user isolation: credentials can't access another user's designs.

Send the following prompts to your AI application and confirm it selects the expected Canva tool. Repeat these checks after changing prompts, system instructions, or tool descriptions.

Also confirm edit routes to perform-editing-operations (not regenerate), and create routes to Canva when other servers are connected (see Step 5).

Test complete workflows rather than individual tools. Many integration issues only appear when chaining multiple tools together and passing data between them.

Read before targeted edit. "Show me the copy on this design, then change only the subheading."

get-design-content → start-editing-transaction → perform-editing-operations → commit-editing-transaction.

get-design-content has no editable element_ids — those come from the transaction.

Upload an asset, then place it. "Add this logo to the design: https://<public-image-url>"

upload-asset-from-url → start-editing-transaction → perform-editing-operations with the returned asset_id (update_fill / insert_fill).

Don't pass the raw URL into the edit. If upload-asset-from-url returns fetch_failed, confirm the URL is public HTTPS and returns 200, then retry before continuing without an asset_id.

Create, then generate an image for it. "Create a launch poster, then add an AI-generated background image."

Create should call Canva generate-design; the image step is where models often divert to built-in image gen (see Step 5).

With multiple MCP servers connected, design prompts may never reach Canva if another tool looks similar (including native image generation).

Connect Canva alongside another server, send ambiguous prompts, and confirm Canva is called:

If Canva loses the call:

• System-prompt guidance / explicit "in Canva" phrasing.
• Pin or force the tool when the client supports it.
• Reduce overlapping tools in context.
• Ask the user which server to use when it's ambiguous.

• Auto-selecting a generated candidate instead of requiring a user choice.
• Fabricating a candidate_id or transaction_id.
• Reporting an edit as saved before commit-editing-transaction.
• Passing a raw image URL into an edit — upload first for an asset_id.

After the manual checks are stable, script them into CI: tool list, one call per tool, error cases, and the prompt library. Postman (MCP requests) and MCPJam (tool-selection evals) are common options.

• Expected tool missing: Client may not expose it — check Step 1.
• Auth fails: Token expired; redirect URI not registered; Inspector CLI can't do interactive sign-in (use the UI or mcp-remote).
• Tool error: Args vs input schema — usually a missing field or wrong type.
• upload-asset-from-url → fetch_failed: URL must be public HTTPS.
• Wrong server called: See Step 5.
• Edits didn't persist: Commit required. Concurrent browser edits can stale the transaction — cancel, start fresh, re-apply, commit.
• Fails in Inspector too: Likely upstream — check the Canva status page⁠(opens in a new tab or window) (Connect API).

• Per-user OAuth; users only access their own designs.
• Signed thumbnail/export/download URLs are short-lived — don't store or share them.
• Uploads and generated designs land in the authenticated user's account.

• Canva Model Context Protocol (MCP)
• MCP tools and rate limits
• Troubleshooting and common questions
• Design edit handoff