# Webex published MCP servers for external AI clients Canonical: https://warmtransfer.net/knowledge/webex-mcp-servers Last verified: 2026-09-05 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 Applies to: Cisco Webex Contact Center, Cisco Webex, Cisco Webex Meetings, Cisco Vidcast, and Cisco Webex Connect. Deployments: cloud. Sources checked 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]. ## Sources [^1]: Both the Meetings and Workspaces servers state that 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. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Prerequisites. Checked 2026-09-05. [^2]: The platform Cisco names 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. Source: [Connect Amazon Quick to a Webex MCP server](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers-amazon-quick), Prerequisites and the console sign-in step. Checked 2026-09-05. [^3]: Cisco's best practices guide for building servers tells third-party developers to encrypt at rest with per-tenant keys, redact personal information from logs, metrics and telemetry, define retention policies with expiry and secure deletion, and log audit records before an action executes. Source: [Best Practices for Building MCP and A2A Servers](https://developer.webex.com/mcp/docs/best-practices-for-building-mcp-and-a2a-servers), data handling and audit sections. Checked 2026-09-05. [^4]: Cisco's own site taxonomy files Bring Your Own Virtual Agent under its Model Context Protocol navigation category, which its own content contradicts. Source: [Bring Your Own Virtual Agent](https://developer.webex.com/mcp/docs/bring-your-own-virtual-agent), embedded page state navigation category, against the article body. Checked 2026-09-05. [^5]: Bring Your Own Virtual Agent is a remote procedure call and websocket contract between Webex Contact Center and a partner-hosted virtual agent connector, and its documentation never uses Model Context Protocol terminology in its body. Source: [Bring Your Own Virtual Agent](https://developer.webex.com/mcp/docs/bring-your-own-virtual-agent), whole article body. Checked 2026-09-05. [^6]: The Bring Your Own Virtual Agent documentation states no maximum number of connectors or data sources per organisation (inferred). Source: [Bring Your Own Virtual Agent](https://developer.webex.com/mcp/docs/bring-your-own-virtual-agent), whole article. Checked 2026-09-05. [^7]: Bring Your Own Virtual Agent authentication requires a service application with data source read and write scopes that do not appear under those names in the scope catalogue the same payload carries. Source: [Bring Your Own Virtual Agent](https://developer.webex.com/mcp/docs/bring-your-own-virtual-agent), authentication setup step, against the embedded scope catalogue. Checked 2026-09-05. [^8]: Cisco states that the Contact Center MCP server applies guardrails for per-organisation and per-tool rate limits, write payload size, maximum nodes, maximum edges and downstream service failures, and publishes no figure for any of them. Source: [Contact Center MCP Server](https://developer.webex.com/mcp/docs/contact-center-mcp-server), Access and Guardrails. Checked 2026-09-05. [^9]: The Contact Center Operation server requires 4 scopes, the platform connection scope plus a configuration read scope, a people read scope and a contact centre user scope. Source: [Contact Center Operation MCP Server](https://developer.webex.com/mcp/docs/contact-center-operation-mcp-server), Scopes section. Checked 2026-09-05. [^10]: Cisco publishes a second contact centre server, the Contact Center Operation MCP server, covering reporting, agent activity, configuration, routing, flow definitions, contact journeys, recordings and artificial intelligence data, and it is in beta. Source: [Contact Center Operation MCP Server](https://developer.webex.com/mcp/docs/contact-center-operation-mcp-server), What is Contact Center Operation MCP Server. Checked 2026-09-05. [^11]: The Contact Center Operation MCP server exposes 25 tools across reporting and search, configuration, flows, routing and staffing, contacts and recordings, and artificial intelligence and virtual agents. Source: [Contact Center Operation MCP Server](https://developer.webex.com/mcp/docs/contact-center-operation-mcp-server), Tools section. Checked 2026-09-05. [^12]: The real-time tool provisions websocket sessions returning a session address and subscription identifier for a client to consume live queue and agent telemetry, is described as used for wallboards and supervisor dashboards, and is marked destructive and requiring a user account context. Source: [Contact Center MCP Server](https://developer.webex.com/mcp/docs/contact-center-mcp-server), Tools table, real time and subscriptions row. Checked 2026-09-05. [^13]: The Contact Center MCP server exposes 15 tools covering flow management, activity discovery, validation, choices, events, templates, real-time subscriptions, administrative configuration and historical analytics. Source: [Contact Center MCP Server](https://developer.webex.com/mcp/docs/contact-center-mcp-server), Tools section. Checked 2026-09-05. [^14]: The 2 contact centre servers name different token issuers, 1 using the public interface host and the other an identity broker host that no other Webex server in the corpus names. Source: [Contact Center Operation MCP Server](https://developer.webex.com/mcp/docs/contact-center-operation-mcp-server), Authentication sections of both contact centre server pages. Checked 2026-09-05. [^15]: A configuration reading tool covers entry points, business hours, dial plans, dial numbers, skill profiles, auxiliary codes, teams, users, agent profiles, outdial identifiers and contact service queues, supports list and get operations, and is marked read-only. Source: [Contact Center MCP Server](https://developer.webex.com/mcp/docs/contact-center-mcp-server), Tools table, administrative configuration row. Checked 2026-09-05. [^16]: The platform Cisco names Circuit is served from a Cisco domain and has no documentation entry among the per-client connection guides, unlike every other named client (inferred). Source: [Cisco Onboarded MCP Servers](https://developer.webex.com/mcp/docs/cisco-onboarded-mcp-servers), the what's new entry naming it, against the per-client guide list. Checked 2026-09-05. [^17]: Cisco tells third-party developers to name tools in a dotted domain, entity and verb pattern of at most 60 characters and never to rename a published tool, and none of Cisco's own servers uses that pattern (inferred). Source: [Best Practices for Building MCP and A2A Servers](https://developer.webex.com/mcp/docs/best-practices-for-building-mcp-and-a2a-servers), naming conventions table, against Cisco's own server tool tables. Checked 2026-09-05. [^18]: The page titled Cisco Onboarded MCP Servers lists 9 third-party servers that Webex artificial intelligence clients call out to, not Webex servers an external client reaches, and Cisco states it does not own them. Source: [Cisco Onboarded MCP Servers](https://developer.webex.com/mcp/docs/cisco-onboarded-mcp-servers), Overview. Checked 2026-09-05. [^19]: Cisco states that the token-based method works only with clients supporting elicitation and that a client without it must use the authorization code method instead, failing on any tool requiring more than the connection scope. Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), token-based authentication note. Checked 2026-09-05. [^20]: Cisco publishes a Webex Contact Center MCP server that lets artificial intelligence agents and automation tools work with contact centre capabilities on behalf of authenticated users, and it is in beta. Source: [Contact Center MCP Server](https://developer.webex.com/mcp/docs/contact-center-mcp-server), What is Contact Center MCP Server. Checked 2026-09-05. [^21]: The Connect CPaaS server's address varies by the customer's Webex Connect tenant region, with distinct addresses for Canada, Europe, India, Australia and Singapore, on a different domain from every other Webex server. Source: [Connect CPaaS MCP Server](https://developer.webex.com/mcp/docs/connect-mcp-server), server address table. Checked 2026-09-05. [^22]: The Connect CPaaS server exposes 3 tools for sender identifiers, short message sending and email sending, and publishes numeric bounds: a short message body of at most 1024 characters and an email body of at most 500000 characters within a total message size of at most 25 megabytes. Source: [Connect CPaaS MCP Server](https://developer.webex.com/mcp/docs/connect-mcp-server), Tools table. Checked 2026-09-05. [^23]: Cisco names 8 artificial intelligence clients with per-client connection guides: Amazon Quick, Claude Code, Claude Desktop, Codex, Copilot Studio, Cursor, Gemini CLI and Visual Studio Code. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Connect to your MCP Client section. Checked 2026-09-05. [^24]: Cisco documents 8 of its own Model Context Protocol servers: Meetings, Messaging, Vidcast, Workspaces, Webex Suite, Connect CPaaS, Contact Center and Contact Center Operation (inferred). Source: [Webex Suite MCP Server](https://developer.webex.com/mcp/docs/webex-suite-mcp-server), the per-server documentation pages and the site navigation. Checked 2026-09-05. [^25]: Of the 3 Webex Model Context Protocol servers documented beyond the 5 previously announced as publicly available, 2 are in beta and 1 combines four capability areas. Source: [Webex Suite MCP Server](https://developer.webex.com/mcp/docs/webex-suite-mcp-server), the per-server documentation pages and the site navigation. Checked 2026-09-05. [^26]: Cisco defines elicitation as a protocol capability by which a server requests information from the user during a tool call, and states that a token-based connection uses it to ask the user to authorise additional scopes in real time. Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), what is MCP elicitation. Checked 2026-09-05. [^27]: Every scope named across the Meetings, Workspaces and both contact centre server pages appears in the Webex scope catalogue with a matching description, including a platform connection scope described as accessing servers hosted on the agentic platform (inferred). Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), server scope tables against the embedded scope catalogue. Checked 2026-09-05. [^28]: The meeting summary tool returns artificial intelligence generated summary notes and action items for ended meetings and requires the Webex AI Assistant. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Tools table, summary row. Checked 2026-09-05. [^29]: The Meetings server exposes 8 tools covering the meeting lifecycle: listing, creating, updating, deleting, status, summary, recordings and transcripts. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Tools table. Checked 2026-09-05. [^30]: The Meetings server forwards the client's own bearer token to the Webex interfaces and calls them on behalf of the authenticated user rather than using a service identity. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Authentication section. Checked 2026-09-05. [^31]: The Meetings server requires 7 scopes: the platform connection scope plus read and write scopes for schedules and read scopes for participants, summaries, recordings and transcripts. Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), Scopes table. Checked 2026-09-05. [^32]: 2 Messaging tools describe themselves as irreversible: deleting a message is destructive and irreversible and a deleted space cannot be recovered. Source: [Messaging MCP Server](https://developer.webex.com/mcp/docs/messaging-mcp-server), Tools table, delete message and delete space rows. Checked 2026-09-05. [^33]: The Messaging server exposes 24 tools across messages, spaces, memberships, webhooks, files and threading, with every operation exposed separately rather than through dispatcher tools. Source: [Messaging MCP Server](https://developer.webex.com/mcp/docs/messaging-mcp-server), Tools section. Checked 2026-09-05. [^34]: The 9 Cisco onboarded third-party servers are Box, Calendly, Figma, GitHub, Google Calendar, HubSpot, Atlassian Jira, Miro and PagerDuty, each published with its own address. Source: [Cisco Onboarded MCP Servers](https://developer.webex.com/mcp/docs/cisco-onboarded-mcp-servers), per-server entries. Checked 2026-09-05. [^35]: No source read states what Cisco does with data, what it logs, or what it audits when an external client calls a Cisco-run Webex server (inferred). Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), whole-document scan of the thirteen sources read for this topic. Checked 2026-09-05. [^36]: No numeric rate limit is published for any Webex Model Context Protocol server; the general Webex interface rate limit that appears in 1 server page's payload belongs to the underlying interfaces rather than to the server (inferred). Source: [Webex Meetings MCP Server](https://developer.webex.com/meeting/docs/meetings-mcp-server), whole-page scan and the embedded interface reference in the same payload. Checked 2026-09-05. [^37]: 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 (inferred). Source: [Workspaces MCP Server](https://developer.webex.com/mcp/docs/workspaces-mcp-server), tool tables of the Workspaces Meetings Messaging and contact centre server pages. Checked 2026-09-05. [^38]: 8 of the 9 Cisco onboarded servers use the authorization code method and PagerDuty uses a user token instead. Source: [Cisco Onboarded MCP Servers](https://developer.webex.com/mcp/docs/cisco-onboarded-mcp-servers), per-server authentication type lines. Checked 2026-09-05. [^39]: Cisco directs a developer to the agentic apps listing and then to each server's own product page to find its required scopes, so there is no single scope reference across servers. Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), scopes step of the integration setup. Checked 2026-09-05. [^40]: The short message tool distinguishes a standard character set from unicode content and does not state whether the 1024 character cap changes with the character set. Source: [Connect CPaaS MCP Server](https://developer.webex.com/mcp/docs/connect-mcp-server), Tools table, short message row. Checked 2026-09-05. [^41]: The Webex Suite server is a single server bringing together meetings, messaging, calling and video capabilities with 25 tools at 1 address. Source: [Webex Suite MCP Server](https://developer.webex.com/mcp/docs/webex-suite-mcp-server), What is Webex Suite MCP Server and the Tools section. Checked 2026-09-05. [^42]: The Webex Suite server consolidates operations that the standalone servers expose separately, so that creating, updating and deleting a meeting are 1 dispatcher tool rather than 3. Source: [Webex Suite MCP Server](https://developer.webex.com/mcp/docs/webex-suite-mcp-server), Tools table, meetings rows, against the standalone Meetings server's tools table. Checked 2026-09-05. [^43]: Webex Model Context Protocol servers support 2 authorisation methods: a token-based method using a Webex client identity token and a full authorization code integration. Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), authorisation section. Checked 2026-09-05. [^44]: The virtual agent transcript tool retrieves a conversation transcript for 1 contact and states that it requires appropriate scope and entitlement because it can expose conversation content. Source: [Contact Center Operation MCP Server](https://developer.webex.com/mcp/docs/contact-center-operation-mcp-server), Tools table, artificial intelligence and virtual agents row. Checked 2026-09-05. [^45]: The Vidcast server exposes 29 tools covering video discovery and search, library browsing, content and artificial intelligence, engagement and analytics. Source: [Vidcast MCP Server](https://developer.webex.com/mcp/docs/vidcast-mcp-server), Tools section. Checked 2026-09-05. [^46]: A Webex client identity token is issued with only the platform connection scope, and any additional scope a tool needs is requested at run time. Source: [Connect to Webex Agentic MCP Servers](https://developer.webex.com/mcp/docs/webex-agentic-mcp-servers), token-based authentication section. Checked 2026-09-05. [^47]: The Workspaces server uses administrator scopes for everything but the platform connection, so access is gated by organisation administration rather than by an individual user's own permissions. Source: [Workspaces MCP Server](https://developer.webex.com/mcp/docs/workspaces-mcp-server), Scopes table and Authentication section. Checked 2026-09-05. [^48]: The Workspaces server additionally requires the Workspaces agentic app and its tools to be enabled in Control Hub before the server can be set up. Source: [Workspaces MCP Server](https://developer.webex.com/mcp/docs/workspaces-mcp-server), What is Workspaces MCP Server. Checked 2026-09-05. [^49]: The Workspaces server exposes 16 tools: 10 device tools covering event history, configuration comparison and listing, configuration schema, template comparison and listing, error code search, device search and product lifecycle, 5 workspace tools covering capacity, popularity, usage, metrics and search, and 1 location search tool. Source: [Workspaces MCP Server](https://developer.webex.com/mcp/docs/workspaces-mcp-server), Tools tables. Checked 2026-09-05.