Webex

@webex list all messages from the 'Q1 Planning' room in the last 48 hours and summarize the key decisions made

Found 37 messages in 'Q1 Planning' room from the past 48 hours. Key decisions include: (1) Budget approved at $450K with 10% contingency; (2) Launch date moved to March 15 to accommodate legal review; (3) Sarah designated as primary stakeholder contact; (4) Weekly syncs scheduled for Tuesdays at 2pm PT. Three action items remain open: finalize vendor contracts, complete risk assessment, and draft comms plan. This summary reflects message content visible to your Webex account as of this query.

This example combines Webex's message retrieval with AI reasoning to extract decisions from conversation threads. Requires read access to the target room. Message history depth depends on your Webex plan tier—some accounts limit retrieval to recent messages only.

@webex create a new room called 'Security Incident Response' and add alice@company.com and bob@company.com as members

Created room 'Security Incident Response' (ID: Y2lzY29zcGFyazovL3VzL1JPT00vYWJjZDEyMzQ). Added alice@company.com and bob@company.com as members. Both users will receive Webex notifications and can access the room immediately. The room is private by default—only invited members can view messages. You can now use this room ID to post updates or attach files related to the incident.

Demonstrates Webex's room provisioning and membership management in a single workflow. Useful for spinning up ad-hoc collaboration spaces during incidents or project kickoffs. Requires OAuth scope to create rooms and manage memberships. Members must have active Webex accounts.

@webex send a message to the 'Engineering All-Hands' room with a markdown summary of this week's sprint retrospective and attach the retro notes PDF

Posted message to 'Engineering All-Hands' room (message ID: Y2lzY29zcGFyazovL3VzL01FU1NBR0UvZGVmNTY3ODk). Message includes markdown-formatted sprint retrospective summary with sections for What Went Well, What Needs Improvement, and Action Items. Attached 'retro-notes-2025-01-20.pdf' (245 KB). All room members can now view the summary and download the full notes. This action is permanent—use Delete Message tool if you need to retract.

Showcases Webex's rich message formatting and file attachment capabilities. The MCP posts directly to the room, making this a write operation with immediate visibility to all members. Be cautious with sensitive content—messages persist in room history and may be subject to compliance retention policies.

When Webex MCP wins for on-call response automation

A 6-person SRE team gets paged at 2am for a production outage. The on-call engineer needs a dedicated war room, needs to pull in the database lead and product owner, and needs a webhook firing updates to their status page. The Webex MCP handles this in one prompt: create the room, add the three people by email, post the incident summary with a card attachment showing severity, and register the webhook to catch resolution messages. OAuth2 means the room inherits the engineer's org permissions without manual token juggling. This works cleanly up to about 15 people per incident; beyond that, you're managing a crowd and the MCP's membership tools get tedious. If your incidents routinely involve 20+ responders across multiple orgs, you need a purpose-built incident platform. For small-team fire drills where speed and context matter more than process, this MCP closes the loop.

When this MCP scales for CS team onboarding workflows

A 4-person customer success team onboards 8-12 new enterprise accounts per quarter. Each account gets a dedicated Webex space with the customer's project lead, the assigned CSM, and a solutions engineer. The Webex MCP automates the setup: create the room with a naming convention, add the three participants by email, post a welcome message with a card linking to the onboarding checklist, and create a webhook that logs room activity to the CRM. The 28 tools cover the full lifecycle—room creation, membership management, message posting, webhook registration—so the CSM never touches the Webex UI. This breaks down if you're onboarding 50+ accounts per month or need complex approval chains; at that scale, the MCP's one-at-a-time tool calls become a bottleneck and you need batch APIs. For quarterly cohorts under 15 accounts, the MCP keeps onboarding consistent without custom dev work.

When Webex MCP handles recurring team broadcast

A 12-person startup runs Friday all-hands and the CEO wants a summary posted to three department rooms—eng, sales, ops—with a card showing the week's wins and next week's priorities. The Webex MCP takes the meeting transcript, formats it as markdown, and posts it to all three rooms in one prompt. The Create Message tool supports markdown and card attachments, so the recap looks polished without manual formatting. OAuth2 means the CEO's assistant can trigger this from Switchy without storing API keys. This works for up to 5-6 target rooms; beyond that, you're better off with a team-wide announcement room or a proper broadcast tool. If your recaps need approval workflows or version control, the MCP won't help—it's a one-shot post, not a content management system. For small teams where the CEO or ops lead owns the message and just needs it distributed fast, this MCP is the right tool.