What TrueDialog actually shipped
MCP is the open standard assistants use to call outside tools. The connector links an assistant to a customer's existing TrueDialog account, so messages go out through that account's own sending numbers. TrueDialog says it is available now in the ChatGPT Plugins directory and the Microsoft (Copilot) Connectors directory. Claude, Gemini, Perplexity and other MCP-compatible assistants connect through setup instructions at tdmcp.com, and listings in more marketplaces are said to be underway.
TrueDialog lists these capabilities:
- Sending a text to one number or many in a single request.
- Searching, viewing, creating and updating contacts by asking in plain language.
- A test send before the real one.
- Automatic opt-out handling.
- A choice of short code or long code from the account.
The company's example prompts are ordinary office tasks, like texting 25 numbers an orientation reminder or updating a contact's mobile number. These are vendor examples, not evidence of customer results.
Fees and sign-in
TrueDialog says customers keep the full platform, native integrations and API at standard pricing, with no added fee for the MCP. So "no added fee" does come from the company's own release, not only the UC Today brief. It is still a vendor claim, and your TrueDialog plan and message volume still apply.
Existing customers sign in with their TrueDialog login, and new users can start a trial from the same flow. The setup site describes OAuth 2.1 browser sign-in against the same TrueDialog credentials used for the portal. It says no API keys need to be pasted into the client. The assistant holds a short-lived token rather than your password.
Tool-level details for admins
The setup documentation lists nine tools, six read-only and three that write. The write tools are create_contact, update_contact and send_sms.
- Read-only tools:
whoami,list_accounts,get_account_info,list_channels,get_contactandsearch_contacts. - Live sends are real by default. The documentation says
send_smsreaches live phones unless you passexecute=falsefor a dry run. - Dry runs use up capacity. A dry run counts toward the connector's send caps just as a real send does. Running one right before a live send to the same numbers can use up the room the real send needs.
- Replies aren't read.
send_smsis one-way, so it doesn't read replies. - Contact edits can't change an existing number.
update_contactwon't change or clear the number on a contact that already has one. TrueDialog keeps an SMS opt-out on the contact, so moving the number would free the old one. You create a new contact instead. - Edits aren't atomic.
update_contactreads the record first and rewrites only the fields you supply, but it isn't atomic against a concurrent edit. - Duplicates are rejected.
create_contactrejects a duplicate rather than quietly creating a second record.
TrueDialog says overwrites and live sends carry "destructive" safety annotations. ChatGPT may ask for approval depending on its policy and the conversation context. That prompt is the assistant's behavior, not a control you set, so don't treat it as your approval process.
RCS: the launch claim and the tool list
The announcement says users can send SMS and RCS. The only outbound tool in the setup documentation is send_sms, and it is described as sending SMS. The channel lookup tool does list RCS among the channel types on an account. The documentation doesn't say that the MCP tool sends RCS through send_sms. Until TrueDialog clarifies, treat RCS sending through the MCP as an announcement claim rather than a documented tool behavior.
Where Copilot fits, and where it doesn't
"Copilot" covers several surfaces here, and the TrueDialog setup page is careful about this. For Microsoft Copilot Studio, you add a Model Context Protocol tool, point it at the endpoint and choose OAuth with dynamic discovery. The page says this needs no Entra app registration. It also says that adding MCP tools is a Copilot Studio capability, distinct from the consumer Microsoft 365 Copilot chat. You can then publish the agent to Teams, Microsoft 365 Copilot or a site. If you only use Copilot chat, check what your tenant actually exposes before assuming this works.
GitHub Copilot is covered too, but only in the VS Code editor and the Copilot CLI. The setup page says the github.com coding agent doesn't take remote OAuth MCP servers yet. It says VS Code 1.102 or later and an active Copilot plan are required. On Copilot Business and Enterprise, an admin must first turn on the "MCP servers in Copilot" policy, which is off by default. For a developer, that is a policy decision to make deliberately.
How it differs from the existing Microsoft connector
TrueDialog already has a Power Platform route. Microsoft Learn documents a TrueDialog SMS connector for Copilot Studio, Power Apps, Power Automate and Logic Apps. The connector is Premium in Copilot Studio, Power Apps and Power Automate, and Standard in Logic Apps. The Power Platform regions exclude US Government (GCC), GCC High, DoD and China Cloud operated by 21Vianet. Logic Apps lists its own Azure Government, Azure China and DoD exclusions.
That older connector uses an account username and password. Microsoft says it also needs your TrueDialog API key and secret from your registration email. It supports contact create, search and update, account lookups and sending. It adds triggers for incoming messages, STOP messages, keywords, delivery notices and invalid targets. It is built for deterministic flows, meaning you design the steps. The MCP is built for an agent that chooses its own steps. Those are different risk profiles, and the Learn page doesn't establish feature parity between them. Learn also notes that the TrueDialog API has more capabilities than the custom connector.
The MCP documentation says the connector currently advertises only the nine tools. The incoming-message and STOP triggers appear in the Power Platform connector, not in that tool list.
Practical guidance before you enable it
- Test in a non-production account first. The live-send default is the main hazard.
- Start with read-only use. TrueDialog says developers choose which tools an agent may use, including read-only agents that cannot send. Use that to stage a rollout.
- Confirm who can connect. On managed ChatGPT workspaces, the setup page says an admin may need to enable Developer mode. On Claude Team and Enterprise, an Owner must enable the connector for the organization first. Plan and workspace availability are controlled by each vendor and may change.
- Keep a human in the loop for bulk sends. TrueDialog says opt-outs are honored automatically. That doesn't confirm the recipient list or the message text. Consent, recipient accuracy and message content remain your responsibility.
- Budget for dry runs. Capacity is consumed, so don't stack a dry run immediately before a live send to the same list.
- Check regional limits. If you work in a government cloud, the Microsoft connector exclusions above are worth reading before you plan a Power Platform route.
Bottom line
The launch is a tidy example of assistants moving from drafting text to acting on it. The company's claims about compliance and opt-outs are its own, and the tool documentation shows real constraints. Treat this as a configurable integration that needs permission design, not a switch to flip.
References
- TrueDialog Brings Business Texting to ChatGPT and Copilot - UC Today UC Today · 2026-11-17T17:00:32.068000+00:00
- TrueDialog Launches MCP for ChatGPT, Copilot, and Other AI Assistants - TrueDialog truedialog.com
- TrueDialog Launches MCP for ChatGPT, Copilot, and Other AI Assistants prnewswire.com