Webex MCP Server

Webex MCP Server is an MCP server that connects AI assistants to Cisco Webex messaging APIs to handle organizational collaboration workflows. Designed for developers, IT administrators, and operations teams using MCP-compatible tools like Claude Desktop, it allows large language models to interact directly with spaces, teams, and users. The server exposes 52 tools that cover reading, creating, and modifying core Webex entities. Assistants can post messages, manage room tabs, configure direct or group spaces, handle team memberships, inspect user profiles, and register webhooks for event automation. It also supports enterprise-grade capabilities like Enterprise Content Management folders and attachment actions. By standardizing Webex operations under the Model Context Protocol, the server lets agents handle automated operational tasks, from sending system notifications to managing access permissions and provisioning incident triage spaces. It supports both local STDIO execution and remote HTTP transport via Node.js or Docker.

Category: Communication & Messaging

Tags: cisco, collaboration, messaging, webex

Visit Webex MCP Server

How to install and configure Webex MCP Server

To install and configure the Webex MCP Server with Claude Desktop, follow these steps: 1. Obtain an API access token from developer.webex.com and note your Webex account email. 2. Build the Docker container locally: bash git clone https://github.com/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server cd webex-messaging-mcp-server docker build -t webex-mcp-server . 3. Open your Claude Desktop configuration file and add the server definition: json { "mcpServers": { "webex-messaging": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "WEBEX_PUBLIC_WORKSPACE_API_KEY", "-e", "WEBEX_USER_EMAIL", "-e", "WEBEX_API_BASE_URL", "webex-mcp-server" ], "env": { "WEBEX_USER_EMAIL": "your.email@company.com", "WEBEX_API_BASE_URL": "https://webexapis.com/v1", "WEBEX_PUBLIC_WORKSPACE_API_KEY": "your_token_here" } } } } 4. Replace your_token_here and your.email@company.com with your actual Webex credentials and restart Claude Desktop.

What you can do with Webex MCP Server

• Generating and provisioning dedicated incident-response spaces, automatically adding relevant on-call engineers by their Webex user directory profiles. * Dispatching automated system alerts, customer incident notifications, and status reports to predefined team spaces and channels. * Managing organizational governance by querying, adding, or removing user memberships across enterprise Webex teams and spaces. * Monitoring and managing Webex webhook subscriptions to automate event-driven integrations with other external developer services. * Organizing enterprise workspaces by attaching files, configuring ECM folders, and managing custom Webex room tabs.

Key facts

• https://github.com/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server
• Communication & Messaging
• cisco, collaboration, messaging, webex

Part of MCP Servers

What can Webex MCP Server do?

Webex MCP Server provides 52 distinct tools covering Cisco Webex messaging APIs. It allows AI clients to compose and delete messages, manage rooms and teams, adjust memberships, look up user profiles in the directory, manage webhooks, and interface with enterprise features like room tabs and ECM folders.

How do I install Webex MCP Server?

You can clone the repository from GitHub and run it using Node.js 18 or higher with npm install and node mcpServer.js. Alternatively, you can build the provided Dockerfile and launch the container in STDIO mode or HTTP mode.

Which MCP clients work with Webex MCP Server?

Webex MCP Server works with any client supporting the Model Context Protocol, including Claude Desktop and custom agents. It supports both standard input/output STDIO mode and HTTP mode with StreamableHTTP transport.

How do I handle token expiration with Webex MCP Server?

Personal developer tokens from the Webex developer portal expire every 12 hours. You must obtain a fresh bearer token from developer.webex.com, remove the Bearer prefix, and update the WEBEX_PUBLIC_WORKSPACE_API_KEY variable in your configuration or environment file.