Webex MCP

io.github.yuryev89Published by GitHub account yuryev89v0.3.0Updated Nov 6, 2026

Cisco Webex MCP server for messages, spaces, teams, people, webhooks and attachments.

VerifiedSTDIODesktop onlyFiles & StorageCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that connects an AI assistant to Cisco Webex Messaging to manage spaces, messages, memberships, teams, people, webhooks and attachments.

What you can do
  • List, search, create, update and delete spaces, and read space meeting info
  • Read, search, send, update and delete messages, including direct rooms, thread replies and attachment actions
  • List, add, update and remove space and team memberships; list, create, update and delete teams
  • Look up people by email, name or ID
  • List, create, update and delete webhooks
  • Inspect, download, save and view received attachments: images inline, text paged, ZIP/JAR entry listings, files saved to local disk
When to use it
Useful when you want an assistant to work inside Webex: summarizing or searching a space's messages, drafting and posting replies, managing space membership and teams, or pulling attachments from messages for review.
Requirements
Runs locally over stdio via npm package @yuryev89/webex-mcp with Node.js 18 or newer and npx. Needs either a Webex bot access token (WEBEX_ACCESS_TOKEN or the --token option) or a Webex Integration with WEBEX_CLIENT_ID and WEBEX_CLIENT_SECRET plus a one-time browser login. Network access to Webex is required; the bot must be a member of a space to read or post there.
Before you install
Requires a Webex credential: a bot token or OAuth client ID and secret, which may be kept in shell history or config files. Many tools write, send, invite or delete data (messages, spaces, teams, memberships, webhooks), so assistant actions affect real people and channels. Saved attachments are untrusted input and should not be executed. Message file URLs need the access token, so files should be fetched through the server's tools.

Installation

In SourceWeft

  1. Open Webex MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

webex-mcp

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

[npm version] [npm downloads] [license]

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

Quick start

Option A — Bot token

bash
# Run via npx (recommended)npx -y @yuryev89/webex-mcp@latest --token YOUR_ACCESS_TOKEN
# Or install globallynpm install -g @yuryev89/webex-mcpwebex-mcp --token YOUR_ACCESS_TOKEN

Option B — OAuth Integration

bash
# 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

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

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

toml
[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:

toml
[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

bash
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:

bash
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

json
{  "$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:

json
{  "$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

Option / CommandDescriptionDefault
--tokenWebex access token (Bot mode)$WEBEX_ACCESS_TOKEN
--fedrampUse FedRAMP endpointfalse
--debugLog startup to stderrfalse
loginOAuth browser login, save tokens—
logoutRemove stored OAuth tokens—
auth-statusShow OAuth expiry metadata—

Tools

Spaces

ToolDescription
webex_list_spacesList spaces (rooms) for the authenticated user
webex_search_spacesSearch spaces by title/name (case-insensitive)
webex_get_spaceGet space details by ID
webex_create_spaceCreate a new space
webex_update_spaceUpdate a space
webex_delete_spaceDelete a space
webex_get_space_meeting_infoGet meeting details for a space

Messages

ToolDescription
webex_get_messagesList messages in a space or get one by ID (includeFileDetails adds attachment names/types/sizes)
webex_search_messagesKeyword search within a single space
webex_create_messageSend text and/or file attachments to a space or DM
webex_update_messageUpdate an existing message
webex_delete_messageDelete a message
webex_list_direct_messagesList messages in a 1:1 direct room (includeFileDetails as above)
webex_create_attachment_actionSubmit an attachment card action
webex_get_attachment_actionGet attachment action details
Sending file attachments

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

json
{  "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:

json
{  "toPersonEmail": "[email protected]",  "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

ToolDescription
webex_get_file_detailsMetadata (filename, type, size) for a message files[] URL
webex_download_fileRead a file (max 10 MB): images inline, text paged with offset/maxChars, ZIP/JAR as an entry list
webex_get_message_imagesDownload all image attachments on a message for LLM vision
webex_save_fileSave one file to local disk (max 100 MB) and return its path
webex_save_message_filesSave every file of a message to local disk
Reading received attachments

What webex_download_file returns depends on the file:

FileResult
PNG, JPEG, GIF, WebPInline ImageContent
Text: text/*, JSON, XML, SQL, diff/patch, source codeJSON summary (totalChars, nextOffset, …) + the text, maxChars per call (default 50 000)
ZIP, JAR, WAR, EARList of entries (name, size, encrypted); nothing is extracted
Anything else (PDF, docx, xlsx, …)Metadata and a hint to use webex_save_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 <download dir>/<message-uuid>/<filename>, 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 <name>.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

ToolDescription
webex_list_membershipsList space memberships
webex_get_membershipGet membership details
webex_add_membershipInvite a person to a space
webex_update_membershipUpdate membership (e.g. moderator)
webex_remove_membershipRemove a person from a space

People

ToolDescription
webex_get_peopleSearch people by email, name, or ID
webex_get_personGet a person by ID (use me for yourself)

Teams

ToolDescription
webex_list_teamsList teams
webex_create_teamCreate a team
webex_get_teamGet team details
webex_update_teamUpdate a team
webex_delete_teamDelete a team
webex_list_team_membershipsList team memberships
webex_add_team_membershipAdd a person to a team
webex_get_team_membershipGet team membership details
webex_update_team_membershipUpdate team membership
webex_remove_team_membershipRemove a person from a team

Webhooks

ToolDescription
webex_list_webhooksList webhooks
webex_create_webhookCreate a webhook
webex_get_webhookGet webhook details
webex_update_webhookUpdate a webhook
webex_delete_webhookDelete a webhook

Limitations

  • webex_search_messages works within a single space only (Webex REST API has no global search)
  • Search scans message history page by page — may be slow in large spaces
  • Bot must be a member of a space to read or post messages
  • OAuth uses user-delegated tokens; Bot mode uses a long-lived Bot token
  • Message files[] URLs require the access token; use webex_get_message_images / webex_download_file / webex_save_file instead of fetching the URL directly
  • Inline vision images are limited to PNG, JPEG, GIF, and WebP, max 10 MB each; inline text and archive listings are also limited to 10 MB
  • PDF and Office documents are not parsed by the server; save them and open them locally
  • ZIP64 archives cannot be listed inline; save them instead

Authentication modes

ModeSetupBest for
Bot tokenCopy token from developer portalSimple Cursor setup, bot identity
OAuth Integrationwebex-mcp login + client ID/secretUser-delegated access with auto-refresh

Full guide

See docs/HOWTO.md for step-by-step setup: bot creation, scopes, Cursor config, example prompts, and troubleshooting.

Local development

bash
git clone https://github.com/yuryev89/webexmcpcd webexmcpnpm installcp .env.example .envnpm run dev -- --token "$WEBEX_ACCESS_TOKEN"npm test

License

MIT

Source: README.md at commit 3da990a

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not answer in time.

Version history

1
  1. v0.3.0LatestNov 6, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts