Zoom Canvas MCP

Use the dedicated Canvas MCP server for agent-driven Canvas file, block, collaborator, sharing, ownership, import, and content export workflows. The current official product name is Zoom Canvas MCP Server; do not select the old Docs MCP endpoint.

Endpoint

https://mcp.zoom.us/mcp/canvas/streamable

Use tools/list as the runtime source of truth for tool names and schemas. The current official catalog exposes 18 tools. See references/tools.md.

Required Scopes

Add only the scopes required by the requested operations:

• docs:read:export
• docs:read:file
• docs:read:general_access
• docs:read:list_children
• docs:read:list_file_collaborators
• docs:write:import
• docs:write:content
• docs:write:collaborator
• docs:update:content
• docs:update:file
• docs:update:file_owner
• docs:update:general_access
• docs:update:collaborator
• docs:delete:content
• docs:delete:file
• docs:delete:collaborator

These are user-level OAuth scopes for the current hosted Canvas server. Do not substitute S2S or Meeting SDK credentials.

Chaining

• Marketplace app creation: Canvas MCP template via Marketplace app management
• Token acquisition: create the app first, then use OAuth and PKCE to authorize the user and mint the bearer token supplied to this endpoint
• Parent MCP routing: ../SKILL.md
• Canvas REST API fallback: ../../rest-api/references/zoom-docs.md

Safety Rules

• Confirm destructive operations before deleting files, blocks, or collaborators.
• Preserve file and block IDs returned by discovery; do not guess identifiers.
• Use REST APIs for deterministic bulk jobs, custom retries, and audit-heavy workflows.

Official Source

https://developers.zoom.us/docs/mcp/zoom-canvas-mcp-server/