CreateBlogSupport
Log inSign up
Home
Create
  • Authentication
  • Login with Webex
  • AI Assistant for Developers
  • Agentic Apps
  • Bots
  • Embedded Apps
  • Integrations
  • Service Apps
  • Instant Connect
  • Workspace Integrations
  • Bring Your Own Datasource
  • Suite Sandbox
  • Contact Center Sandbox
  • Guest to Guest Sandbox
  • Submit Your App
  • Tutorials

Create

Webex MCP Server Usage Guide

This guide helps developers integrate Webex MCP (Model Context Protocol) servers with popular AI clients. MCP enables AI agents to securely access Webex capabilities through the Model Context Protocol.

anchorOverview

anchor

Webex provides MCP servers that enable AI agents to securely access various Webex functionalities through the Model Context Protocol. These servers act as a bridge between your AI client and Webex services, allowing AI agents to perform actions and retrieve information on your behalf.

anchorStep 1: Generate Your Authentication Token

anchor

To connect to Webex MCP servers, you need a WCIT (Webex Client Identity Token).

Generate WCIT Token

The WCIT is a special authentication token with enhanced validity that includes the spark:mcp scope required to connect with Webex MCP servers.

  1. In the Webex Developer Portal, navigate to the Generate WCIT Token page
  2. Enter an appropriate name for your token (e.g., "Claude Desktop Integration" or "VS Code Copilot")
  3. Click Generate New Token
  4. Copy the generated token and store it securely (you'll need this for configuration)

Important: Keep your token secure and never commit it to version control.

anchorAvailable MCP Servers

anchor

Note: The servers are currently under development.

anchorStep 2: Configure Your AI Client

anchor

Choose your AI client below and follow the configuration steps:

👉 Click to see Claude Desktop

Claude Desktop supports MCP servers through its configuration file. You can connect to remote Webex MCP servers using HTTP transport.

Configuration Steps

  1. Open Claude Desktop Settings

    Click on the Claude menu in your system's menu bar (not the settings within the Claude window itself) and select Settings...

    On macOS, this appears in the top menu bar. On Windows, access it from the Claude Desktop application menu.

  2. Access Developer Settings

    In the Settings window, navigate to the Developer tab in the left sidebar. This section contains options for configuring MCP servers.

    Click the Edit Config button to open the configuration file.

  3. Add Webex MCP Server Configuration

    Add the following configuration to connect to a Webex MCP server. If the file is empty, you can paste this entire structure. If you already have other MCP servers configured, add a new entry to your existing mcpServers object.

Configuration Code
{
  "mcpServers": {
    "<server-name>": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<MCP_SERVER_URL>",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_WCIT_TOKEN_HERE"
      }
    }
  }
}

Important:

  • Replace <server-name> with a descriptive name for the server (e.g., webex-messaging, webex-meetings)
  • Replace <MCP_SERVER_URL> with the desired server endpoint from the Available MCP Servers section above
  • Replace YOUR_WCIT_TOKEN_HERE with the WCIT token you generated in Step 1
  • The -y flag automatically confirms the installation of the mcp-remote package
Verify Connection

  1. Restart Claude Desktop

    After saving the configuration file, completely quit Claude Desktop and restart it. The application needs to restart to load the new configuration.

  2. Check MCP Server Status

    Upon successful restart, you'll see an MCP server indicator (hammer icon) in the bottom-right corner of the conversation input box. Click on this indicator to view the available tools provided by the Webex MCP server.

  3. Test the Connection

    Start a new conversation and look for the tools icon or type "What Webex capabilities do you have?" Claude should list available Webex functions like sending messages, listing spaces, etc.

Configuration File Location

The configuration file is located at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

You can also access this file directly if you prefer not to use the Edit Config button.

👉 Click to see GitHub Copilot (VS Code)

GitHub Copilot with MCP support allows you to connect external servers through either the Command Palette (recommended) or by manually editing the configuration file.

Method 1: Using Command Palette (Recommended)

This method provides a guided setup experience with built-in authentication handling.

  1. Open Command Palette

    Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS) to open the Command Palette.

  2. Add MCP Server

    Type MCP: Add Server and select it from the list.

  3. Select Connection Type

    Choose HTTP (or Server Sent Events) as the connection type.

  4. Name the Server

    Enter a descriptive name (e.g., webex-messaging, webex-meetings) and press Enter.

  5. Set Configuration Scope

    Select either:

    • Global: Server will be available across all VS Code projects
    • Workspace: Server will only be available in the current project

  6. Enter Server URL

    Enter the Webex MCP server URL from the Available MCP Servers section above (e.g., https://agentic-server-platform-intb.ciscospark.com/agentic-server-platform/mcp/messaging) and press Enter.

  7. Configure Authentication

    When prompted for authentication headers, add:

    Authorization: Bearer YOUR_WCIT_TOKEN_HERE

    Replace YOUR_WCIT_TOKEN_HERE with the WCIT token you generated in Step 1.

  8. Verify Installation

    Open the Command Palette again and run MCP: List Servers. You should see your configured server listed.

Method 2: Manual Configuration via mcp.json

This method is useful if you prefer direct file editing or need to configure multiple servers at once.

  1. Open VS Code

  2. Locate or Create Configuration File

    You can configure MCP servers either globally (for all projects) or per workspace:

    Global Configuration (available across all VS Code projects):

    • macOS: ~/Library/Application Support/Code/User/mcp.json
    • Windows: %APPDATA%\Code\User\mcp.json
    • Linux: ~/.config/Code/User/mcp.json

    Workspace Configuration (specific to current project):

    • Create an mcp.json file in your workspace's .vscode folder: .vscode/mcp.json

    If the file doesn't exist, create it with the basic structure shown below.

  3. Add Server Configuration

    Add the Webex MCP server configuration to the servers object:

{
  "servers": {
    "<server-name>": {
      "url": "<MCP_SERVER_URL>",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_WCIT_TOKEN_HERE"
      }
    }
  },
  "inputs": []
}

Important:

  • Replace <server-name> with a descriptive name for the server (e.g., webex-messaging, webex-meetings)
  • Replace <MCP_SERVER_URL> with the desired server endpoint from the Available MCP Servers section above
  • Replace YOUR_WCIT_TOKEN_HERE with the WCIT token you generated in Step 1
  • "type": "http" specifies the connection method for remote servers
  • "headers" contains authentication credentials passed with each request
Verify Connection

  1. Reload VS Code

    After saving the mcp.json file, reload the VS Code window:

    • Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
    • Type and select "Developer: Reload Window"

  2. Check Available Tools

    Open the GitHub Copilot chat interface and check that Webex MCP tools are now available in the suggestions.

  3. Test the Connection

    In the Copilot Chat panel, type "@webex" or ask "What Webex tools are available?" Copilot should show available Webex MCP tools.

👉 Click to see Cursor IDE

Cursor IDE supports MCP servers through its configuration system. You can configure servers either through the Cursor Settings UI or by manually editing the configuration file.

Configuration Steps

  1. Open Cursor Settings

    Use the command palette (Ctrl+Shift+P or Cmd+Shift+P on macOS) and search for "Cursor Settings".

    Alternatively, navigate to File > Preferences > Cursor Settings.

  2. Navigate to MCP Tools

    In the settings sidebar, select Tools & Integrations and then find the MCP Tools section.

  3. Add New MCP Server Click the button to add a new MCP server. This will open the global ~/.cursor/mcp.json configuration file in your editor. If the file doesn't exist, Cursor will create it automatically.

  4. Add Webex MCP Server Configuration Add the following configuration to the mcpServers object in the mcp.json file. If the file is empty, you can paste this entire structure. If you already have other MCP servers configured, add a new entry to your existing mcpServers object.

Configuration Code
{
  "mcpServers": {
    "<server-name>": {
      "url": "<MCP_SERVER_URL>",
      "headers": {
        "Authorization": "Bearer YOUR_WCIT_TOKEN_HERE"
      }
    }
  }
}

Important:

  • Replace <server-name> with a descriptive name for the server (e.g., webex-messaging, webex-meetings)
  • Replace <MCP_SERVER_URL> with the desired server endpoint from the Available MCP Servers section above
  • Replace YOUR_WCIT_TOKEN_HERE with the WCIT token you generated in Step 1
Verify Connection

  1. Save and Auto-Install Save the mcp.json file. Cursor will automatically detect the changes and attempt to install and run the server.

  2. Check Server Status A green status dot next to the server name in the Cursor settings indicates the server is running correctly. If you see a red or yellow indicator, check the troubleshooting section below.

  3. Test the Connection

    Open the AI chat interface and ask "Show me available Webex tools". Cursor should display the connected MCP server capabilities.

Configuration File Location

The MCP configuration file is located at:

  • macOS: ~/.cursor/mcp.json
  • Windows: %USERPROFILE%\.cursor\mcp.json
  • Linux: ~/.cursor/mcp.json

You can edit this file directly if you prefer not to use the Cursor Settings UI.

anchorTroubleshooting

anchor
Common Issues
Connection Failed

Problem: MCP server fails to connect

Solutions:

  • Verify your WCIT token is valid and not expired
  • Check that the endpoint URL is correct
  • Ensure you have an active internet connection
Authentication Error

Problem: "401 Unauthorized" or authentication errors

Solutions:

  • Regenerate your WCIT token from the Developer Portal
  • Ensure the token is properly formatted with "Bearer " prefix in the configuration
  • Check that the token hasn't been revoked
Server Not Responding

Problem: MCP server is not responding to requests

Solutions:

  • Verify your firewall isn't blocking the connection
  • Try restarting your AI client
Tools Not Appearing

Problem: Webex tools don't show up in the AI client

Solutions:

  • Confirm the configuration file syntax is correct (valid JSON)
  • Restart the AI client completely
  • Check the AI client's console/logs for error messages
  • Verify you're using the latest version of your AI client:
    • Claude Desktop: Check for updates via Claude menu > "Check for Updates..."
    • VS Code: Ensure GitHub Copilot extension is up to date
    • Cursor: Check for IDE updates in Cursor settings
Getting Help

If you continue to experience issues, visit the Webex Developer Support.

anchorManaging Your MCP Connection

anchor
Unlinking an MCP Server

If you need to remove an MCP server from your AI client:

Claude Desktop:

  1. Open Settings > Developer tab
  2. Click "Edit Config" to open claude_desktop_config.json
  3. Remove the server entry from the mcpServers object
  4. Save the file and restart Claude Desktop

VS Code:

  1. Use Command Palette: MCP: Remove Server and select the server to remove, or
  2. Manually edit mcp.json (global or workspace) and remove the server entry from the servers object
  3. Reload the VS Code window

Cursor IDE:

  1. Open Cursor Settings > Tools & Integrations > MCP Tools
  2. Remove the server entry from ~/.cursor/mcp.json
  3. Save the file (Cursor will automatically detect the change)
Revoking Your WCIT Token

If your token is compromised or you no longer need it:

  1. Navigate to the Manage WCIT Tokens page in the Webex Developer Portal
  2. Locate the token you want to revoke in the list
  3. Click the Delete button next to the token
  4. Confirm the revocation

Important: After revoking a token, any AI clients using that token will immediately lose access to Webex MCP servers. You'll need to generate a new token and update your client configurations.

anchorNext Steps

anchor

Now that you've connected your Webex MCP server, you can:

  • Explore the available Webex capabilities in your AI client
  • Build custom workflows using Webex messaging and collaboration features
  • Create intelligent agents that interact with your Webex organization

anchorAdditional Resources

anchor
  • Webex Developer Portal
  • Model Context Protocol Specification

Last Updated: February 2, 2026

Questions or Feedback? Visit the Webex Developer Community or contact support through the Developer Portal.

In This Article
  • Overview
  • Step 1: Generate Your Authentication Token
  • Available MCP Servers
  • Step 2: Configure Your AI Client
  • Troubleshooting
  • Managing Your MCP Connection
  • Next Steps
  • Additional Resources

Connect

Support

Developer Community

Developer Events

Contact Sales

Handy Links

Webex Ambassadors

Webex App Hub

Resources

Open Source Bot Starter Kits

Download Webex

DevNet Learning Labs

Terms of Service

Privacy Policy

Cookie Policy

Trademarks

© 2026 Cisco and/or its affiliates. All rights reserved.