LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Webex Meetings & Messaging

Three separate endpoints — meetings, messaging and Vidcast — each connected only if your admin enables it.

by Webex ↗Calendars, Meetings & Scheduling✓ Official

LABSCO SUMMARY

Splitting into three endpoints is a context decision as much as a permissions one.

Someone automating meeting scheduling has no use for two dozen messaging tools riding along on every turn, and separating them means they never do. It also gives an administrator a real choice — meetings on, messaging off — rather than an all-or-nothing switch. That is the pattern to look for in any large vendor's endpoint. Connect only the surface you need, and treat the recordings and transcripts on the meetings endpoint as the sensitive part: they contain everyone else in the room.

What it is

Cisco publishes three distinct Webex endpoints rather than one. You connect the ones you need, and each is enabled independently by an administrator.

What you get

  • Meetings — scheduling and modifying meetings, minutes, recordings and transcripts
  • Messaging — messages, spaces, memberships and webhooks
  • Vidcast — video discovery, analytics and sharing

Requirements

  • An organisation administrator enables the specific server in Control Hub
  • Your client obtains a Webex OAuth token carrying the scopes those tools need
  • Connect to each of the three endpoints separately, as needed

Setup effort

Admin enables it, then paste and authorize — add the servers you want to your client, then approve the OAuth consent screen

See installation options