TrueDialog MCP (Preview)

TrueDialog is a business SMS texting platform used by organizations to reach customers, students, and employees at scale. This connector gives agents secure, OAuth-protected access to a TrueDialog account so they can send outbound text messages, find, create, and update contacts, and look up channels and account details. Use it to automate reminders, notifications, and outreach directly from agent conversations.

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 TrueDialog Support
URL https://tdmcp.com
Email support@truedialog.com
Connector Metadata
Publisher TrueDialog, Inc.
Website https://tdmcp.com
Privacy policy https://tdmcp.com/privacy
Categories Communication;IT Operations

TrueDialog MCP

TrueDialog is a carrier-grade SMS platform. The TrueDialog MCP connector lets an agent send outbound SMS and manage contacts, channels, and account details in a TrueDialog account, through TrueDialog's remote MCP server at https://connect.tdmcp.com/.

TrueDialog remains the system of record. The MCP server is a thin, stateless bridge: it stores no credentials server-side and keeps nothing durable of its own.

Publisher: TrueDialog Inc.

Prerequisites

  • An active TrueDialog account with an SMS channel and API access. No signup happens inside the connector.
  • Sign-in uses your TrueDialog username and password. TrueDialog SSO (OneLogin) users cannot sign in to the connector.

Obtaining Credentials

The connector signs in with OAuth 2.0 through TrueDialog's authorization server at auth.tdmcp.com. No API key or client registration is needed on your side: use the username and password of your TrueDialog account. To get a TrueDialog account, contact TrueDialog at https://www.truedialog.com.

Getting Started

  1. In Copilot Studio, open your agent, go to Tools, select Add a tool, and choose TrueDialog MCP (Model Context Protocol).
  2. Create a connection. A sign-in window opens at auth.tdmcp.com; sign in with your TrueDialog credentials and approve access. The connection holds a short-lived OAuth 2.0 token and never sees your password.
  3. The agent can now discover and call the tools listed below.

The connector also has a Check server health action, usable from Power Automate, that returns OK when the TrueDialog MCP server is reachable.

Supported Operations

Ten tools: 6 read-only and 4 write. Only send_sms transmits to live phone numbers.

Tool Access What it does
whoami read Confirm the authorized user and account.
list_accounts read List accounts visible to the signed-in user.
get_account_info read Retrieve details for one account.
list_channels read List configured messaging channels.
get_contact read Retrieve one contact record.
search_contacts read Search contacts by phone or email substring.
create_contact write Create a contact record.
update_contact write Update fields on an existing contact.
send_sms write Send an outbound SMS. Reaches live phones.
report_issue write File a bug or feedback report with TrueDialog support.

send_sms accepts execute=false for a dry run. A dry run does not transmit and consumes no credits, but it does still create a campaign record.

update_contact is annotated destructive: it can overwrite or clear existing phone, email, or name fields on the selected contact.

About report_issue

report_issue is a support channel, not a TrueDialog data operation. It transmits a user-authored problem report (a category, a one-line summary, a free-text detail, and optionally the tool name and the verbatim error text) to the publisher's own support mailbox, and returns a reference_id to quote when following up. It delivers only there and cannot address arbitrary recipients.

It is designed to require human confirmation: the agent is instructed to show you the exact text before submitting and never to file a report silently. It must not include message bodies, recipient numbers, customer names, or credentials; the server scrubs credential-shaped text as a backstop, but the instruction to the agent is to describe the problem rather than the data. A contact_email is included only if you volunteer one.

Known Issues and Limitations

  • Outbound only. This server sends SMS; it cannot retrieve inbound messages, replies, or conversation threads. TrueDialog inbound is push-only into a separate product. An agent asked "what did they reply?" has no tool here that can answer.
  • Tool descriptions mention an optional pack that is off on this endpoint. Several descriptions refer to inbox_* tools; for example send_sms points at inbox_sms_send for conversational threads. Those belong to an optional Inbox tool pack that is not enabled here. Each reference is written conditionally and says so ("if you see no inbox_* tools, it is not exposed here"), so the tool list you receive is authoritative. Nothing outside the ten tools above is callable.
  • send_sms transmits for real by default. execute defaults to true. Use execute=false to rehearse.
  • send_sms fans out. One call accepts multiple recipients, so a single invocation can send many messages. Review the recipient list before confirming.
  • Compliance stays with you. You send from your own account under your own carrier registration and remain responsible for recipient consent, opt-out handling, and 10DLC/TCPA obligations. The force_opt_in parameter can reach contacts who have opted out and should be used only where you have a lawful basis for doing so.
  • Two contact stores exist; this connector writes one. The TrueDialog platform contact store is keyed by integer ids. It is not the same store as an Inbox organization's, which uses UUIDs and is not reachable here.
  • No scheduled or recurring campaigns. Sends are immediate and point-to-point.
  • One account per authorization. Tools act on the account the token authorizes; operating across accounts requires re-authorizing.

Frequently Asked Questions

Does the connector store my TrueDialog password? No. You enter it only on TrueDialog's own sign-in page; the connection holds an OAuth token.

Can I test a send without texting anyone? Yes. Call send_sms with execute=false.

Why can't I read replies? Inbound messages are not available through this server. See Known Issues and Limitations.

Deployment Instructions

Add the certified TrueDialog MCP connector from the tool list in your agent; no custom deployment is required.

Support, privacy, and terms

Publisher: TrueDialog Inc.

Actions

Check server health

Returns OK when the TrueDialog MCP server is healthy.
Invoke MCP server

Handles communication with the TrueDialog MCP server, which exposes tools to send SMS and manage contacts, channels, and account details.

Check server health

Operation ID:
HealthCheck

Returns OK when the TrueDialog MCP server is healthy.

Returns

response
string

Invoke MCP server

Operation ID:
InvokeMCP

Handles communication with the TrueDialog MCP server, which exposes tools to send SMS and manage contacts, channels, and account details.

Returns

response
object

Definitions

string

This is the basic data type 'string'.

object

This is the type 'object'.