Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldCanva Dev MCPMCP100 SelectedDocker MCP GatewayMCP100 Selected
Task fit
Best for
  • Building Canva Apps SDK and Connect API integrations
  • Finding Canva developer documentation and App UI Kit guidance
  • Generating app scaffolds and reviewing app UI against Canva guidance
  • Running multiple MCP servers behind one stdio connection
  • Isolating catalog MCP servers in containers with restricted privileges and resources
  • Centralizing server profiles, secrets, OAuth, logs, and call traces
Not ideal for
  • Creating or editing end-user Canva designs through natural language
  • Production automation that needs direct Canva account actions
  • Users who need only one simple remote MCP endpoint
  • Hosts where Docker Desktop or Docker Engine cannot run
Avoid when
  • Node.js 24 or later and npm cannot be installed
  • The coding agent must not receive local app context
  • Agent-generated code would be deployed without review or normal testing
  • You cannot review every downstream MCP server and profile permission
  • The agent must not be able to discover or add tools dynamically
  • Container isolation is being treated as protection from an over-privileged downstream credential
Provenance
Provenance details

First-party MCP

Canva · Publisher source ↗

First-party MCP

Docker · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Jul 22, 2026

Repo: Aug 13, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,529

GitHub stars · checked 2026-08-14T18:46:26.000Z

Shared package downloads

10,746

Shared package downloads (not MCP-specific) · checked 2026-07-29T17:30:00.000Z

Not documented
External adoption evidence
  • npm: package downloads: 10,746Non-comparable contextual signal.npm: package downloads · Admission snapshot · checked 2026-07-29T17:30:00.000ZEvidence source ↗
  • github: repository stars: 1,529Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe documented Dev MCP setup itself requires no Canva account login. Separate Canva CLI or Connect API workflows can require their own Canva credentials, which must not be placed in prompts.The gateway handles downstream server credentials and OAuth flows. The client connects locally over stdio by running `docker mcp gateway run`, optionally with a named profile.
CostCanva documents no separate Dev MCP fee. Node/npm are free; Canva developer services, the selected AI client, and model usage may have separate costs.The open-source gateway documents no standalone usage fee. Docker Desktop licensing, Docker AI Governance invite-only features, container infrastructure, downstream MCP services, and AI-client charges may apply.
PermissionsThe local server can fetch Canva developer documentation and expose development helpers, including app generation and design-review guidance. Its effective local access also depends on the connected coding client's filesystem and command permissions.The gateway exposes the servers and tools included in the selected profile. It starts catalog servers in containers with restricted privileges, network access, and resource usage, injects configured secrets, and can support OAuth. Dynamic MCP can additionally expose tools that discover, add, configure, remove, and execute servers during a session.
Data handlingCanva states that the MCP server operates locally, fetches documentation from canva.dev and other sources, and does not transmit code or prompts anywhere other than the selected AI agent or LLM tool.Tool requests and results pass through the local gateway to downstream MCP containers or remote services. Docker documents built-in logging and call tracing. Credentials are managed and injected by the gateway; downstream servers can still receive data and reach networks allowed by their configuration.
Limitations
Tradeoffs
  • The server runs locally and Canva says it does not transmit code or prompts beyond the chosen AI agent, but the agent itself still receives project context.
  • Using `@latest` gives current guidance but is mutable; pin an approved Canva CLI version for reproducibility.
  • Generated code and design-review advice accelerate development but do not replace API validation, tests, or app review.
  • Gateway isolation improves lifecycle and credential management but adds Docker runtime complexity and local resource use.
  • The MCP Toolkit is documented as Beta, and Dynamic MCP is experimental.
  • The gateway reduces direct host privileges, but network access and injected credentials still let downstream servers affect external systems.
Risk contextTreat generated code as untrusted until reviewed and tested, keep production tokens out of prompts, validate Connect API requests against official schemas, and pin the CLI for controlled environments. This is a documentary review and does not claim MCP100 execution testing.Gateway safety is only as strong as the selected profile, catalog provenance, tool filters, network policy, and downstream credentials. Disable experimental Dynamic MCP unless required, use narrow profiles, verify signatures where available, inspect traces, and treat each downstream server as a separate trust decision. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-07-29T20:58:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →
Compare MCPs | MCP100 Index