ContextSMS MCP (Preview)
Send and read business SMS from authorized ContextSMS business lines. List conversations, read message threads, send one SMS at a time, and check inbound messages.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Copilot Studio | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Sabrhub Technologies |
| URL | https://www.sabrhub.com |
| sabeeh@sabrhub.com |
| Connector Metadata | |
|---|---|
| Publisher | Sabrhub Technologies |
| Website | https://www.sabrhub.com |
| Privacy policy | https://www.sabrhub.com/privacy-policy |
| Categories | Communication;AI |
ContextSMS MCP
ContextSMS MCP connects Microsoft Copilot Studio and Power Platform agents to SabrHub business SMS lines. Each user signs in with their own SabrHub account; the connector only exposes SMS data and phone lines authorized for that user.
Overview
- Publisher: Sabrhub Technologies
- MCP endpoint:
https://mcp.sabrhub.com/mcp - Transport: Streamable HTTP (MCP)
- Protocol header:
x-ms-agentic-protocol: mcp-streamable-1.0 - Backend: SabrHub Teams API (
https://teams-backend.sabrhub.com) - Multi-tenant: One shared MCP URL; per-user OAuth scopes data to that user's business lines
Prerequisites
Before connecting, each user needs:
- An active SabrHub account with at least one provisioned business SMS line mapped to their email
- Permission to send and receive SMS on that line (as configured by their organization in SabrHub)
- Ability to complete OAuth sign-in through SabrHub Hosted UI (
auth-prod.sabrhub.com)
No API key is entered in the connector UI. Authentication is OAuth 2.0 only.
OAuth setup (for administrators)
The connector uses Generic OAuth 2.0 via AWS Cognito.
| Setting | Production value |
|---|---|
| Authorization URL | https://auth-prod.sabrhub.com/oauth2/authorize |
| Token URL | https://auth-prod.sabrhub.com/oauth2/token |
| Refresh URL | https://auth-prod.sabrhub.com/oauth2/token |
| Scopes | openid email profile phone |
| Redirect mode | Global per connector (Power Platform) |
Cognito user pool (prod): us-east-1_I5Il3FWAl
Marketplace app client: Client ID and secret are supplied in Partner Center Packages tab (not in this document).
Tools
| Tool | Type | Description |
|---|---|---|
get_agent_context |
Read | Returns the signed-in user's email and authorized SabrHub business phone lines |
list_conversations |
Read | Lists recent SMS conversations for a business line |
get_message_thread |
Read | Reads recent messages in a customer SMS thread |
poll_inbound_messages |
Read | Polls for new inbound customer SMS (read-only) |
wait_for_inbound_message |
Read | Waits until a new inbound SMS arrives (read-only, rate-limited) |
send_sms |
Write | Sends exactly one SMS from an authorized business line (rate-limited, destructive) |
Example prompts (Copilot Studio)
- "What SabrHub business lines am I authorized to use?"
- "Show the last 20 SMS messages with +15551234567"
- "List my recent SMS conversations"
- "Send an SMS to +15551234567 saying: Your appointment is confirmed for tomorrow at 2pm"
Privacy and support
- Privacy policy: https://www.sabrhub.com/privacy-policy
- Company: https://www.sabrhub.com
- Support: dev@sabrhub.com
Actions
| ContextSMS MCP Server |
Invoke the ContextSMS MCP server over streamable HTTP. |
ContextSMS MCP Server
Invoke the ContextSMS MCP server over streamable HTTP.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Accept
|
Accept | True | string |
HTTP Accept header. Must include both application/json and text/event-stream for MCP streamable transport. |
|
Content-Type
|
Content-Type | True | string |
HTTP Content-Type header for the MCP JSON-RPC request body. |