Webex MCP

webex-mcp

Maintainers: see Publishing a release for GitHub Releases and npm setup.

MCP server for Cisco Webex Messaging — connect AI assistants to Webex spaces, messages, and people.

Minimal MCP server that exposes Webex messaging tools over stdio. Works with Cursor, Claude Desktop, Codex, Claude Code, OpenCode, and other MCP clients.

Features

• Full core Webex Messaging API coverage: spaces, messages, memberships, people, teams, webhooks, attachment actions, and file downloads
• Received attachments for agents: images inline, text paged inline, ZIP/JAR listings, and saving any file to local disk
• Search spaces and messages by keyword (client-side scan)
• Bearer token authentication via webex-node SDK with REST fallback for select endpoints
• OAuth 2.0 Integration login with automatic token refresh

Requirements

• Node.js >= 18
• Webex Bot access token or Webex Integration (OAuth) — developer.webex.com

Quick start

Option A — Bot token

# Run via npx (recommended)

npx -y @yuryev89/webex-mcp@latest --token YOUR_ACCESS_TOKEN

Or install globally

npm install -g @yuryev89/webex-mcp webex-mcp --token YOUR_ACCESS_TOKEN

Option B — OAuth Integration

# 1. Set credentials (or use a .env file in your working directory)

export WEBEX_CLIENT_ID="your-client-id" export WEBEX_CLIENT_SECRET="your-client-secret"

2. Authenticate once (opens browser)

npx -y @yuryev89/webex-mcp@latest login

3. Start MCP server (reads saved tokens, auto-refreshes)

npx -y @yuryev89/webex-mcp@latest

Cursor configuration

Bot token

{

"mcpServers": { "webex": { "command": "bash", "args": [ "-lc", "npx -y @yuryev89/webex-mcp@latest --token \"$WEBEX_ACCESS_TOKEN\"" ], "env": { "WEBEX_ACCESS_TOKEN": "YOUR_BOT_ACCESS_TOKEN" } } } }

OAuth Integration

{

"mcpServers": { "webex": { "command": "npx", "args": ["-y", "@yuryev89/webex-mcp@latest"], "env": { "WEBEX_CLIENT_ID": "YOUR_CLIENT_ID", "WEBEX_CLIENT_SECRET": "YOUR_CLIENT_SECRET" } } } }

Run npx -y @yuryev89/webex-mcp@latest login once before starting Cursor (with WEBEX_CLIENT_ID and WEBEX_CLIENT_SECRET set).

Codex configuration

Add one of the following configurations to ~/.codex/config.toml (merge it with any existing configuration).

Bot token

[mcp_servers.webex]

command = "npx" args = ["-y", "@yuryev89/webex-mcp@latest"]

[mcp_servers.webex.env] WEBEX_ACCESS_TOKEN = "YOUR_BOT_ACCESS_TOKEN"

OAuth Integration

Complete Option B — OAuth Integration first, then use:

[mcp_servers.webex]

command = "npx" args = ["-y", "@yuryev89/webex-mcp@latest"]

[mcp_servers.webex.env] WEBEX_CLIENT_ID = "YOUR_CLIENT_ID" WEBEX_CLIENT_SECRET = "YOUR_CLIENT_SECRET"

Alternatively, keep credentials in your shell environment and replace the [mcp_servers.webex.env] table with env_vars = ["WEBEX_ACCESS_TOKEN"] inside [mcp_servers.webex] (or ["WEBEX_CLIENT_ID", "WEBEX_CLIENT_SECRET"] for OAuth). Start Codex from that shell.

Run codex mcp list to verify registration, then use /mcp in Codex to inspect the active server.

Reference: Codex MCP documentation.

Claude Code configuration

The following commands register Webex for your user account across projects. Choose one authentication mode.

Bot token

claude mcp add --scope user \

--env WEBEX_ACCESS_TOKEN=YOUR_BOT_ACCESS_TOKEN \ --transport stdio webex -- npx -y @yuryev89/webex-mcp@latest

OAuth Integration

Complete Option B — OAuth Integration first, then register:

claude mcp add --scope user \

--env WEBEX_CLIENT_ID=YOUR_CLIENT_ID \ --env WEBEX_CLIENT_SECRET=YOUR_CLIENT_SECRET \ --transport stdio webex -- npx -y @yuryev89/webex-mcp@latest

Run claude mcp list or claude mcp get webex to check the connection. Inside Claude Code, use /mcp to inspect status and tools. To switch modes, remove the existing entry with claude mcp remove --scope user webex, then register it again.

Reference: Claude Code MCP documentation.

OpenCode configuration

Merge one of these examples into opencode.json in your project, or ~/.config/opencode/opencode.json for all projects.

Bot token

{

"$schema": "https://opencode.ai/config.json", "mcp": { "webex": { "type": "local", "command": ["npx", "-y", "@yuryev89/webex-mcp@latest"], "enabled": true, "environment": { "WEBEX_ACCESS_TOKEN": "{env:WEBEX_ACCESS_TOKEN}" } } } }

Set WEBEX_ACCESS_TOKEN in your environment before launching OpenCode; {env:...} reads that variable.

OAuth Integration

Complete Option B — OAuth Integration first, then use:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "webex": { "type": "local", "command": ["npx", "-y", "@yuryev89/webex-mcp@latest"], "enabled": true, "environment": { "WEBEX_CLIENT_ID": "{env:WEBEX_CLIENT_ID}", "WEBEX_CLIENT_SECRET": "{env:WEBEX_CLIENT_SECRET}" } } } }

Keep WEBEX_CLIENT_ID and WEBEX_CLIENT_SECRET exported when launching OpenCode. Run opencode mcp list to check the server.

References: OpenCode MCP documentation and configuration.

Client setup notes

• Each client starts the server as a local stdio process; no separate server terminal or HTTP URL is needed.
• OAuth login is handled by npx -y @yuryev89/webex-mcp@latest login. Run it under the same OS user and token-store configuration as the client. Client-native MCP OAuth login commands do not replace this step.
• For OAuth, remove WEBEX_ACCESS_TOKEN from the client configuration, inherited environment, and any loaded .env: a static token takes precedence over saved OAuth tokens.
• Replace credential placeholders locally. Keep real credentials out of version control; CLI arguments may also be retained in shell history.
• Ensure Node.js and npx are available to the client, then restart it after configuration changes.
• Try: "Use Webex to list my spaces." For a message search, identify a space first; webex_search_messages searches one space at a time.

CLI options

Tools

Spaces

Messages

Sending file attachments

Use webex_create_message with files for publicly accessible HTTP(S) URLs:

{

"roomId": "SPACE_ID", "text": "Here is the report", "files": ["https://example.com/report.pdf"] }

For a local file, use filePath instead. The server uploads its contents using multipart; the file must be on the machine running the MCP server, with an absolute path and a size of at most 100 MB:

{

"toPersonEmail": "colleague@example.com", "filePath": "/absolute/path/to/report.pdf" }

On Windows, use an absolute Windows path such as C:\\Reports\\report.pdf. Text and markdown are optional when attaching a file. files must be nonempty and cannot be combined with filePath. Recipient fields (roomId, toPersonId, toPersonEmail) and parentId for thread replies work as with text messages. URL downloads and attachment limits are enforced by Webex; private URLs requiring additional credentials cannot be used as public file URLs. See the Webex attachment guide.

Files

Reading received attachments

What webex_download_file returns depends on the file:

For PDF and Office documents, save the file and open it with the client's own tools (many agents read PDFs and images directly; use a script for docx/xlsx). Saved files go to / / , where the download dir is WEBEX_DOWNLOAD_DIR or ~/.cache/webex-mcp/downloads. Names are taken from Webex, decoded and made safe for the file system; saving again replaces the file, and webex_save_message_files adds (1) to same-named files of one message. The body streams to .part and is renamed only when complete. Treat saved files as untrusted input: open or list them, never run them.

If Webex is still virus-scanning a file it answers 423 Locked; downloads wait for Retry-After (up to 10 s) and retry three times before failing.

Memberships

People

Teams

| `webex