Webex Meetings
Schedule, update and delete Webex meetings and read their recordings and transcripts from an AI agent. Cisco documents all 8 tools and Anthropic's directory lists the same 8. Creating a meeting emails the invitees by default.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Webex Meetings via MCP
https://mcp.webexapis.com/mcp/webex-meetingWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Webex Meetings Tools & Capabilities (8)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The OAuth scope list is not a read/write boundary. The server's RFC 9728 descriptor lists seven scopes under
scopes_supportedand repeats all seven underrequired_scopes. Nothing is optional, so an OAuth grant that reads transcripts necessarily also grantsmeeting:schedules_write, which is create, update and delete. The one place a boundary does exist is the WCIT token path, where Cisco documents scopes being elicited per tool call — but that path only works on clients supporting MCP elicitation. - Email is the default on every write. Webex's Create, Update and Delete Meeting APIs all document
sendEmaildefaulting totrue. An agent that does not set it explicitly notifies the host and every invitee. - Deletion cannot be undone, and can take a whole series. Webex documents that a deleted meeting cannot be recovered and that passing a meeting-series ID deletes the entire series.
- An admin gate stands in front of everything. Cisco requires the server to be enabled in Webex Control Hub before any user can connect. That gate is also the strongest control available to you: Control Hub supports per-tool enablement scoped to user groups, so an org can publish the read tools broadly and restrict create and delete to a named group.
- The meeting summary needs Webex AI Assistant. Cisco flags
webex-get-meeting-summaryas requiring it. Without AI Assistant there are no summary notes or action items to fetch. - Transcripts and summaries only exist for ended meetings. Webex's transcript and summary APIs both reject meeting series, scheduled meetings and in-progress instances; only an ended meeting instance is supported.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or
readOnlyHintis published here. Everything above about tool behaviour comes from Cisco's documentation and from the REST endpoints Cisco documents these tools as calling. - Cisco publishes no rate limit for this server. It publishes one for its Vidcast MCP server — 120 invocations per 60 seconds, 10 concurrent — and none on the Meetings page. Assume the underlying Webex REST API limits apply and that they are not documented here.
- There is no
llms.txtand the doc page is JavaScript-rendered.developer.webex.com/llms.txtreturns 404, and the documentation page yields 478 words to a plain text extractor while carrying its full content inside awindow.__INITIAL_STATE__payload in the same response. An agent using a naive extractor would wrongly conclude Cisco documents almost nothing. - Do not confuse this with Cisco's other four MCP servers. Cisco runs Messaging (24 tools), Vidcast (29), Workspaces (16) and Webex Suite (25) at sibling paths on the same host. The Suite server duplicates this one's meeting functions behind a single
webex-manage-meetingdispatcher and adds messaging writes; its Workspaces sibling advertises awebexsquare:adminscope that its documentation page does not mention.
Frequently asked questions
Yes. The webex-create-meeting tool creates a real meeting with a title, time, duration, recurrence, password and an invitee list, and Cisco's documentation says it sends email invitations. This is the sharp difference from the Zoom connector, which reads meeting history and schedules nothing. Treat every create call as an action other people will see.
Yes, on three of its eight tools, and by default. Cisco documents that webex-create-meeting sends email invitations and that webex-delete-meeting sends an optional cancellation email. The underlying Webex REST API exposes a sendEmail flag on create, update and delete whose documented default value is true, so silence in a tool call means mail goes out.
Yes, and Webex documents the deletion as unrecoverable. Cisco's Meetings API states plainly that a deleted meeting cannot be recovered, and that deleting the ID of a meeting series deletes the entire series rather than one occurrence. The same call emails a cancellation notice to the host and invitees unless that behaviour is explicitly turned off.
Yes, as full plain text. Cisco documents webex-list-transcripts as listing transcript metadata and optionally downloading full plain-text transcript content for LLM analysis. That puts every participant's recorded speech into the agent's context, and it needs the meeting:transcripts_read scope. Transcripts are available only for meeting instances that have already ended.
Seven, and the server's own descriptor marks all seven as required rather than optional. They are spark:mcp for the connection plus six meeting scopes covering schedules read, schedules write, participants, summaries, recordings and transcripts. Because schedules write is in the required set, an OAuth connection cannot be granted read-only access to this server.
Only on the token path, not the OAuth path. Cisco documents a WCIT token issued with the spark:mcp scope alone, where the server uses MCP elicitation to request each further scope at tool-call time. Clients that do not support elicitation must use OAuth instead, and the OAuth descriptor requires all seven scopes up front.
An administrator has to switch it on first. Cisco states this MCP server must be enabled by your organization's admin in Webex Control Hub before it can be used. The admin decides in Control Hub which individual tools are available and to which user groups, so the delete and create tools can be withheld from most of the organization.
No, they are different endpoints with different tool surfaces. The Webex Suite server at mcp.webexapis.com/mcp/webex-suite carries 25 tools spanning Meetings, Messaging, Vidcast and Calling, and it collapses create, update and delete into one webex-manage-meeting dispatcher. Its Messaging half can post messages to spaces; this Meetings server cannot.
Sources
- Cisco Webex Meetings MCP Server documentation (retrieved 2026-08-22). All eight tool names, descriptions and the seven-scope map are read from this page's embedded
window.__INITIAL_STATE__payload; the same content is served atdeveloper.webex.com/meeting/docs/meetings-mcp-server. · retrieved 2026-08-22 - Cisco Webex MCP Server Usage Guide, covering WCIT tokens, MCP elicitation, OAuth integration setup and troubleshooting (retrieved 2026-08-22) · retrieved 2026-08-22
- Cisco Webex MCP client setup for Claude Code and Claude Desktop — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Cisco Webex Agentic Apps Admin Approval Guide, risk buckets and per-tool Control Hub enablement (retrieved 2026-08-22) · retrieved 2026-08-22
- Cisco Webex MCP and A2A security best practices, untrusted-input guidance (retrieved 2026-08-22) · retrieved 2026-08-22
- Webex Meetings REST API, Create a Meeting, Update a Meeting and Delete a Meeting, source of the
sendEmaildefault and the unrecoverable-deletion statement — · · (retrieved 2026-08-22, from the OpenAPI specifications embedded in the Meetings documentation payload) · retrieved 2026-08-22 - Webex REST API, List Recordings, List Meeting Transcripts and List Meeting Participants response schemas — · · (retrieved 2026-08-22) · retrieved 2026-08-22
- Cisco Webex sibling MCP servers — Messaging, Vidcast, Webex Suite and Workspaces — · · · (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous
initializetohttps://mcp.webexapis.com/mcp/webex-meetingreturned 401 with awww-authenticatebearer challenge naming the resource metadata document, RFC 9728 metadata athttps://mcp.webexapis.com/.well-known/oauth-protected-resource/mcp/webex-meeting, and authorization server metadata athttps://mcp.webexapis.com/.well-known/oauth-authorization-server(2026-08-22). Control probes at unrelated.well-knownpaths returned empty 404s, so the 200s are genuine rather than a catch-all. · retrieved 2026-08-22 developer.webex.com/robots.txtpermits/mcp/docs/and/meeting/docs/and carries noContent-Signaldirective (retrieved 2026-08-22).developer.webex.com/llms.txtreturns 404. · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Cisco support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Webex Meetings
- Tools
- 8
- Domain
- mcp.webexapis.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.