Canva MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_healthA | Returns runtime readiness for the Canva MCP server. |
| create_presentation_outlineC | Generates a presentation plan from a brief. |
| select_templateC | Selects the most appropriate Canva template for the brief. |
| list_presentationsC | Lists Canva presentations in a folder, defaulting to root. |
| list_brand_templatesC | Lists Canva brand templates available to the authorized user. |
| get_brand_template_datasetB | Returns the autofillable dataset fields for a Canva brand template. |
| create_autofilled_presentationB | Creates a Canva design from a brand template using Autofill data. |
| create_markdown_presentationB | Builds a styled PPTX from a markdown file and optionally imports it into Canva. |
| get_import_jobB | Retrieves the current status of a Canva import job. |
| upload_image_assetA | Uploads a local image file to Canva as a reusable asset (for use in autofill image fields). |
| create_flyerA | Builds a styled single-page flyer (PPTX) and optionally imports it into Canva as a design. If you already have a flyer-shaped Brand Template in Canva, generate_presentation_from_brief + get_brand_template_dataset (autofill) can target it directly instead. |
| generate_presentation_from_briefA | Builds an outline and creates a Canva presentation using Autofill when a brand template is available. |
| create_presentationC | Creates a new Canva presentation from template or outline. |
| add_slideA | Not implementable: Canva Connect API has no endpoint to add a slide to an existing design. |
| batch_upsert_slidesA | Not implementable: Canva Connect API has no endpoint to create or update slides in an existing design. |
| update_slide_contentC | Not implementable: Canva Connect API has no endpoint to edit text/structure of a slide in an existing design. |
| apply_brand_kitA | Not implementable: Canva Connect API has no endpoint to restyle colors/fonts on an existing design. |
| replace_text_placeholdersC | Not implementable: Canva Connect API has no endpoint to edit text nodes in an existing design. |
| search_assetsC | Not implemented: no Canva-hosted asset search/library endpoint is wired up here. |
| insert_imageA | Not implementable: Canva Connect API has no endpoint to insert an image into an existing design's slide. |
| insert_chartA | Not implementable: Canva Connect API has no endpoint to insert a chart into an existing design's slide. |
| reorder_slidesA | Not implementable: Canva Connect API has no endpoint to reorder slides in an existing design. |
| validate_presentationC | Not implemented: Canva Connect API exposes no design-content introspection endpoint to validate an existing design against. |
| generate_speaker_notesA | Not implemented: Canva Connect API has no endpoint to write speaker notes into an existing design. |
| export_presentationC | Exports the presentation to a supported format. |
| get_export_jobB | Retrieves the current status of a Canva export job. |
| share_presentationB | Not implemented: no sharing/permissions endpoint for designs was confirmed or wired up in this integration. |
| browser_run_canva_actionD | Not implemented: no browser-automation dependency (e.g. Playwright) is installed in this project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Multiple tools target the same action of creating presentations (create_presentation, create_markdown_presentation, generate_presentation_from_brief, create_autofilled_presentation, create_flyer), with descriptions that only partially differentiate them. Many tools are stubs marked 'Not implementable' or 'Not implemented,' which creates ambiguity about which tools are actually usable and what they do.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_presentations, create_presentation, export_presentation, get_export_job). There are no mixed conventions or unpredictable verb styles, making the naming highly predictable.
The server exposes 28 tools, but a large portion are non-functional stubs or redundant creation variants. This overinflates the count relative to the actual working surface, making it heavier than needed for the core functionality and adding noise for agents.
The tool set covers creation, autofill, export, and import workflows, but lacks any meaningful editing or management capabilities—slide manipulation, text replacement, and sharing are all stubs. This leaves obvious gaps in the lifecycle of a presentation (e.g., no update/delete), causing dead ends for agents.