Connectors
Commanders Act, Tealium and OneTrust
Connect Commanders Act, Tealium and OneTrust through each vendor's official MCP server. Who has to enable what, steps, limits and troubleshooting.
Up to date with v1.5.4Updated 26 October 20263 min read
Three tag-management and privacy vendors publish their own MCP server. Each one needs something different before it connects, so this page has a section per vendor.
Before you start#
| Tool | What Henkan can read | What the vendor requires |
|---|
| Commanders Act | Tag management, server-side, sources and destinations, data and audiences, privacy (cookie scanner results, consent statistics), monitoring, reporting and administration. Read-only. | A closed beta. Ask Commanders Act support or your account manager to open it for your organisation; they send you the MCP address. You sign in with your Commanders Act account (SSO and two-factor work) and Henkan has your user permissions. |
| Tealium | Server-side profiles: data sources, event feeds and specifications, attributes, audiences (without segments), connectors, rules and labels. Not client-side Tealium iQ, and not consent orchestration. | Available to selected customers: ask Tealium support. An admin then sets MCP Server to On in AI Settings for the account and each profile, and gives you access: Reader (legacy permissions) or MCP Server: Viewer under AI Access (platform permissions). Pick your default account and profile in Edit/View User Settings › Tealium Configuration MCP. |
| OneTrust | OneTrust's developer portal: its API reference (privacy requests (DSAR), inventories, assessments) and a tool that prepares API requests. No cookie-consent data or consent rates. | Nothing: no sign-in. Reading your own OneTrust data needs a OneTrust API token, which this connector doesn't store. |
Connect#
- Open Tools In the sidebar, select Tools, then select Commanders Act, Tealium or OneTrust.
- Commanders Act: paste your address Select Add my Commanders Act address, paste the MCP address Commanders Act sent you and select Save. A sign-in window opens.
- Tealium: sign in Select Sign in with Tealium. Enter your account name, then your username and password or SSO, and select Yes to allow access.
- OneTrust: add it Select Add OneTrust. It connects straight away.
- Check the result The tile shows Connected, and Advanced settings › Tool by tool lists the vendor's tools.
What you can ask#
- "Which tags fire on the checkout pages, and which ones have no consent category?" (Commanders Act)
- "How did the consent rate change over the last 30 days?" (Commanders Act)
- "Explain the rules feeding the high-value-customer audience in our server-side profile." (Tealium)
- "Which OneTrust API returns the status of a privacy request?" (OneTrust)
Limits and good to know#
- Commanders Act addresses are per organisation. The address must be on commandersact.com or commander1.com for Henkan to show it under the Commanders Act tile; any other address still works as a custom server.
- A configured tag doesn't prove delivery. Commanders Act says so itself: check the destination's own reporting.
- Tealium only covers server-side. For client-side Tealium iQ, there is no official MCP yet.
- Costs and who pays. Your Henkan plan covers the AI requests: each question counts towards your organisation's requests (see Usage and limits). Usage on the vendor's side falls under your contract with that vendor.
Troubleshooting#
| Error or symptom | Fix |
|---|
| Commanders Act: no address | The MCP server is in closed beta. Ask Commanders Act support or your account manager. |
| Tealium sign-in works but there is no data | MCP Server isn't on for the account or the profile, or your user has no MCP access. Ask your Tealium admin. |
| Tealium shows the wrong profile | Change the default in Edit/View User Settings › Tealium Configuration MCP, then connect again. |
| OneTrust can't read our account | Expected: this connector reads OneTrust's public API reference, not your account data. |
Sources#