Skip to main content
Glama
Justin-Gladiator

Zoom Phone + Virtual Agent MCP Server

by Justin-Gladiator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Zoom Phone + Virtual Agent MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Zoom MCP Server

      halbert04
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing Zoom users, meetings, webinars, and recordings through 24 tools with support for server-to-server OAuth and static token authentication.
      13 npm
      MIT

    • zoom-mcp

      aronroyca
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with structured access to Zoom recorded meetings, enabling search, summarization, and action item extraction.
      0
      BSD 2-Clause "Simplified"

    • Zoom MCP Server

      surajpratap
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the Zoom API to manage meetings, retrieve cloud recording transcripts, and access team chat messages. The server supports listing account users and participants, featuring a configurable read-only mode for secure tool access.
      10
      18 npm
      MIT

    • ParcelPilot MCP Server

      PraneethGoud04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve customer, order, ticket, policy, and agreement information, and to prepare or execute state-changing support actions like escalations and follow-ups with confirmation and access control.
      -
    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

    B3.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools are clearly distinct: phone_ tools handle call data/routing while va_ tools handle virtual agent content and analytics. There's some potential confusion between phone_get_account_call_history and phone_get_account_call_logs (similar purpose, distinguished by legacy-style), and between phone_get_call_log_details and phone_get_call_element (both detail views of call segments, but one is by log ID vs element ID).

    Naming Consistency4/5

    Names follow a consistent prefix_verb_noun pattern: phone_/va_ prefixes cleanly separate domains, and verbs like get/update/create are used consistently. The single deviation is va_sync_knowledge_base, which uses 'sync' as a verb rather than the otherwise consistent get/create/update pattern, making it slightly inconsistent with the established naming style.

    Tool Count4/5

    19 tools is at the upper edge of the reasonable range, but it spans two distinct product domains (Zoom Phone and Virtual Agent) with rich feature sets. Each tool covers a meaningful operation. Slightly heavy because it combines two domains, but each tool earns its place within its domain.

    Completeness4/5

    The Virtual Agent side is well-covered with articles CRUD (create/get/update but missing delete), sync operations, and analytics queries. The phone side covers call history, logs, and call handling settings with read/update but lacks create operations (which makes sense for read-centric call data). Minor gaps: no delete article, and the call-handling settings lack full lifecycle coverage, but the core workflows are complete.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources