ClawHub

Maverick Canva Mcp

Search, read, and manage Canva design work through Canva's hosted MCP server. Thin pass-through to Canva's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about Canva designs, assets, exports, brand materials, folders, comments, or templates.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisReview

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install maverick-canva-mcp

Canva

How to use this skill

This skill is a thin pass-through to Canva's hosted MCP server at https://mcp.canva.com/mcp. The live server is the source of truth for what tools exist, what they're called, what arguments they take, and any per-server instructions the server publishes.

Always invoke through bash {baseDir}/scripts/invoke.sh — never call mcporter directly. The wrapper seeds the OAuth vault from the env-supplied tokens when needed, then calls mcporter.

Step 1 — Discover the live tool catalog and any server-published usage instructions. Always run this first; do not rely on tool names from memory:

bash {baseDir}/scripts/invoke.sh list maverick-canva-mcp --schema

The output includes the server's Instructions: field, if published, and a JSON Schema for every tool's parameters. Treat this as the authoritative reference for the rest of the session.

Step 2 — Call any tool from the catalog using the form maverick-canva-mcp.<tool>:

bash {baseDir}/scripts/invoke.sh call maverick-canva-mcp.<tool> <arg>=<value> ...

Add --output json for structured output and transport-error envelopes:

bash {baseDir}/scripts/invoke.sh call --output json maverick-canva-mcp.<tool> ...

Safety

Write-capable tools can create, edit, export, publish, share, comment on, or otherwise change Canva content visible to the connected account or team. Confirm clear user intent before making changes, and inspect current design or asset state before editing.

Authentication

Credentials are available to the agent runtime through required env vars. The wrapper seeds mcporter's vault as needed before each call. mcporter handles authentication automatically: it reads tokens from the vault, sends them with each request, and refreshes them on expiry.

The only failure mcporter cannot recover from on its own is grant revocation. It manifests as calls persistently failing with auth errors that do not clear on retry; ask the user to re-authorize the integration.

References