This is a test environment for integration and development. Visit the production site at apphub.webex.com.

Webex Contact Center MCP Server

Cisco Official Cisco Official; Certified by Cisco

AI-powered flow design, real-time telemetry, and contact center analytics — build, validate, and monitor Webex Contact Center workflows through natural language.

Webex Contact Center MCP Server

Cisco Official Cisco Official; Certified by Cisco
Agentic App by Cisco

AI-powered flow design, real-time telemetry, and contact center analytics — build, validate, and monitor Webex Contact Center workflows through natural language.

Agentic App by Cisco

The Webex Contact Center MCP Server is a Model Context Protocol (MCP) server that enables AI agents and automation tools to securely work with Webex Contact Center capabilities on behalf of authenticated users. It exposes 15 tools across five categories: flow management (list, create, read, save, patch, validate contact center flows using FlowV2), activity and template discovery (activity schemas, event specifications, dynamic choices, starter templates), admin configuration (read and write organizational config resources like entry points, queues, teams, and dial plans), real-time telemetry (webhook subscriptions and WebSocket session provisioning for wallboards), and historical analytics (GraphQL queries against contact summary records). Authentication uses OAuth 2.0 with Webex bearer tokens.

Support

Categories

The Webex Contact Center MCP Server is a Model Context Protocol (MCP) server that enables AI agents and automation tools to securely work with Webex Contact Center capabilities on behalf of authenticated users. It exposes 15 tools across five categories: flow management (list, create, read, save, patch, validate contact center flows using FlowV2), activity and template discovery (activity schemas, event specifications, dynamic choices, starter templates), admin configuration (read and write organizational config resources like entry points, queues, teams, and dial plans), real-time telemetry (webhook subscriptions and WebSocket session provisioning for wallboards), and historical analytics (GraphQL queries against contact summary records). Authentication uses OAuth 2.0 with Webex bearer tokens.