Webex Meetings

Schedule, update and delete Webex meetings and read recordings and transcripts.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Webex Meetings connector does

The Webex Meetings MCP server connects Cisco Webex meeting scheduling and recordings to Claude, ChatGPT and any MCP-compatible agent. Cisco documents eight tools that list, create, update and delete meetings and read summaries, recordings and transcripts. Sign-in is OAuth against Webex. Unlike most meeting connectors, this one schedules — and emails the invitees.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Webex Meetings tools (8)

  • webex-list-meetings
  • webex-create-meeting
  • webex-update-meeting
  • webex-delete-meeting
  • webex-get-meeting-status
  • webex-get-meeting-summary
  • webex-list-recordings
  • webex-list-transcripts

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The OAuth scope list is not a read/write boundary. The server's RFC 9728 descriptor lists seven scopes under scopes_supported and repeats all seven under required_scopes. Nothing is optional, so an OAuth grant that reads transcripts necessarily also grants meeting:schedules_write, which is create, update and delete. The one place a boundary does exist is the WCIT token path, where Cisco documents scopes being elicited per tool call — but that path only works on clients supporting MCP elicitation.
  • Email is the default on every write. Webex's Create, Update and Delete Meeting APIs all document sendEmail defaulting to true. An agent that does not set it explicitly notifies the host and every invitee.
  • Deletion cannot be undone, and can take a whole series. Webex documents that a deleted meeting cannot be recovered and that passing a meeting-series ID deletes the entire series.
  • An admin gate stands in front of everything. Cisco requires the server to be enabled in Webex Control Hub before any user can connect. That gate is also the strongest control available to you: Control Hub supports per-tool enablement scoped to user groups, so an org can publish the read tools broadly and restrict create and delete to a named group.
  • The meeting summary needs Webex AI Assistant. Cisco flags webex-get-meeting-summary as requiring it. Without AI Assistant there are no summary notes or action items to fetch.
  • Transcripts and summaries only exist for ended meetings. Webex's transcript and summary APIs both reject meeting series, scheduled meetings and in-progress instances; only an ended meeting instance is supported.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint is published here. Everything above about tool behaviour comes from Cisco's documentation and from the REST endpoints Cisco documents these tools as calling.
  • Cisco publishes no rate limit for this server. It publishes one for its Vidcast MCP server — 120 invocations per 60 seconds, 10 concurrent — and none on the Meetings page. Assume the underlying Webex REST API limits apply and that they are not documented here.
  • There is no llms.txt and the doc page is JavaScript-rendered. developer.webex.com/llms.txt returns 404, and the documentation page yields 478 words to a plain text extractor while carrying its full content inside a window.__INITIAL_STATE__ payload in the same response. An agent using a naive extractor would wrongly conclude Cisco documents almost nothing.
  • Do not confuse this with Cisco's other four MCP servers. Cisco runs Messaging (24 tools), Vidcast (29), Workspaces (16) and Webex Suite (25) at sibling paths on the same host. The Suite server duplicates this one's meeting functions behind a single webex-manage-meeting dispatcher and adds messaging writes; its Workspaces sibling advertises a webexsquare:admin scope that its documentation page does not mention.

Frequently asked questions

Can the Webex Meetings connector schedule a meeting?

Yes. The webex-create-meeting tool creates a real meeting with a title, time, duration, recurrence, password and an invitee list, and Cisco's documentation says it sends email invitations. This is the sharp difference from the Zoom connector, which reads meeting history and schedules nothing. Treat every create call as an action other people will see.

Does the Webex connector send email to other people?

Yes, on three of its eight tools, and by default. Cisco documents that webex-create-meeting sends email invitations and that webex-delete-meeting sends an optional cancellation email. The underlying Webex REST API exposes a sendEmail flag on create, update and delete whose documented default value is true, so silence in a tool call means mail goes out.

Can the Webex Meetings connector delete a meeting?

Yes, and Webex documents the deletion as unrecoverable. Cisco's Meetings API states plainly that a deleted meeting cannot be recovered, and that deleting the ID of a meeting series deletes the entire series rather than one occurrence. The same call emails a cancellation notice to the host and invitees unless that behaviour is explicitly turned off.

Can the Webex connector read my meeting transcripts?

Yes, as full plain text. Cisco documents webex-list-transcripts as listing transcript metadata and optionally downloading full plain-text transcript content for LLM analysis. That puts every participant's recorded speech into the agent's context, and it needs the meeting:transcripts_read scope. Transcripts are available only for meeting instances that have already ended.

What OAuth scopes does the Webex Meetings MCP server require?

Seven, and the server's own descriptor marks all seven as required rather than optional. They are spark:mcp for the connection plus six meeting scopes covering schedules read, schedules write, participants, summaries, recordings and transcripts. Because schedules write is in the required set, an OAuth connection cannot be granted read-only access to this server.

Can I connect the Webex MCP server without granting write access?

Only on the token path, not the OAuth path. Cisco documents a WCIT token issued with the spark:mcp scope alone, where the server uses MCP elicitation to request each further scope at tool-call time. Clients that do not support elicitation must use OAuth instead, and the OAuth descriptor requires all seven scopes up front.

What do I need before connecting Webex Meetings to Claude?

An administrator has to switch it on first. Cisco states this MCP server must be enabled by your organization's admin in Webex Control Hub before it can be used. The admin decides in Control Hub which individual tools are available and to which user groups, so the delete and create tools can be withheld from most of the organization.

Is the Webex Meetings connector the same as the Webex Suite server?

No, they are different endpoints with different tool surfaces. The Webex Suite server at mcp.webexapis.com/mcp/webex-suite carries 25 tools spanning Meetings, Messaging, Vidcast and Calling, and it collapses create, update and delete into one webex-manage-meeting dispatcher. Its Messaging half can post messages to spaces; this Meetings server cannot.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Webex Meetings to work.

Connect Webex Meetings once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio