Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Webex to Claude Code

Let Claude post to spaces and schedule meetings in Webex. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Webex to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Webex, you add a Webex MCP server: a small hosted service that exposes Webex's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Webex account. No API keys pasted into config files.

claude mcp add --transport http webex https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Webex once connected?

Full read-write Webex access lets Claude post a message into a specific space, create or update a meeting and invite attendees, add or remove people from a space, and share a file once you approve. The coordination that used to mean switching apps happens where the conversation already lives.

  • Post a message into a specific Webex space, with formatting preserved
  • Create a meeting and invite attendees, or update an existing one
  • Add or remove people from a space as membership changes
  • Create a new space and seed it with the right participants
  • Share a file or update into the relevant space after you approve

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Webex access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Webex API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Webex changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Webex connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Webex connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Webex account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Webex's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Webex?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Webex account it signs in with. Revoking access is one click in Webex.

More on the Webex connector

Webex connector for claude.aiTelegram + Claude CodeWhatsApp Business + Claude CodeRingCentral + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us