TrueDialog,
plumbed into
every agent.

One command, no headers — Claude Code runs the OAuth handshake for you:

claude mcp add --scope user --transport http truedialog https://connect.tdmcp.com/

Then run /mcp inside Claude Code and choose Authenticate — a browser opens for the TrueDialog sign-in. After that, the tools are live.

In ChatGPT on the web, open Settings → Connectors (labelled Apps & connectors on newer accounts) → Advanced settings, turn on Developer mode, then Create a connector:

Name:   TrueDialog
URL:    https://connect.tdmcp.com/
Auth:   OAuth (discovered automatically)

Click Create and sign in with your TrueDialog credentials in the popup — ChatGPT registers itself with the OAuth server automatically, nothing to paste. Because TrueDialog exposes write tools, this connector is beta on Business, Enterprise, and Edu only. Pro is limited to read/fetch MCPs, and TrueDialog's tools don't yet publish the read-only annotations ChatGPT would need to expose just the reads — so treat Pro as unsupported for now. Plus and Free get no custom-connector access at all. Eligible users enable Developer mode first (on a managed workspace, an admin turns it on for the workspace). For a live send like send_sms, ChatGPT usually prompts for approval — but that's permission- and context-dependent and can be remembered for a chat, so it's not guaranteed on every send. Developer mode is beta; OpenAI flags it as powerful but risky.

In Microsoft Copilot Studio, add a tool → Model Context Protocol and point the wizard at the endpoint:

Server URL:       https://connect.tdmcp.com/
Authentication:   OAuth 2.0 — Dynamic discovery

“Dynamic discovery” means no Entra app registration — Copilot Studio registers itself with auth.tdmcp.com over DCR. Turn on generative orchestration so the agent can choose tools on its own, then publish the agent to the channels you want — Teams, Microsoft 365 Copilot, or your own site. Adding MCP tools is a Copilot Studio capability, distinct from the consumer M365 Copilot chat.

For the Gemini CLI, add the server to ~/.gemini/settings.json and let it authorize on first use:

{
  "mcpServers": {
    "truedialog": {
      "httpUrl": "https://connect.tdmcp.com/"
    }
  }
}

The first call opens the OAuth sign-in in your browser; if it doesn't, run /mcp auth truedialog inside the Gemini CLI to start it by hand. Gemini Enterprise wires the same endpoint through the admin connector console (set once for the org). MCP support is landing across Gemini's surfaces on different schedules — point any OAuth-capable one at the same endpoint.

For the OpenAI Codex CLI, add the server to ~/.codex/config.toml as a streamable-HTTP MCP server, then log in once:

[mcp_servers.truedialog]
url = "https://connect.tdmcp.com/"
auth = "oauth"
oauth_resource = "https://connect.tdmcp.com/"

codex mcp login truedialog

That opens the browser for the TrueDialog sign-in — Codex does OAuth 2.1 with dynamic client registration, so there's no client id to enter. oauth_resource pins the token to connect.tdmcp.com so the gateway-fronted auth server issues it for the right audience. On older Codex builds that don't default to the remote-HTTP client, also add experimental_use_rmcp_client = true.

GitHub Copilot speaks MCP in the VS Code editor and the Copilot CLI (the github.com coding agent doesn't take remote OAuth MCP servers yet). In VS Code, add the server to .vscode/mcp.json (workspace) or your user mcp.json:

{
  "servers": {
    "truedialog": {
      "type": "http",
      "url": "https://connect.tdmcp.com/"
    }
  }
}

The Copilot CLI uses the same shape under an mcpServers key in ~/.copilot/mcp-config.json (or run /mcp add inside the CLI):

{
  "mcpServers": {
    "truedialog": {
      "type": "http",
      "url": "https://connect.tdmcp.com/"
    }
  }
}

In VS Code, the MCP view shows a Start action; it detects the server's OAuth challenge, registers itself via dynamic client registration, and opens a browser for the TrueDialog sign-in — no client id or token to paste. The tools then appear in Copilot Chat's Agent mode. Remote OAuth in the Copilot CLI is newer and less reliable for gateway-fronted servers — if the browser sign-in doesn't complete, supply a bearer through a headers block, or track copilot-cli#3100/#4096. Needs VS Code 1.102+ (MCP generally available) and an active Copilot plan; on Copilot Business/Enterprise an admin must first turn on the “MCP servers in Copilot” policy (Org/Enterprise settings → Copilot → Policies), which is off by default, and Copilot Free can't use the CLI at all.

No token needed to confirm the server is up and speaking OAuth. An unauthenticated request returns a 401 that points at the OAuth metadata:

curl -sS -i -X POST https://connect.tdmcp.com/ \
    -H 'Content-Type: application/json' \
    -H 'Accept: application/json, text/event-stream' \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Expect HTTP/2 401 with a WWW-Authenticate: Bearer header whose resource_metadata points at connect.tdmcp.com/.well-known/oauth-protected-resource — fetch that to discover the authorization server (auth.tdmcp.com). That challenge is the smoke test. To actually list tools, add a bearer token from the OAuth flow as Authorization: Bearer <token>; your client obtains one for you.