| name | zoom-mcp/team-chat |
| description | Zoom Team Chat MCP server guidance. Use for Team Chat MCP endpoints, OAuth scopes,
and write-capable tool workflows such as sending or editing messages, creating or
updating channels, adding channel members, and sending contact invitations. Prefer
this child skill when the request is specifically about Team Chat MCP rather than
default Zoom MCP search or deterministic Team Chat REST API implementation.
|
| user-invocable | false |
| triggers | ["team chat mcp","zoom chat mcp","zoom team chat mcp","send zoom chat via mcp","edit zoom chat message mcp","create zoom chat channel mcp","add zoom chat channel members mcp","zoom_chat_message_send","zoom_chat_channel_create"] |
Zoom MCP Team Chat
Dedicated guidance for Zoom's Team Chat MCP server.
Use this MCP surface for agent-driven Team Chat actions. Use
../../team-chat/SKILL.md when the user needs deterministic REST
API implementation, custom backend retries, webhooks, reporting, or a production integration
that should not depend on agent tool invocation.
Endpoints
| Transport | URL |
|---|
| Streamable HTTP (recommended) | https://mcp.zoom.us/mcp/team_chat/streamable |
| SSE (fallback) | https://mcp.zoom.us/mcp/team_chat/sse |
This plugin documents the Team Chat MCP surface but does not register it in
../../../.mcp.json by default. Add it manually if a workflow needs
write-capable Team Chat MCP tools.
Authentication
- OAuth bearer tokens are passed through the MCP
Authorization header.
- The protected-resource metadata endpoint is
https://mcp.zoom.us/.well-known/oauth-protected-resource/mcp_team_chat.
- The server is scoped to the caller's account and subject to Team Chat policy restrictions.
- End-to-end encrypted, archived, retention-restricted, or policy-blocked chats may not be accessible or mutable through this surface.
Required Scopes
Team Chat MCP scopes advertised by protected-resource metadata:
team_chat:write:user_messageteam_chat:update:user_messageteam_chat:write:contact_informationteam_chat:write:user_channelteam_chat:update:user_channelteam_chat:write:members
Safety Rules
This server contains write-capable tools. Before invoking a write tool:
- Confirm the user explicitly asked to send, edit, create, update, invite, or add members.
- Resolve IDs carefully.
chat_session_id may be a user/member ID, user email for 1:1 messages, or a channel ID.
- Preview message/channel changes when the target or wording is ambiguous.
- Do not guess channel IDs, message IDs, or invitee emails.
- Prefer the REST Team Chat skill for bulk operations, durable retry logic, approval workflows, or audit-heavy production systems.
Available Tools
The current Team Chat MCP tool surface is:
zoom_chat_message_sendzoom_chat_message_updatezoom_chat_contact_addzoom_chat_channel_createzoom_chat_channel_updatezoom_chat_channel_members_add
Some MCP clients namespace server tools in the UI. Treat the raw tool names above as
authoritative after tools/list.
Reference: references/tools.md
Common Workflows
Send a message:
zoom_chat_message_send
chat_session_id: "CHANNEL_ID_OR_USER_ID_OR_EMAIL"
message_content: "Deployment starts at 17:00 UTC."
message_format: "text"
Send a threaded reply:
zoom_chat_message_send
chat_session_id: "CHANNEL_ID"
parent_message_id: "PARENT_MESSAGE_ID"
message_content: "Confirmed. I will post the follow-up here."
message_format: "text"
Edit a message sent by the caller:
zoom_chat_message_update
chat_session_id: "CHANNEL_ID_OR_USER_ID"
messageId: "MESSAGE_ID"
message_content: "Updated status: deployment completed."
message_format: "text"
Create a channel:
zoom_chat_channel_create
channel_name: "incident-response"
channel_type: "private_channel"
post_message_permission: "everyone"
mention_all_permission: "channel_owner_and_admin"
new_members_can_see_previous_messages_and_files: true
Add members to a channel:
zoom_chat_channel_members_add
channelId: "CHANNEL_ID"
user_email_list:
- "person@example.com"
Chaining
References
