create_meeting
Create a meeting
LABSCO SUMMARY
Booking a call stops being a tab switch, but the meeting record is as far in as you get.
Four tools cover a scheduled meeting end to end — create it, list what exists, read one back, remove it. Nothing here touches participants, recordings, chat or cloud storage, and a meeting created elsewhere is reachable only if list_meetings returns its ID first.
What it is
A scheduling surface over the Zoom meetings API, covering the life of a scheduled meeting and nothing around it.
What you get
- Meeting creation carrying a topic, an agenda, a start time and a timezone
- The list of scheduled meetings, narrowed by meeting type
- Full detail for one meeting read back by its ID
- Deletion of a meeting by ID
Requirements
A Zoom account whose app credentials fill three environment variables: ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET.
Setup effort
One command plus credentials — npx -y @yitianyigexiangfa/zoom-mcp-server@latest, then supply credentials
USE CASES
01
Scheduling a call while you are still in the thread that needs it
Create the meeting with its topic, agenda, start time and timezone in the same message where the time was agreed, then confirm it landed on the calendar.
02
Calling off a meeting that no longer needs to happen
Find the meeting in the schedule, read its details back to be sure it is the right one, and remove it by ID.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_a_meeting
Delete a meeting with a given ID
get_a_meeting_details
Retrieve the meeting's details with a given ID
list_meetings
List scheduled meetings
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
- npx on PATH
- ZOOM_ACCOUNT_ID in your environment
- ZOOM_CLIENT_ID in your environment
- ZOOM_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @yitianyigexiangfa/zoom-mcp-server@latestMCP Clients
VS Code
VS CODE · JSON
{
"inputs": [
{
"type": "promptString",
"id": "ZOOM_ACCOUNT_ID"
},
{
"type": "promptString",
"id": "ZOOM_CLIENT_ID"
},
{
"type": "promptString",
"id": "ZOOM_CLIENT_SECRET"
}
],
"servers": {
"zoom-mcp-server": {
"command": "npx",
"args": [
"-y",
"@yitianyigexiangfa/zoom-mcp-server@latest"
],
"env": {
"ZOOM_ACCOUNT_ID": "${input:ZOOM_ACCOUNT_ID}",
"ZOOM_CLIENT_ID": "${input:ZOOM_CLIENT_ID}",
"ZOOM_CLIENT_SECRET": "${input:ZOOM_CLIENT_SECRET}"
}
}
}
}
