Go-based Model Context Protocol server enabling AI assistants to interact with Cisco Webex APIs. Features messaging tools for rooms, teams, people & webhooks.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"webex": {
"env": {
"WEBEX_PUBLIC_WORKSPACE_API_KEY": "your-webex-token"
},
"args": [
"-env",
"/absolute/path/to/your/webex-mcp-server/.env",
"-all-tools"
],
"command": "/absolute/path/to/your/webex-mcp-server/build/webex-mcp-server"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A high-performance Go implementation of the Webex MCP (Model Context Protocol) Server, providing AI assistants with comprehensive access to Cisco Webex messaging, collaboration, and enterprise features.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@modelcontextprotocol/inspector' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server
An XSS flaw exists in the MCP Inspector local development tool when it renders a redirect URL returned by a remote MCP server. If the Inspector connects to an untrusted server, a crafted redirect can inject script into the Inspector context and, via the built-in proxy, be leveraged to trigger arbitrary command execution on the developer machine. Version 0.16.6 hardens URL handling/validation and prevents script execution. > Thank you to the following researchers for their reports and contributi
MCP Inspector proxy server lacks authentication between the Inspector client and proxy
Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities. Credit: Rémy Marot <bughunters@tenable.com>
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
PubNub Model Context Protocol MCP Server for Cursor and Claude
Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers
MCP server for Voximplant API — call history, users, SMS. 3 tools.
MCP Security Weekly
Get CVE alerts and security updates for Webex Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A high-performance Go implementation of the Webex MCP (Model Context Protocol) Server, providing AI assistants with comprehensive access to Cisco Webex messaging, collaboration, and enterprise features.
make build
Find your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonAdd this configuration:
{
"mcpServers": {
"webex": {
"command": "/absolute/path/to/your/webex-mcp-server/build/webex-mcp-server",
"args": ["-env", "/absolute/path/to/your/webex-mcp-server/.env", "-all-tools"],
"env": {
"WEBEX_PUBLIC_WORKSPACE_API_KEY": "your-webex-token"
}
}
}
}
In Claude, you can now say:
net/http with intelligent connection poolinggit clone https://github.com/raja-aiml/webex-mcp-server.git
cd webex-mcp-server
make deps
# Copy the example environment file
cp .env.example .env
# Edit .env and add your Webex API token
# WEBEX_PUBLIC_WORKSPACE_API_KEY=your_webex_api_token_here
Create a .env file in the project root with the following variables:
# Required: Your Webex API token
WEBEX_PUBLIC_WORKSPACE_API_KEY=your_webex_api_token_here
# Optional: Webex API base URL (default: https://webexapis.com/v1)
WEBEX_API_BASE_URL=https://webexapis.com/v1
# Optional: Server port for HTTP mode (default: 3001)
PORT=3001
This MCP server is optimized for Claude Desktop.
make build
{
"mcpServers": {
"webex": {
"command": "/full/path/to/webex-mcp-server/build/webex-mcp-server",
"args": ["-env", "/full/path/to/webex-mcp-server/.env", "-all-tools"],
"env": {
"WEBEX_PUBLIC_WORKSPACE_API_KEY": "your-token"
}
}
}
}
make run
# or
make mcp-local
make run http
# Check health endpoint
curl http://localhost:3001/health
# Build and run in Docker
make mcp-docker
# Or use docker-compose for HTTP mode
make
... [View full README on GitHub](https://github.com/raja-aiml/webex-mcp-server#readme)