LabscoMCP early access ↗
Kashyap-AI-ML-SolutionsMCP SERVER

Webex MCP Server

Cisco Webex messaging as 52 tools — messages, rooms, teams, memberships, the people directory, webhooks and events, plus room tabs and ECM folders.

by Kashyap-AI-ML-Solutions ↗Team Chat PlatformsCommunity

LABSCO SUMMARY

52 tools is a lot of context — narrow it with `ENABLED_TOOLS`.

Few workflows need messaging, team administration, webhooks and ECM folders at once, and loading all of them costs tool definitions on every turn. The annotations help here too: each tool declares whether it reads or writes, which is worth checking before you let an agent loose on delete_person or delete_room. The token is the practical constraint — a developer bearer token expires in 12 hours, so treat an unattended deployment as needing a renewal path before anything else.

What it is

An MCP server covering Cisco Webex's messaging API across 52 tools: the messaging surface itself, the org structures around it (rooms, teams, memberships, people), event plumbing through webhooks, and the enterprise pieces — room tabs, attachment actions and linked ECM folders. It runs over stdio or as an HTTP server.

What you get

  • Messages sent, listed, edited, deleted and read individually — create_message, list_messages, edit_message, delete_message, get_message_details
  • Rooms created, browsed, inspected, reconfigured and removed — create_room, list_rooms, get_room_details, update_room, delete_room
  • Teams created, listed, inspected, updated and deleted — create_team, list_teams, get_team_details, update_team, delete_team
  • Membership managed on both rooms and teams, including role changes — create_membership, list_memberships, update_membership, delete_membership, create_team_membership, list_team_memberships
  • The people directory read and administered: your own profile, user search, individual details, and creation, update and removal for administrators — get_my_own_details, list_people, get_person_details, create_person, update_person, delete_person
  • Webhooks created, listed, inspected, updated and removed, and the activity log read as events — create_webhook, list_webhooks, get_webhook_details, update_webhook, delete_webhook, list_events, get_event_details
  • Enterprise surfaces: tabs added to rooms and managed, adaptive-card form submissions handled, and enterprise content management folders listed, created, linked and unlinked — create_room_tab, list_room_tabs, update_room_tab, delete_room_tab, create_attachment_action, get_attachment_action_details, list_ecm_folder, create_ecm_folder, update_ecm_linked_folder, unlink_ecm_linked_folder
  • Every tool publishing MCP annotations through tools/list that name its closest sibling tool, say whether it reads or changes Webex state, and describe how errors and rate limits come back

Requirements

A Webex API token from developer.webex.com, in WEBEX_PUBLIC_WORKSPACE_API_KEY with the Bearer prefix stripped. Plan for renewal: the developer bearer token is short-lived and the README puts its lifetime at 12 hours, so a long-running deployment needs a token strategy rather than a paste. Node.js 18+, with 20+ recommended — below 18 there is no global fetch and the tools depend on it. WEBEX_API_BASE_URL overrides the endpoint, MCP_MODE selects stdio or http, and PORT sets the HTTP port, defaulting to 3001. The npm package name is webex-messaging-mcp-server (0.2.1), and a Docker image runs it as a non-root user. ENABLED_TOOLS narrows which tools load.

Setup effort

Run a container — build the image from the repository, then point your client at it