Design MCP Servers Compared (2026): Figma, Canva, Webflow, Wix, Miro, Cloudinary

• Figma: hosted at https://mcp.figma.com/mcp, or a desktop server at http://127.0.0.1:3845/mcp. Reads design context, variables, screenshots and Code Connect maps; use_figma and other write tools edit files. Sign in with your Figma account. Starter (free): 20 tool calls a month. Professional Full or Dev seat: 200 calls a day.
• Canva: hosted, OAuth per user, added in Claude from the connectors list. Generate, edit, search, comment on and export designs. Most tools work on all plans, including Free. Resize, autofill, brand kits and brand templates need Pro or above (Pro is US$144 a year).
• Webflow: hosted at https://mcp.webflow.com/mcp with OAuth, or local npx webflow-mcp-server@latest with WEBFLOW_TOKEN. Edits pages, elements, styles, components and the CMS. A few tools need the Designer open with the MCP Bridge App. Webflow's pricing page lists the MCP server on the free Starter site plan.
• Wix: hosted at https://mcp.wix.com/mcp; signs in through your Wix account, or an API key plus account ID. Creates, updates and publishes sites, and calls site APIs such as Stores, Bookings and CMS. The MCP docs list no plan requirement.
• Miro: hosted at https://mcp.miro.com with OAuth 2.1. Reads boards as SVG, creates and updates board items, diagrams, prototypes and comments. All plans: Free 100 calls a day, Starter 500, Business 2,000, Enterprise 10,000.
• Cloudinary: several hosted servers (Asset Management, Environment Config, Structured Metadata, Analysis, MediaFlows) with OAuth or API keys, plus local npx packages. Upload, search, manage and transform media. Free plan: 25 monthly credits, no card. Plus: $99 a month billed monthly.
• Prices, limits and tool lists were checked on each vendor's docs and pricing pages on 2026-10-23 and change often.

Figma's MCP server gives the agent design context from a Figma file so it can write code that matches. Figma recommends the remote server, which connects to Figma's hosted endpoint and does not need the desktop app. The desktop server runs locally through the Figma desktop app and needs a Dev or Full seat on a paid plan. You sign in with your Figma account the first time you connect. Figma's docs say only clients in its MCP catalog can connect.

claude plugin install figma@claude-plugins-official

claude mcp add --scope user --transport http figma https://mcp.figma.com/mcp

{
  "mcpServers": {
    "figma": {
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp

• Read tools: get_design_context, get_variable_defs, get_screenshot, get_metadata, get_code_connect_map, search_design_system (remote only), download_assets (remote only), get_figjam.
• Write tools (remote only unless noted): use_figma creates, edits and inspects content in Figma files; also create_new_file, generate_diagram, generate_figma_design, html_to_figma, upload_assets, and add_code_connect_map (both servers).
• Writing to the canvas needs the remote server and a Full seat to write outside your drafts. Figma says it is free during the beta and will become a usage-based paid feature.
• Limits: Starter, and View or Collab seats on any plan, get 20 tool calls a month. Professional Full or Dev seats get 200 a day and 10 a minute; Organization 200 a day and 15 a minute; Enterprise 600 a day and 20 a minute.
• Price: Professional lists a Dev seat at $12/mo and a Full seat at $16/mo.
• Desktop server: open a Design file, switch to Dev Mode with nothing selected, and click Enable desktop MCP server in the right sidebar.

• Figma MCP server: install for every agent

Canva's MCP server is hosted by Canva and lets the agent create, edit, search and export designs in your Canva account. Each user signs in with OAuth; Canva does not support one shared login for a whole organization. In Claude, add Canva from Settings, Connectors. Canva's docs we checked do not publish a server URL for manual setup.

• Main tools: generate-design, create-design, search-designs, get-design-content, start-editing-transaction, perform-editing-operations, commit-editing-transaction, export-design, upload-asset-from-url, comment-on-design, resize-design, autofill-design.
• Plans: most tools are on all plans, including Free. resize-design, autofill-design, brand kits and brand templates are Pro and above. Free users get a limited trial of resize-design.
• Export works on all plans, but the plan affects output quality, and designs with premium elements can fail with license_required.
• Rate limit: 300 requests a minute per user across all MCP clients, with lower limits on some tools (for example generate-design at 20 a minute).
• Gotcha: Canva's Help Center pages give different plan rules for autofill than the developer tools table (Pro and above). Check your plan if autofill fails.
• Separate product: the Canva Dev MCP server (claude mcp add canva-dev -- npx -y @canva/cli@latest mcp) helps you build Canva apps. It is not for editing your designs.

• Canva MCP server: install for every agent

Webflow's MCP server can change a site's design (layouts, elements, styles, components, interactions), work with the CMS, create pages and read analytics. You connect with OAuth and pick which sites it can reach. Agents can do only what your Webflow role allows. Most tools work without the Designer open; snapshots, image uploads and reading or changing the current selection, page or breakpoint need the Designer open with the MCP Bridge App running.

claude mcp add --transport http webflow https://mcp.webflow.com/mcp

{
  "mcpServers": {
    "webflow": {
      "command": "npx",
      "args": ["-y", "webflow-mcp-server@latest"],
      "env": { "WEBFLOW_TOKEN": "YOUR_WEBFLOW_TOKEN" }
    }
  }
}

• Main tools: data_sites_tool, data_pages_tool, data_cms_tool, data_element_builder, data_element_tool, data_style_tool, data_component_tool, data_assets_tool, data_localization_tool, data_scripts_tool.
• Limits: each authorization covers one workspace. The agent cannot create new site projects; make the site in the dashboard first. Page branches need an Enterprise plan.
• Free tier: Webflow's pricing page lists the MCP server on the free Starter site plan (webflow.io domain, 2 static pages, limited CMS).
• Gotcha: the GitHub README lists the remote URL as https://mcp.webflow.com/sse; the developer docs use https://mcp.webflow.com/mcp, which we follow.

• Webflow MCP server: install for every agent

The Wix MCP lets the agent search Wix docs, write code for Wix, call APIs on your sites, and create and publish sites. It is a built-in connector in Claude. By default it signs in through your Wix account; for tools with no interactive login, use an API key and your Wix account ID. Wix lists Node.js 19.9.0 or higher as a prerequisite.

claude mcp add --transport http wix-mcp-remote https://mcp.wix.com/mcp

{
  "mcpServers": {
    "wix-mcp-remote": {
      "command": "npx",
      "args": ["-y", "@wix/mcp-remote@latest", "https://mcp.wix.com/mcp"]
    }
  }
}

• Main tools: WixREADME, ListWixSites, GetSiteContext, ManageWixSite (create, update or publish a site), CallWixSiteAPI, ExecuteWixAPI (Bookings, Stores, CMS), UploadImageToWixSite, plus documentation search tools.
• API key setup: send Authorization and wix-account-id headers; the local proxy reads WIX_API_KEY.
• Gotcha: if the connection drops after a long idle period or after switching Wix accounts, delete ~/.mcp-auth and reconnect.
• Do not confuse it with the Wix Site MCP at <your-site>/_api/mcp. That one lets visitors' agents use a live site as an anonymous visitor and cannot edit it.

• Wix MCP server: install for every agent

Miro's MCP server is hosted by Miro, and clients must support remote connections. It reads board content and creates or updates boards, diagrams, prototypes and comments. You sign in with OAuth 2.1 and pick one Miro team; the agent sees only boards in that team. On Enterprise, an admin must enable MCP first.

claude mcp add --transport http miro https://mcp.miro.com

• Main tools: board_search_boards, board_create, canvas_search, canvas_read_as_svg, canvas_create_from_svg, canvas_update_from_svg, prototype_read, prototype_create, comment_list_comments, comment_reply, image_create.
• Daily tool-call limits reset at 00:00 UTC: Free 100, Starter 500, Business 2,000, Enterprise 10,000.
• Price: Starter $8 and Business $20 per member a month, billed yearly.
• Gotcha: older board_list_items, context_*, layout_*, diagram_* and doc_* tools were removed, so old prompts that name them will fail. The table_* tools are marked as deprecating soon.

• Miro MCP server: install for every agent

Cloudinary runs several MCP servers. Asset Management uploads and manages images, videos and raw files with search and filtering. Environment Config manages upload presets and named transformations. Structured Metadata manages metadata fields. Analysis does AI tagging and needs OAuth. MediaFlows builds media automations. Remote servers use OAuth by default, or API credentials in headers; MediaFlows does not use OAuth and takes credentials in headers only.

{
  "mcpServers": {
    "cloudinary-asset-mgmt": {
      "url": "https://asset-management.mcp.cloudinary.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "cloudinary-asset-mgmt": {
      "url": "https://asset-management.mcp.cloudinary.com/mcp",
      "headers": {
        "cloudinary-url": "cloudinary://api_key:api_secret@cloud_name"
      }
    }
  }
}

• Other remote URLs: https://environment-config.mcp.cloudinary.com/mcp, https://structured-metadata.mcp.cloudinary.com/mcp, https://analysis.mcp.cloudinary.com/sse, https://mediaflows.mcp.cloudinary.com/v2/mcp.
• Local: the npx packages read CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET (the Asset Management README also accepts CLOUDINARY_URL). Find credentials on the API Keys page in Console Settings. Package names differ between the docs (@cloudinary/asset-management) and the GitHub README (@cloudinary/asset-management-mcp); use the docs name.
• Asset Management custom tools: transform-asset and get-tx-reference. Run with --mode dynamic to load tools on demand.
• Free plan: 25 monthly credits, 3 users, no credit card. Plus: $99 a month billed monthly, or $89 a month billed yearly.
• Gotcha: Cloudinary's docs give Claude Code commands with --transport sse, which we follow; its GitHub README says the /mcp endpoints are Streamable HTTP and /sse is deprecated. MediaFlows uses different header names (cld-cloud-name, cld-api-key, cld-secret).

• Cloudinary MCP server: install for every agent

• Design to code: Figma remote server. Budget for a Professional Dev or Full seat; the free Starter plan's 20 calls a month is only enough to try it.
• Build a website: Webflow if you want precise control of layout, styles and the CMS. Wix if you want the agent to create and publish a site and manage store, bookings or CMS data.
• Edit marketing designs: Canva. Free covers generating, editing and exporting; brand templates and resizing need Pro.
• Whiteboards: Miro. The free plan's 100 calls a day is enough for reading boards and drafting diagrams.
• Image and video assets: Cloudinary Asset Management, with Environment Config if the agent should manage upload presets.
• Prefer the OAuth endpoints, so no API keys end up in committed config files.
• All details on this page were checked against vendor docs and pricing pages on 2026-10-23.

• Set up MCP servers, rules and permissions in one paste
• Add an MCP server in every AI coding agent