Skip to main content
mcpFirst-partyLow risk Safety Privacy
Canva logo

Canva MCP Server for Claude

Browse, summarize, and generate Canva designs directly from Claude

HarnessClaude CodeCodexCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.canva.dev/docs/connect/canva-mcp-server-setup/, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/canva-mcp-server.mdx
Brand
Canva
Brand domain
canva.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/canva-mcp-server.mcpb
Package SHA256
461bfddb65f343a48e35a1dfcfbec79028101aebeebb217c5c0ed6dd55e48afe
Safety notes
Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.
Privacy notes
Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.
Author
Canva
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

4 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials4Configuration1Permissions & scopes1Network & hosting3General12 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: network access.

2 areas
  • SafetyGeneralLimit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.
  • PrivacyNetwork accessDesign contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.

Safety notes

  • Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.

Privacy notes

  • Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.

Prerequisites

  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Rate limit awareness: Design Export API (10 requests per 10 seconds), Native Element API (20 requests per 10 seconds)
  • Understanding of Canva design structure, templates, pages, and brand kits
  • Appropriate team permissions for design operations (read, write, create, export as needed)
  • Canva Developer Console access for managing OAuth applications and access tokens
  • OAuth scopes: design read/write access required for design operations

Schema details

Install type
package
Reading time
1 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
461bfddb65f343a48e35a1dfcfbec79028101aebeebb217c5c0ed6dd55e48afe
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "canva": {
    "url": "https://mcp.canva.com/mcp",
    "transport": "http"
  }
}

About this resource

Content

Create and manage Canva designs through Claude for automated design generation.

Features

  • Browse design templates and assets
  • Generate new designs programmatically
  • Summarize design content and elements
  • Autofill design elements with data
  • Manage brand kits and style guides
  • Advanced Canva design creation and management with template library access, brand kit integration, and collaborative design workflows
  • Batch operations support for efficient bulk design creation, updates, and asset management with automatic rate limit handling and retry logic
  • Real-time design synchronization capabilities with webhook integration support for monitoring design changes and triggering automated workflows

Use Cases

  • Generate social media graphics at scale
  • Create presentation slides automatically
  • Design marketing materials consistently
  • Produce brand assets variations
  • Maintain brand consistency across designs
  • Build automated design generation workflows that create branded content from templates for marketing campaigns and social media

Installation

Claude Code

  1. claude mcp add --transport http canva https://mcp.canva.com/mcp
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status canva

Claude Desktop

  1. Open Claude Desktop configuration file
  2. Add the Canva server configuration with HTTP transport
  3. Restart Claude Desktop
  4. Authenticate with your Canva account

Requirements

  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Rate limit awareness: Design Export API (10 requests per 10 seconds), Native Element API (20 requests per 10 seconds)
  • Understanding of Canva design structure, templates, pages, and brand kits
  • Appropriate team permissions for design operations (read, write, create, export as needed)
  • Canva Developer Console access for managing OAuth applications and access tokens
  • OAuth scopes: design read/write access required for design operations

Configuration

{
  "canva": {
    "url": "https://mcp.canva.com/mcp",
    "transport": "http"
  }
}

Examples

Create an Instagram post about our product launch

Common usage pattern for this MCP server

Ask Claude: "Create an Instagram post about our product launch"

Generate a presentation slide template

Common usage pattern for this MCP server

Ask Claude: "Generate a presentation slide template"

Export all logo variations

Common usage pattern for this MCP server

Ask Claude: "Export all logo variations"

Update brand colors in templates

Common usage pattern for this MCP server

Ask Claude: "Update brand colors in templates"

Create Design from Template

Create a new Canva design from a template with brand kit integration

// Create Canva design from template
const design = await canva.designs.create({
  templateId: "template-id",
  brandKitId: "brand-kit-id",
  title: "New Marketing Campaign",
  elements: [{ type: "text", content: "Hello World" }],
});

Security

  • OAuth authentication for account access
  • Respect brand guidelines and permissions
  • Manage team permissions appropriately
  • Regular asset backups recommended
  • Canva API tokens and OAuth access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • Canva OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • Canva design IDs and brand kit IDs may expose organizational design assets and brand information - ensure Canva resource IDs are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Canva MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Canva webhook configurations and payloads may contain sensitive design metadata and asset information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

Rate limit error when exporting designs

Design Export API allows 10 requests per 10 seconds. Wait for time window to reset before retrying. Implement request queuing with 1-second delays between exports to stay within limits.

Authentication fails with 401 signature verification error

Verify your OAuth 2.0 implementation ensures tokens refresh correctly. Check that access token hasn't expired and regenerate from Canva Developer Console if needed.

Cannot add elements to design - hitting rate limit

Native Element API allows 20 requests per 10 seconds. Batch element additions where possible and add 500ms delays between individual add operations to avoid throttling.

Designs not accessible or permission denied errors

Verify your Canva Pro subscription is active and your account has proper team permissions. Check OAuth scope includes design read/write access and re-authenticate if necessary.

Canva MCP server authentication errors with OAuth tokens

Verify OAuth token is valid and not expired. Check token scopes match required permissions. Ensure token format is correct (Bearer token in Authorization header). Implement automatic token refresh logic for long-running operations.

Canva design creation or update failures

Check design size limits and template availability. Verify brand kit permissions allow design creation. Ensure network connectivity is stable. For large designs, use chunked upload API with resumable upload support.

Canva MCP server rate limiting or throttling errors

Implement exponential backoff retry logic with jitter. Use Canva API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed design metadata. Request rate limit increases from Canva support if needed.

Canva MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Canva API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Canva MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/canva-mcp-server.svg)](https://heyclau.de/entry/mcp/canva-mcp-server)

How it compares

Canva MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field

Browse, summarize, and generate Canva designs directly from Claude

Open dossier

Connect to nearly 8,000 apps through Zapier's automation platform

Open dossier

Interact with Asana workspaces to manage projects and tasks

Open dossier

Task management and project tracking with ClickUp integration

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow risk
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandCanva logoCanvaZapier logoZapierAsana logoAsanaClickUp logoClickUp
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorCanvaZapierAsanahauptsacheNet
Added2025-09-182025-09-182025-09-182025-09-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesLimit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.Restrict the generated Zapier MCP URL and enabled actions because automations can write across many connected apps.Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.Scope the ClickUp API key to the intended team and review task, status, or project mutations before using it on active workspaces.
Privacy notesDesign contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.Connected app data, workflow payloads, account metadata, and action inputs or outputs may be sent through model context.Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.Tasks, comments, custom fields, assignees, due dates, and workspace metadata may be exposed through tool calls.
Prerequisites
  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • Zapier account (free or paid plan)
  • Personal authentication token (generated at mcp.zapier.com)
  • Network access to mcp.zapier.com (HTTPS required, HTTP transport)
  • Understanding of Zapier Zaps/workflows (automation concepts)
  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • ClickUp account with workspace access
  • ClickUp Personal API Token from https://app.clickup.com/settings/apps
  • ClickUp Team ID (found in ClickUp workspace settings)
  • Node.js and npm/npx available for running the @hauptsache.net/clickup-mcp package
Install
claude mcp list && claude mcp status canva
claude mcp add --transport http zapier YOUR_GENERATED_URL && claude mcp list
claude mcp list && claude mcp status asana
claude mcp add clickup --env CLICKUP_API_KEY=YOUR_KEY --env CLICKUP_TEAM_ID=YOUR_TEAM_ID -- npx -y @hauptsache.net/clickup-mcp && claude mcp list
Config
{
  "mcpServers": {
    "canva": {
      "url": "https://mcp.canva.com/mcp",
      "type": "http"
    }
  }
}
Manual-only setup:
{
  "zapier": {
    "url": "https://mcp.zapier.com/YOUR_GENERATED_URL",
    "transport": "http"
  }
}
{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "clickup": {
      "env": {
        "CLICKUP_API_KEY": "${CLICKUP_API_KEY}",
        "CLICKUP_TEAM_ID": "${CLICKUP_TEAM_ID}"
      },
      "args": [
        "-y",
        "@hauptsache.net/clickup-mcp"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.