Webex Messaging MCP Server

A comprehensive MCP server providing AI assistants with full access to Cisco Webex messaging capabilities including messages, rooms, teams, people

Local serverstdioTypeScript

What is the Webex Messaging MCP server?

Webex messaging mcp server lets Claude, Cursor and other MCP clients work with Webex Messaging directly. A comprehensive MCP server providing AI assistants with full access to Cisco Webex messaging capabilities including messages, rooms, teams, people, webhooks, and enterprise features.

What Webex Messaging does

A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to Cisco Webex messaging capabilities.

This MCP server enables AI assistants to interact with Webex messaging through 52 different tools covering:

Key capabilities

  • Complete Webex API Coverage: 52 tools covering all major messaging operations
  • Docker Support: Production-ready containerization
  • Dual Transport: Both STDIO and HTTP (StreamableHTTP) modes
  • Enterprise Ready: Supports Cisco enterprise authentication
  • Type Safe: Full TypeScript/JavaScript implementation with proper error handling
  • Centralized Configuration: Easy token and endpoint management

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Installation — 1. Clone and install dependencies: bash git clone cd webex-messaging-mcp-server npm install

Installing the webex messaging mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 4 environment variables: WEBEX_USER_EMAIL, WEBEX_API_BASE_URL, WEBEX_PUBLIC_WORKSPACE_API_KEY, GEMINI_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Node.js 18+ (20+ recommended). Warning: if you run with a lower version of Node, fetch won't be present. Tools use fetch to make HTTP calls. To work around this, you can modify the tools to use node-fetch instead. Make sure that node-fetch is installed as a dependency and then import it as fetch into each tool file. - Docker (optional, for containerized deployment) - Webex API token

Where it fits

Communication servers earn their keep on volume — summarising channels and threads that would otherwise cost you an hour of scrollback. Webex Messaging sits in that group, and the shape of its toolset — Prerequisites, Installation — tells you what it is really for. Worth comparing against the other communication servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by Kashyap-AI-ML-Solutions, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the webex messaging mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
Installation1. **Clone and install dependencies:** bash git clone <repository-url> cd webex-messaging-mcp-server npm install

How to install the Webex Messaging MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 18+ (20+ recommended). Warning: if you run with a lower version of Node, fetch won't be present. Tools use fetch to make HTTP calls. To work around this, you can modify the tools to use node-fetch instead. Make sure that node-fetch is installed as a dependency and then import it as fetch into each tool file. - Docker (optional, for containerized deployment) - Webex API token
VariableDescriptionRequired
WEBEX_USER_EMAILConfiguration value read at startup.Optional
WEBEX_API_BASE_URLEndpoint or connection string the server talks to.Yes
WEBEX_PUBLIC_WORKSPACE_API_KEYCredential the server authenticates with.Yes
GEMINI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Webex Messaging to Prerequisites.
  • Use Webex Messaging to Installation.

Frequently asked questions

It connects Webex Messaging to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, Installation) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Webex Messaging directly.