anchorOverview

Webex Connect skills are focused instruction packages that help an AI coding agent build, configure, and operate Webex Connect workflows. They explain when a workflow applies, what information it needs, how to validate the request, and how to handle the result.

The public Webex Skills repository provides two ways to install these instructions:

• Standalone skills install selected workflows individually.
• Webex Connect AI plugin bundles the Connect skills with host-specific commands, rules, manifests, and branding.

The plugin includes 19 independently packaged skills. The source repository currently identifies the plugin as a beta release. The skill set and versions can change; the table below reflects the current catalog.

Installing a skill or plugin does not create a Webex Connect tenant, register a mobile device, approve a sender, configure credentials, or enable an MCP connection. Complete the relevant setup steps in this guide before using API-backed workflows.

anchorBefore you begin

AI host and installation tools

• The plugin supports Codex, Claude Code, and Cursor.
• Standalone installers also support GitHub Copilot. Client support can vary by skill; check the skill's entry in the catalog.
• For repository-based plugin installation, install Git and make sure the host can access GitHub.
• Standalone skill installers use Node.js 20 or later and npm (which provides npx). Setup utilities use Python 3.
• The shell commands below use macOS or Linux paths. On Windows, use the equivalent paths and copy commands for your host.

Webex Connect tenant and credentials

Have access to a Webex Connect tenant and decide whether the task uses Sandbox or Production. Gather only the credentials required by the selected workflow.

Prepare channel resources where the task needs them:

• SMS or Email: an approved sender and recipient details.
• Push: a configured mobile or web app asset and a registered user or device identifier.
• Live Chat or In-App Messaging: a configured asset, app and user identifiers, and any required flow or webhook configuration.
• Android or iOS SDK work: the relevant SDK, platform credentials, and a test application or device.

For MCP-backed Production messaging, an organization administrator must enable the MCP server in Webex Control Hub and Webex Connect Tenant Settings. The tenant also needs an approved SMS phone number or supported Email asset with an approved AI Agent Messaging use case. Sandbox does not use the Production CPaaS MCP server.

Store secrets only in protected local configuration or the AI host's secure credential store. Do not put Service Keys, JWTs, MCP tokens, platform credentials, or tenant secrets in a prompt, skill package, plugin, public issue, or committed .env file.

anchorComplete the task

Choose an installation

Choose standalone skills when you need a smaller, auditable set of workflows. Choose the plugin when you want the bundled Webex Connect workflows, commands, and rules together.

The plugin supports Codex, Claude Code, and Cursor. A standalone skill can support additional clients through its installer. See the Webex Skills repository for the current package source and release information.

Skill catalog

Use the message router for an outbound send request. It selects one channel-specific skill and adds setup, Contact Policy, webhook, or Sandbox guidance when the task requires it.

Install the bundled plugin

Clone the public repository once. Use a directory where you keep development tools, not your application project root:

git clone https://github.com/webex/webex-skills.git
cd webex-skills

The assembled, installable plugin is in plugin-packages/webex-connect-ai/. No local build step is required for normal installation.

Codex

Add the Webex Skills marketplace to Codex:

codex plugin marketplace add https://github.com/webex/webex-skills.git \
  --sparse .agents/plugins \
  --sparse plugin-packages/webex-connect-ai

Open Codex and run:

/plugins

Select Webex Skills, choose Webex Connect AI, and select Install plugin. Complete any prompts, then start a new Codex session and confirm that the plugin appears in the plugin browser.

Claude Code

In a Claude Code session, add the public marketplace and install the plugin:

/plugin marketplace add webex/webex-skills
/plugin install webex-connect-ai@webex-skills

Review the plugin details and select user, project, or local scope when prompted. Start a new Claude Code session after installation. Use /plugin to inspect installed and available plugins.

Cursor

Copy the assembled plugin into Cursor's local plugin directory:

mkdir -p ~/.cursor/plugins/local/webex-connect-ai
rsync -a --delete ./plugin-packages/webex-connect-ai/ ~/.cursor/plugins/local/webex-connect-ai/

Reload Cursor, open Customize, and confirm that the skills, commands, and rules are visible. Enterprise administrators may need to allow local plugin imports or distribute the plugin through a team marketplace.

Install standalone skills

Choose a skill from the catalog and install its package. The packages are distributed as GitHub archives; they do not need to be published to the npm registry. Installers use npx.

For example, install the SMS skill for Codex at user scope:

npx --yes \
  --package https://raw.githubusercontent.com/webex/webex-skills/main/skills/webexconnect-sms-sendmessage/release/webexconnect-sms-sendmessage-latest.tgz \
  webexconnect-sms-sendmessage install --client codex --scope user

Install the setup skill as well when you plan to use API-backed workflows:

npx --yes \
  --package https://raw.githubusercontent.com/webex/webex-skills/main/skills/webex-connect-setup/release/webex-connect-setup-latest.tgz \
  webex-connect-setup install --client codex --scope user

Use --scope project to install into the current application project. Installer-supported clients include Codex, Claude Code, and GitHub Copilot; --client all installs for Codex, GitHub Copilot, and Claude Code. Check the selected skill's package metadata for the supported clients.

Update an installation

Before updating, close active sessions using Webex Connect AI. After updating, restart or reload the host so it does not keep an older copy in memory. Updating a plugin or skill does not change the tenant, digital assets, sender IDs, project .env, or secure MCP credentials.

For a Codex Git-backed marketplace, refresh the source:

codex plugin marketplace upgrade webex-skills

Open /plugins in Codex to inspect Webex Connect AI and use the available plugin update action. If no update is offered, remove and reinstall the plugin from the refreshed Webex Skills marketplace. Start a new Codex session after updating.

For Claude Code, update the marketplace and plugin:

/plugin marketplace update webex-skills

Or use the CLI:

claude plugin marketplace update webex-skills
claude plugin update webex-connect-ai@webex-skills
claude plugin list

For the local Cursor installation, update the webex-skills clone used during installation and copy the refreshed plugin files into Cursor's local plugin directory:

git pull --ff-only
rsync -a --delete ./plugin-packages/webex-connect-ai/ ~/.cursor/plugins/local/webex-connect-ai/

The trailing slashes copy the package contents, and --delete removes local files that are no longer in the source. Reload Cursor and confirm the updated skills, commands, and rules are visible.

To update a standalone skill, rerun its installer with the same client and scope and add --force. For example:

npx --yes \
  --package https://raw.githubusercontent.com/webex/webex-skills/main/skills/webexconnect-sms-sendmessage/release/webexconnect-sms-sendmessage-latest.tgz \
  webexconnect-sms-sendmessage install --client codex --scope user --force

Review local modifications before replacing a skill. For project installs, run from the target project and keep --scope project. Do not mix skill directories from different releases.

Configure Webex Connect

Open the application project in the AI host. For API-backed work, run the setup skill when tenant, region, authentication, or channel configuration is missing:

Use webex-connect-setup to configure Webex Connect.

The setup flow:

1. Asks you to select Sandbox or Production. It does not silently choose an environment.
2. Collects the tenant context and confirms the region. It uses documented API hosts for each API family rather than deriving one host from another.
3. For Production, registers the region-matched SMS and Email MCP endpoint with the active AI host. Sandbox has no MCP endpoint and does not configure Production MCP.
4. Creates or updates the project .env with supported Messaging v1/v2, Voice, Contact Policy, Profile, Audit Logs, Digital Asset, and Production MCP endpoints. Existing values are preserved, missing keys are added, and file permissions are restricted. Credentials are left blank for you to enter locally.
5. Identifies the authentication required by the selected workflow and checks for the endpoint and credential values before an API-backed skill continues.
6. Confirms channel resources and summarizes the requested action before a send or asset mutation.

Android, iOS, and browser widget builders collect their SDK configuration directly and do not require the API .env preflight.

The project .env is not automatically loaded by every MCP host. The current setup utility registers only Production-region MCP endpoints; it does not configure Integration staging or preproduction endpoints. For staging or preproduction, manually configure the AI host's MCP server URL using the matching endpoint in the following table instead of using the Production MCP installer. Configure authentication separately using the host's documented flow. Codex uses a WCIT bearer token, Cursor supports WCIT or OAuth, and Claude Code uses browser OAuth. Do not assume that writing .env authenticates a remote MCP connection.

MCP endpoints, region, and authentication

Use the Integration endpoint for the tenant's staging or preproduction environment, or the Production endpoint for its confirmed region. Do not guess an endpoint that is not listed.

The MCP server must be enabled by an organization administrator in Webex Control Hub and Webex Connect Tenant Settings. An approved SMS phone number or supported Email asset and an approved AI Agent Messaging use case are also required.

Codex supports token-based authentication with a Webex Client Integration Token (WCIT) that has the spark:mcp scope. Store the token as a bearer token in Codex's MCP server configuration; protect the local configuration file. The server requests any additional tool scopes at runtime through MCP elicitation. Cursor supports the same WCIT flow and also OAuth through an Integration App; register Cursor's fixed redirect URI cursor://anysphere.cursor-mcp/oauth/callback. Claude Code uses client-based browser OAuth; prepare the Integration App client ID, client secret, and matching callback URI listed above. Keep bearer tokens and client secrets in protected local configuration, never in a prompt or committed file.

• Codex: configure the selected URL and WCIT as the Authorization bearer token in Codex's MCP server configuration, then protect the local configuration file.
• Claude Code: add the selected URL with claude mcp add --transport http using the Integration App client ID, client secret, and registered callback port. Then run /mcp, select the server, and choose Authenticate to complete browser authorization. See the Claude Code MCP setup guide for the command and callback details.
• Cursor: use the one-click WCIT token flow or configure OAuth through the Integration App flow described in Cursor's MCP guide.

The CPaaS MCP server exposes sender discovery and non-templated SMS and Email messaging. Its tools are webex-sender-ids, webex-sms-message, and webex-email-message. Do not use Production MCP credentials for Sandbox. If your tenant region is not listed, confirm it with your administrator and use documented direct APIs until a supported MCP endpoint is confirmed.

Direct API credentials and MCP credentials are separate and are not interchangeable. Keep the selected tenant and environment in your local setup record without storing credential values there.

Common use cases

Example requests

Send an SMS

Use the Webex Connect SMS skill to prepare an approved utility SMS to my test recipient with the configured sender ID. Show me the recipient and message before sending.

The workflow validates the E.164 recipient, sender, encoding, and Send Message API v2 request. It reports acceptance and the message ID; acceptance does not prove delivery.

Send an Email through MCP

Use the Webex Connect Email skill. Find the approved sender for this use case, show me the sender and recipient, and wait for my confirmation before sending.

The MCP path must already be configured. If sender discovery finds no compatible sender, ask an administrator to approve one; do not invent a sender ID.

Manage a digital asset

Create a Webex Connect digital asset.

For retrieval or update, name the operation and provide the documented asset identifier. The skill asks which operation and asset type apply, validates against that operation's schema, and requests confirmation before a create or update.

Build a widget or mobile integration

Use the Webex Connect Live Chat widget skill to build a browser widget for my tenant.

For mobile work, select the Android or iOS Push and In-App Messaging builder. These builders collect app identifiers and platform credentials, then produce an integration structure with validation and QA steps.

Test in Sandbox

Use the Sandbox skill for supported SMS, Voice, or WhatsApp tests. Sandbox setup must not configure the Production CPaaS MCP server or its credentials.

anchorVerify the result

• Confirm the installed plugin or skill and release in the AI host, then reload or restart the host.
• Ask the agent to list the Webex Connect skills and confirm that the expected workflows are available.
• For API-backed work, run setup as a preflight check and confirm the selected tenant, environment, region, endpoint, and required local credentials.
• For MCP, verify the intended regional URL, secure authentication, and the available sender discovery or messaging tools.
• Start with a test tenant, test asset, or test recipient when possible. Record message IDs, correlation IDs, request timestamps, and acceptance status.
• Treat an accepted or queued response as platform acceptance. Check receipts, callbacks, and tenant logs separately to confirm delivery.

anchorSecurity and operational guidance

• Review the plugin source and manifest before installing, especially from a third-party marketplace.
• Grant filesystem and MCP permissions only to workflows that need them.
• Keep secrets in an ignored local .env with owner-only access or in the host's secure credential store. Never paste bearer tokens or Service Keys into a public prompt, README, issue, generated source, or committed environment file.
• Use test recipients and assets before Production sends.
• Confirm the environment, tenant, sender, recipient, and payload before each irreversible action.
• Configure Contact Policy and opt-out handling for promotional messages.
• Treat API acceptance, provider delivery, and end-user display as separate states.

anchorTroubleshooting

A skill is not discovered

Confirm that the selected skill is installed in the correct host or project skills directory, that its folder contains SKILL.md, and that the directory uses the expected skill name. Reload or restart the AI tool.

The plugin is installed but its commands are missing

Check that the installed plugin package contains its manifests, skills/, commands/, and rules/ directories. For local installs, confirm the plugin path points to plugin-packages/webex-connect-ai/, then reload the host.

Sandbox setup asks for MCP authentication

Stop and confirm the selected environment. Sandbox does not use the Production CPaaS MCP server or its credentials.

Sender discovery returns no compatible sender

Do not invent a sender ID. Ask the tenant administrator to approve or expose a sender for the intended channel and use case, then repeat discovery.

A message is queued but not received

Queued means accepted for processing, not delivered. Check the recipient or device registration, sender configuration, channel credentials, provider status, webhook receipts, and tenant logs.

anchorRelated resources

• Webex Skills repository
• Webex Connect skill and plugin catalog
• Webex Connect plugin source
• Webex Connect API overview
• Webex Connect API authentication
• Webex Connect regional API endpoints