In short
Copilot Studio agents can use OmniChannels.ai by adding our remote MCP server, https://mcp.broadnet.me/mcp, as an agent tool with your token sent in the Authorization header. The agent can then send WhatsApp, SMS and RCS messages, use approved templates and read delivery reports. Alternatively, a Power Platform custom connector can call our REST API. There is no marketplace connector to install.
What you can do
Notify customers from an internal agent
A service agent your team uses in Teams sends a WhatsApp or SMS update on request.
Try asking
“Send an SMS to 447700900123 saying the technician arrives at 3 pm.”
Approved templates in Arabic and English
The agent lists your approved WhatsApp templates and fills the right one, so business-initiated messages stay within WhatsApp's rules.
Try asking
“Send the order_update WhatsApp template in Arabic to 966500000000 with order number INV-400.”
Delivery checks for support staff
Give a support agent only the delivery report tool so it can explain why a message failed.
Try asking
“Did the last message to 971500000000 get delivered, and if not, why?”
Updates based on Dynamics 365 records
When the agent also has a connector to Dynamics 365 or Dataverse, it reads the records there and sends through OmniChannels.ai.
Try asking
“Send a WhatsApp reminder to customers with a service visit booked for tomorrow.”
How it connects
OmniChannels.ai runs a remote MCP server over Streamable HTTP. Copilot Studio can add MCP servers to an agent as tools: you give it the server URL and choose an authentication type. Where the wizard offers API key authentication in a header, use the header name Authorization and the value Bearer followed by your token. Each tool then acts with your account's permissions, sender IDs and balance.
If the MCP route does not suit your tenant, build a Power Platform custom connector for our REST API. Custom connectors import OpenAPI 2.0 definitions, while our public spec is OpenAPI 3.1, so convert the parts you need or define the actions by hand. Bulk and most channel sends use multipart/form-data, so start with the JSON single SMS endpoint and test each action.
- Endpoint: https://mcp.broadnet.me/mcp (Streamable HTTP)
- Authentication: Authorization: Bearer <token>
- Alternative: custom connector to https://api.broadnet.me
- Custom connectors take OpenAPI 2.0; our spec is 3.1
- Menus and licensing change; check Microsoft's current documentation
Set it up
- 1
Request API access
Request test access and receive an API token. Test sends go only to your own verified numbers.
- 2
Get an MCP key
In the admin portal open Integrations, then MCP Integration, and copy a temporary key.
Guide: MCP server for AI agents - 3
Add the MCP server as a tool
In your agent's tools, add a new Model Context Protocol tool with the server URL and header-based authentication carrying Bearer and your token.
- 4
Keep only the tools you need
Turn off tools the agent does not need and review how the agent confirms actions before it sends real, billed messages.
- 5
Or build a custom connector
Define actions against https://api.broadnet.me with a Bearer token, converting the OpenAPI 3.1 spec or writing actions by hand.
Guide: OpenAPI 3.1 spec - 6
Test with your own number
Send a test message to your verified number from the test pane, then check the delivery report.
Vendor documentation
Microsoft Copilot Studio is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Microsoft Copilot Studio; this page describes a connection built with Microsoft Copilot Studio's own MCP, HTTP or webhook features.
