Thanks for your feedback.

September 2026

Group-Level Access

Use Limited access to choose which groups can discover an MCP server's enabled functions. For example, you can select a support team and a pilot group, or give individual functions different audiences. The MCP server's own authentication and authorization controls still apply when a function is invoked.

For more information, see the Group-Level Access section at Provisioning on Control Hub

Deprecation Labels in Control Hub

Control Hub supports end-to-end lifecycle management for MCP tools, resources, and prompts. Deprecated and Retired labels help administrators identify affected capabilities. Where available, Control Hub also displays retirement dates, replacement capabilities, and migration guidance so administrators can plan migrations before a capability is retired.

Refreshing MCP Server Tools in Control Hub

The backend caches each MCP server's tool list for up to one hour. During this period, requests from Control Hub administrators or SDK clients return the cached list. After the cache expires, the next backend request retrieves the latest tools from the MCP server.

June 2026

Agentic Apps Category

A dedicated section in Webex App Hub for discovering and deploying AI-native applications that use Model Context Protocol and Agent-to-Agent (A2A) communication. These apps leverage MCP servers to provide standardized, secure connections between AI assistants and your business tools.

Webex MCP Servers for External Agents

Webex now exposes its own MCP servers, allowing external AI agents built on platforms like Claude, ChatGPT, or custom solutions to access the following:

• Meeting context - transcripts, recordings, participants, and summaries
• Messaging history - space conversations, direct messages, and team communications
• Contact Center data - queue states, call transcripts, agent status, and routing context*
• Device intelligence - workspace sensors, room booking, and environmental controls. For m ore information, see Workspaces MCP server in Control Hub.

External agents can now tap into Webex capabilities through standardized protocols without building custom API integrations.

External MCP Servers for Webex Agents

Webex AI agents can now consume external MCP servers from partners and third-party providers, giving them instant access to:

• CRM systems - Salesforce, HubSpot, Microsoft Dynamics
• Ticketing platforms - Jira, ServiceNow, Zendesk
• Knowledge bases - Confluence, SharePoint, Notion
• Business tools - Airtable, Miro, PagerDuty, Slack

Onboarding for some of the MCP servers listed above is still in progress, and they are not yet available in Webex App Hub.

This bidirectional approach means your Webex AI agents become more powerful while your existing AI investments gain Webex collaboration intelligence.

AGNTCY Ecosystem Layer

AGNTCY serves as the orchestration and governance foundation for the agentic ecosystem:

• Agent Registry - Discover available agents and their capabilities across your organization
• Security Validation - Every tool invocation is scanned by MCP Scanner for threats and policy violations
• Unified Governance - Centralized access controls, audit logging, and compliance enforcement
• Marketplace - Browse, evaluate, and deploy certified MCP servers from Webex and partners

For Administrators

1. Explore Agentic Apps—Visit Webex App Hub and browse the new Agentic Apps category
2. Review MCP Servers—Check available internal Webex and external partner MCP servers
3. Enable Users—Approve specific MCP servers for your organization. Enable or disable supported MCP servers for your organization.

For Developers

1. Access Developer Portal—Visit developer.webex.com and navigate to the MCP section
2. Review Documentation—Read MCP server setup guides and tool schemas
3. Use AI Assistant—Generate code snippets for your integration use case
4. Test in Sandbox—Validate your MCP server in the developer sandbox environment
5. Submit for Certification—Request review to publish in Webex App Hub marketplace

For questions or support, contact your Webex account team or visit the Webex for Developers.