MCP messaging tools

Learn how Webex MCP Server tools enable AI agents to retrieve enabled sender IDs and send governed, non-templated SMS and email messages through Webex Connect.

Webex MCP Server tools enable AI agents to send governed SMS and email messages through Webex Connect. The tools are backed by Send Message API v2 and use the SMS phone numbers, alphanumeric Sender IDs, and email app assets configured in Webex Connect.

AI agents can use MCP messaging tools to:

  • Retrieve sender IDs for a channel and use case.
  • Send non-templated SMS messages.
  • Send non-templated plain text or HTML email messages.
  • Send email attachments by media URL.

MCP messaging does not support template-based SMS or email messages.

Prerequisites

Before using MCP messaging tools:

  • MCP Messaging for AI Agents must be enabled for the tenant in Webex Connect.
  • The SMS phone number, alphanumeric Sender ID, or email app asset must be enabled for AI Agent Messaging.
  • One or more use cases must be selected for the sender ID or email app asset.
  • The MCP client must be configured with OAuth 2.0 details for the Integration App.
  • The Integration App must include the spark:mcp scope.
  • The AI agent must have a valid access token for the Webex MCP Server.

Available tools

ToolDescription
webex-sender-idsRetrieves sender IDs that are enabled for AI Agent Messaging for the specified channel and use case.
webex-sms-messageSends a non-templated SMS message from an AI Agent-enabled SMS phone number or alphanumeric Sender ID.
webex-email-messageSends a non-templated plain text or HTML email message from an AI Agent-enabled email sender.

Sender ID lookup

Before sending a message, an AI agent can retrieve the sender IDs that are enabled for the requested channel and use case.

For SMS, sender IDs can include eligible SMS phone numbers and alphanumeric Sender IDs. Alphanumeric Sender IDs support outbound, one-way SMS messaging only. Customers cannot reply to messages sent from an alphanumeric Sender ID.

For email, sender IDs include the email sender addresses that are configured in the email app asset and enabled for AI Agent Messaging.

Sender ID lookup returns only sender IDs that meet all of the following conditions:

  • MCP Messaging for AI Agents is enabled for the tenant.
  • The SMS phone number, alphanumeric Sender ID, or email app asset is enabled for AI Agent Messaging.
  • The SMS phone number, alphanumeric Sender ID, or email app asset is mapped to the requested use case.
  • The sender belongs to the tenant associated with the access token.

📘

Note

Sender ID lookup request and response details are available to the AI agent through the Webex MCP Server tool metadata.

SMS messaging

AI agents can send non-templated SMS messages through the webex-sms-message tool. The sender must be enabled for AI Agent Messaging and mapped to the selected use case.

The recipient phone number must be in E.164 format. SMS messages can use text encoding for GSM 03.38 characters or unicode encoding for non-GSM characters, such as emojis, complex symbols, or non-Latin scripts.

Email messaging

AI agents can send non-templated plain text or HTML email messages through the webex-email-message tool. The sender email address must be enabled for AI Agent Messaging and mapped to the selected use case.

Email attachments are supported by media URL.

📘

Note

MCP tool request and response details are available to the AI agent through the Webex MCP Server tool metadata.