Webex published MCP servers for external AI clients

Verified 2026-09-05 · 49 claims · sources tier 2

Also known as Amazon Quick, Contact Center Operation MCP Server, Vidcast, WCIT, elicitation.

Cisco publishes Model Context Protocol (MCP) servers that allow external artificial intelligence clients and automation tools to interact with Webex capabilities on behalf of authenticated users 20. WarmTransfer's reading of the sources is that Cisco documents 8 of its own MCP servers, covering collaboration, workspaces, customer interaction, and communications infrastructure 24.

Published Webex MCP Servers

WarmTransfer's reading of the sources is that Cisco documents 8 first-party MCP servers: Meetings, Messaging, Vidcast, Workspaces, Webex Suite, Connect CPaaS, Contact Center, and Contact Center Operation 24. Of the 3 servers documented beyond the 5 previously announced as publicly available, 2 are in beta and 1 combines 4 capability areas 25.

The Webex Suite server functions as a single server bringing together meetings, messaging, calling, and video capabilities with 25 tools at 1 address 41. Unlike standalone servers that separate actions, the Webex Suite server consolidates operations; for instance, creating, updating, and deleting a meeting are combined into 1 dispatcher tool rather than 3 42.

The standalone collaboration and device servers expose dedicated tool sets:

• Meetings: Exposes 8 tools covering listing, creating, updating, deleting, status, summary, recordings, and transcripts 29. The meeting summary tool returns AI-generated summary notes and action items for ended meetings and requires the Webex AI Assistant 28.
• Messaging: Exposes 24 tools across messages, spaces, memberships, webhooks, files, and threading, with each operation exposed separately rather than through dispatcher tools 33. Within this server, 2 tools are explicitly described as irreversible: deleting a message is destructive and irreversible, and a deleted space cannot be recovered 32.
• Vidcast: Exposes 29 tools covering video discovery and search, library browsing, content and AI, engagement, and analytics 45.
• Workspaces: Exposes 16 tools, comprising 10 device tools (event history, configuration comparison and listing, configuration schema, template comparison and listing, error code search, device search, and product lifecycle), 5 workspace tools (capacity, popularity, usage, metrics, and search), and 1 location search tool 49.
• Connect CPaaS: Exposes 3 tools for sender identifiers, short message sending, and email sending 22. Numeric limits apply: short message bodies are capped at 1024 characters, while email bodies are capped at 500000 characters within a maximum total message size of 25 megabytes 22. The short message tool distinguishes standard character sets from unicode content, though documentation does not state whether the 1024 character cap changes based on the character set 40. Connect CPaaS addresses vary across tenant regions, maintaining distinct addresses for Canada, Europe, India, Australia, and Singapore on a domain different from every other Webex server 21.

Contact Center Servers

Cisco publishes a Webex Contact Center MCP server in beta, and publishes a second contact centre server, the Contact Center Operation MCP server, also in beta 20​10.

The Contact Center MCP server provides 15 tools covering flow management, activity discovery, validation, choices, events, templates, real-time subscriptions, administrative configuration, and historical analytics 13. Its real-time tool provisions websocket sessions that return a session address and subscription identifier for consuming live queue and agent telemetry in wallboards and supervisor dashboards; this tool is marked destructive and requires a user account context 12. A configuration reading tool spans entry points, business hours, dial plans, dial numbers, skill profiles, auxiliary codes, teams, users, agent profiles, outdial identifiers, and contact service queues via read-only list and get operations 15. Cisco states that guardrails are applied for per-organisation and per-tool rate limits, write payload size, maximum nodes, maximum edges, and downstream service failures, but publishes no figures for any of them 8.

The Contact Center Operation MCP server exposes 25 tools across reporting and search, configuration, flows, routing and staffing, contacts and recordings, and AI and virtual agents 11. Its virtual agent transcript tool retrieves a conversation transcript for 1 contact and states that appropriate scope and entitlement are required because conversation content can be exposed 44.

The 2 contact centre servers name different token issuers: 1 uses the public interface host, while the other points to an identity broker host not named by any other Webex server in the corpus 14.

Authentication and Authorisation Architecture

Webex MCP servers support 2 authorisation methods: a token-based method using a Webex client identity token and a full authorization code integration 43. A Webex client identity token is issued with only the platform connection scope, requesting additional tool scopes at run time 46. Cisco defines elicitation as a protocol capability by which a server requests information from a user during a tool call, using it in token-based connections to ask users to authorise additional scopes in real time 26. Cisco states that the token-based method works only with clients supporting elicitation; clients without support must use the authorization code method, or fail on any tool requiring more than the base connection scope 19.

For both Meetings and Workspaces, an organisation administrator must enable the server in Control Hub before any user can connect, which is a separate gate from the user's own scope grant 1. Workspaces additionally requires its agentic app and associated tools to be enabled in Control Hub prior to server setup 48, and utilizes administrator scopes for everything beyond the platform connection 47. Conversely, the Meetings server forwards the client's own bearer token directly to Webex interfaces on behalf of the user rather than leveraging a service identity 30.

Scopes vary by server and are documented on their respective product pages rather than in a consolidated reference 39:

• Meetings: Requires 7 scopes (platform connection, schedule read/write, and read scopes for participants, summaries, recordings, and transcripts) 31.
• Contact Center Operation: Requires 4 scopes (platform connection, configuration read, people read, and contact centre user) 9.

WarmTransfer's reading of the sources is that every scope named across Meetings, Workspaces, and both contact centre server pages appears in the Webex scope catalogue with matching descriptions, including the platform connection scope for accessing servers hosted on the agentic platform 27.

Supported External Clients and Architecture

Cisco provides per-client connection guides for 8 AI clients: Amazon Quick, Claude Code, Claude Desktop, Codex, Copilot Studio, Cursor, Gemini CLI, and Visual Studio Code 23. Amazon Quick is Amazon's business intelligence product—whose console is still served from its former name's domain—and connecting to it requires an enterprise subscription 2. WarmTransfer's reading of the sources is that the platform Cisco names Circuit is served from a Cisco domain and has no documentation entry among the per-client guides 16.

Separately, the Cisco Onboarded MCP Servers page lists 9 third-party servers that Webex AI clients call out to, rather than servers external clients reach, and Cisco states it does not own them 18. The 9 Cisco onboarded third-party servers are Box, Calendly, Figma, GitHub, Google Calendar, HubSpot, Atlassian Jira, Miro, and PagerDuty 34. Of these, 8 use authorization code flows, whereas PagerDuty uses a user token 38.

Design Patterns and Governance Gaps

WarmTransfer's reading of the sources is that Cisco's own servers use at least 3 tool naming conventions: underscores without a prefix on Workspaces, hyphens with a Webex prefix on Meetings and Messaging, and hyphens with a contact centre prefix on both contact centre servers 37. Cisco's best practices guide tells third-party developers to name tools using a dotted domain, entity, and verb pattern of at most 60 characters and never to rename a published tool; WarmTransfer's reading of the sources is that none of Cisco's own servers uses that pattern 17.

While Cisco directs third-party developers to encrypt data at rest with per-tenant keys, redact personal information from telemetry, define retention and deletion policies, and log audit records before an action executes 3, WarmTransfer's reading of the sources is that no read source states what Cisco logs, audits, or does with data when an external client calls a Cisco-run Webex server 35. Furthermore, WarmTransfer's reading of the sources is that no numeric rate limits are published for any Webex MCP server, as limits referenced in page payloads belong to underlying interface rate limits 36.

Bring Your Own Virtual Agent (BYOVA) is filed under Cisco's MCP site navigation taxonomy, but its body contradicts this classification 4. BYOVA is a remote procedure call and websocket contract between Webex Contact Center and a partner-hosted connector, never using MCP terminology in its documentation 5. BYOVA authentication requires data source read and write scopes that do not appear under those names in Webex's scope catalogue 7, and WarmTransfer's reading of the sources is that BYOVA documentation states no cap on connectors or data sources per organisation 6.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, Cisco Webex, Cisco Webex Meetings, Cisco Vidcast, and Cisco Webex Connect across cloud deployments, verified as of 2026-09-05. The Connect CPaaS MCP server's deployment addresses are specific to Canada, Europe, India, Australia, and Singapore tenants 21. The Contact Center and Contact Center Operation servers apply to environments supporting their beta release status 20​10.

What remains uncertain

The short message tool does not state whether the 1024 character cap changes based on character set 40. Cisco publishes no figure for any of the Contact Center MCP server guardrails 8. WarmTransfer's reading of the sources is that no numeric rate limit is published for any Webex Model Context Protocol server 36. WarmTransfer's reading of the sources is that the platform Cisco names Circuit is served from a Cisco domain and has no documentation entry among the per-client connection guides 16.

WarmTransfer. (2026, September 5). Webex published MCP servers for external AI clients. WarmTransfer. https://warmtransfer.net/knowledge/webex-mcp-servers

@misc{warmtransfer-webex-mcp-servers,
  title  = {Webex published MCP servers for external AI clients},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-mcp-servers},
  note   = {Verified 2026-09-05}
}