Learn how Webex MCP Server tools enable AI agents to retrieve sender IDs and send non-templated SMS and email messages through Webex Connect.
Webex MCP Server tools enable AI agents to send 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 information for a channel.
- 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:
- An administrator must enable MCP messaging in Control Hub.
- Create or use an OAuth 2.0 Integration App in the Webex Developer Portal.
- Configure the
spark:mcpscope for the Integration App. - Obtain a valid access token for the Webex MCP Server.
- Configure the sender or email app asset required for the requested channel.
Authentication and authorization continue to apply to every MCP request. Webex Connect also validates the tenant, requested channel, sender, and message before processing the request.
Available tools
| Tool | Description |
|---|---|
webex-sender-ids | Retrieves the sender information available to the tenant for the requested channel. |
webex-sms-message | Sends a non-templated SMS message from an available SMS phone number or alphanumeric Sender ID. |
webex-email-message | Sends a non-templated plain text or HTML email message from an available email sender. |
Sender ID lookup
Before sending a message, an AI agent can use the webex-sender-ids tool to retrieve the sender information available for the requested channel.
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 SMTP email assets, the response contains the sender email addresses available for the tenant.
For domain-based email app assets, the response contains the domain or domains configured for the tenant. The MCP client or AI agent selects a returned domain, supplies the local part, and constructs the sender address as <local-part>@<returned-domain>.
The sender information must be valid for the requested channel and belong to the tenant associated with the access token. The client or agent must use the sender information returned by the tool when sending the message.
Note
Sender 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.
Before sending a message, use webex-sender-ids to retrieve a sender ID that is available for the SMS channel. Pass the selected sender ID in the SMS message request.
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.
Before sending an email, use webex-sender-ids to retrieve an available sender for the email channel.
- For SMTP email assets, select one of the returned sender email addresses.
- For domain-based email app assets, use a returned domain and construct the sender address as
<local-part>@<returned-domain>.
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.
