Zoom MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Zoom MCP Server?

Zoom MCP Server is a tool that allows users to manage Zoom meetings using AI assistance, enabling functionalities like scheduling, listing, and deleting meetings.

how to use Zoom MCP Server?

To use Zoom MCP Server, you need to configure it with your Zoom Client ID, Client Secret, and Account ID, and then you can execute commands to manage your meetings.

key features of Zoom MCP Server?

  • List upcoming and past meetings
  • Schedule new meetings with specific details
  • Delete existing meetings
  • Retrieve details of specific meetings

use cases of Zoom MCP Server?

  1. Automating the scheduling of meetings for teams.
  2. Quickly retrieving meeting details for reference.
  3. Managing multiple meetings efficiently through command-line interface.

FAQ from Zoom MCP Server?

  • What do I need to start using Zoom MCP Server?

You need a Zoom account and to create a Server to Server OAuth App in the Zoom Marketplace to get your Client ID, Client Secret, and Account ID.

  • Is there a graphical interface for Zoom MCP Server?

No, it is primarily a command-line tool designed for developers and advanced users.

  • Can I use it for personal meetings?

Yes, it can be used for personal or professional meetings as long as you have the necessary Zoom credentials.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago