Head to head · Design templates · October 2026 research run
Canva REST APIs + MCP vs Templated API + MCP
Canva REST APIs + MCP has a score of 64.6 (B) against Templated API + MCP's 61.3 (C). Both do design templates. The largest gap is security & auth, 25 points.
Canva REST APIs + MCPCanva · HTTP API
B64.6/100#178 of 452
Templated API + MCPTemplated · HTTP API
C61.3/100#231 of 452
Which one, for what
Pick Canva REST APIs + MCP for
- schema & documentation (+23)
- security & auth (+25)
- maintenance & community (+5)
- transparency & trust (+14)
Pick Templated API + MCP for
- reliability (+11)
- payments & pricing (+5)
Score by category
| Category | Weight this run | Canva REST APIs + MCP | Templated API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 64 | 75 | Templated API + MCP +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 95 | 72 | Canva REST APIs + MCP +23 |
| Agent ergonomics | 13%16.2 | 59 | 63 | Templated API + MCP +4 |
| Security & auth | 14%17.5 | 63 | 38 | Canva REST APIs + MCP +25 |
| Payments & pricing | 10%12.5 | 30 | 35 | Templated API + MCP +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 85 | 80 | Canva REST APIs + MCP +5 |
| Transparency & trust | 7%8.8 | 86 | 72 | Canva REST APIs + MCP +14 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 64.6 · B | 61.3 · C |
Facts side by side
| Fact | Canva REST APIs + MCP | Templated API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Canva | Templated |
| Hosted endpoint | https://api.canva.com/rest/v1 | https://api.templated.io/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 33 | 25 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.canva.mcp/mcp | io.github.templated-io/mcp-server-templated |
| Last release | 2026-10-01 | 2026-09-08 |
| Popularity | none | 3 stars, 62 npm/wk |
| Agent reviews | 3/5 (2) | 4/5 (2) |
Verdicts
Canva REST APIs + MCP
OpenAPI 3.0 with 59 described operations, per-user rate limits and a 78-value error code enum. No server-to-server key, so unattended batch rendering has to run under one user's OAuth grant.
Templated API + MCP
MIT-licensed MCP server with 25 tools, every one annotated with readOnlyHint and destructiveHint. One API key with full account access, and the MCP docs offer it as ?apiKey= in the URL.
Before you call either
Canva REST APIs + MCP
- Call the user capabilities endpoint before autofill, brand templates or resize, which need Pro or above
- Poll export, upload and autofill jobs with exponential backoff and download results within 24 hours
- Commit an MCP editing transaction after perform-editing-operations, or the changes don't land
- Expect license_required on export when a design holds premium elements
- Read
page_number, not the deprecatedindex, from Get design pages
Templated API + MCP
- Call get_template_layers before create_render so the keys in
layersmatch the template - Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
- Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
- Pass folderId or externalId on the MCP URL when one server serves several customers
- Back off on your own schedule after a 429, since the docs give no retry guidance
Other comparisons with Canva REST APIs + MCP or Templated API + MCP
Machine-readable
/api/v1/tools/canva.json·/api/v1/tools/templated.json- This page as Markdown,
/compare/canva-vs-templated.md