Skip to main content
Glama
mattcoatsworth

Zoom API MCP Server

by mattcoatsworth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Zoom API MCP Server

No user-submitted related servers found.

    Related Servers

    • Zoom API MCP Server

      allisonwhilden
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP Server that enables interaction with Zoom's API through the Multi-Agent Conversation Protocol, allowing users to access and control Zoom's functionality via natural language commands.
      -

    • Zoom MCP Server

      qingyun-ag2
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the Zoom API through natural language, auto-generated using AG2's MCP builder.
      -

    • Zoom API MCP Server

      qingyun-wu
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the Zoom API through natural language commands, auto-generated using AG2's MCP builder.
      -

    • zoom-mcp

      LesterAJohn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with Zoom APIs through MCP, supporting multi-user OAuth token management, read-only and admin-gated mutation tools, schema discovery, and query suggestions for LLM workflows.
      MIT

    • ChatterBox MCP Server

      ChatterBoxIO
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to join and interact with online meetings (Zoom and Google Meet), capturing transcripts and recordings to generate meeting summaries.
      3
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2/5.0

    Scored across 54 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose based on resource type and action. Tools are organized by resource (meeting, user, webinar, channel, etc.) and operation (create, get, list, update, delete), with no ambiguous overlaps. The consistent pattern makes it easy to distinguish between tools like get_meeting, list_meetings, and delete_meeting.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout. Verbs (create, get, list, update, delete, send, search) are used predictably, and nouns clearly identify the resource type. There are no deviations in naming conventions across the entire set.

    Tool Count2/5

    With 54 tools, this is an extremely large set that feels heavy and overwhelming for a single server. While Zoom's API is comprehensive, this many tools suggests poor scoping or a direct mapping of API endpoints without consolidation, making it difficult for agents to navigate efficiently.

    Completeness5/5

    The tool set provides comprehensive CRUD/lifecycle coverage across all major Zoom resources (meetings, webinars, users, channels, webhooks, recordings, etc.). It includes create, get, list, update, and delete operations consistently, plus specialized actions like sending messages and generating reports, leaving no obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources