Canva Dev MCP Server

The Canva Dev MCP Server is Canva's official Model Context Protocol server for developers building Canva Apps or Connect API integrations. It runs locally on the development machine and fetches documentation from canva.dev and related sources on demand. This gives a compatible AI client — such as Cursor, Claude Desktop, or Claude Code — specialized tools and up-to-date documentation context without the developer needing to switch between the assistant and a browser. The official documentation is available at https://www.canva.dev/docs/apps/mcp-server/.

What is the Canva Dev MCP Server?

The server is not a design automation tool and has nothing in common with the Canva AI Connector (the remote MCP endpoint at mcp.canva.com/mcp). It is a pure developer assistant: it brings Canva developer documentation, the App UI Kit, the Apps SDK, and the Connect API reference into the AI agent's context, so that the agent can provide more precise, documentation-backed answers when writing Canva App code. According to the provider, the server supports AI clients such as Cursor, Claude Desktop, and Claude Code.

Distinction from the Canva AI Connector

Canva publishes two separate MCP products with different purposes. The AI Connector (Canva MCP Server) is a remote server at https://mcp.canva.com/mcp that connects via OAuth to a Canva user account and enables design actions such as creating, editing, searching, and exporting designs. It is aimed at content and marketing teams. The Canva Dev MCP Server, by contrast, is a local stdio process launched by the Canva CLI that provides exclusively read access to public developer documentation. It is aimed at developers. Both servers come from Canva but address different target audiences and use cases — one for design work, the other for app development.

How does the server work?

The Canva Dev MCP Server is started via the Canva CLI (@canva/cli) and configured as a local MCP endpoint in the respective client. For Cursor, a .cursor/mcp.json file is created containing the start command npx -y @canva/cli@latest mcp. Claude Desktop and Claude Code receive analogous configuration files. According to the documentation, MCP tools are only available in the client's Agent mode and cannot be invoked directly: the AI agent decides which tool to use based on the request. To activate the server, a context-relevant question with keywords such as "App UI Kit," "Apps SDK," or an explicit request for Canva documentation references is sufficient.

Requirements

For operation, git, Node.js v24 or higher, npm, and a compatible MCP client are required. According to the official documentation, Cursor, Claude Desktop, and Claude Code are explicitly named. An internet connection is required so that the server can load documentation from canva.dev on demand. A Canva account or API key is not needed, since the server accesses only public developer documentation.

Step-by-step setup

Setup for Cursor involves three steps: first, create the configuration file .cursor/mcp.json in the project directory. Second, add the entry { "mcpServers": { "canva-dev": { "command": "npx", "args": ["-y", "@canva/cli@latest", "mcp"] } } }. Third, restart Cursor to load the settings. The procedure is analogous for Claude Desktop and Claude Code: the respective MCP configuration file receives the same start command. Canva also provides a direct Cursor configuration link that skips manual file creation. After restarting the client, verify the connection by asking a question in Agent mode — for example, "How many components are in the App UI Kit?" — and wait for a tool invocation prompt.

Features and tools

According to the provider, the server gives an AI agent access to specialized tools and documentation context for Canva App development. Specifically, the assistant enables: documentation search on canva.dev for Apps, the App UI Kit, the Apps SDK, the Connect API, and related topics; API reference queries about available components, hooks, and configuration options; context-relevant answers about app configuration, authentication, scopes, monetization, and the submission process; and code suggestions based on current Canva design guidelines and component definitions. The server has no public source repository; Canva distributes the package through the Canva CLI.

Security and privacy

According to the official documentation, the Canva Dev MCP Server operates locally on the device and does not transmit code or prompts to any sources other than the configured AI agent or the language model in use. It fetches documentation from canva.dev and other sources and provides it to the agent as context. Developers should be aware that retrieved documentation content is embedded in the AI client's model requests. When working with proprietary model backends, it is worth verifying what data the requests contain. Theoretical prompt injection through manipulated documentation content is practically very unlikely with official Canva documentation. Since the server requires no Canva account and no authentication, there is no risk of accidental design changes or data access.

FAQ

Is this server different from the Canva AI Connector? Yes. The Canva AI Connector is a remote MCP server for design work that connects via OAuth to a Canva account. The Canva Dev MCP Server is a local stdio process for developers that fetches public Canva developer documentation. Both come from Canva but address different audiences.

Do I need a Canva account? No. The Dev MCP Server accesses only public documentation and requires neither an account nor an API key.

Is the server free? The Canva CLI package @canva/cli is free to use. Costs may arise from the AI client or the language model in use.

Is there a public repository? According to research conducted on 2026-09-08, Canva does not publish standalone source code for this MCP server; it is distributed through the Canva CLI.

git, Node.js v24 or higher, npm, compatible AI client (Cursor, Claude Desktop, Claude Code), internet connection for documentation fetching.

Add to .cursor/mcp.json (or client equivalent): { "mcpServers": { "canva-dev": { "command": "npx", "args": ["-y", "@canva/cli@latest", "mcp"] } } }. Restart the client.

npx -y @canva/cli@latest mcp

No authentication required; the server accesses public Canva developer documentation.

Read-only access to public Canva developer documentation; no account or design access.

The server runs locally and fetches documentation from canva.dev. Retrieved content is embedded in the AI client's model requests. According to the provider, no code or prompt is transmitted to other sources.

Low risk profile: read-only access to public documentation, no authentication, local stdio process. Retrieved documentation flows into model requests.