01 · Records and state owned
Customer schemas, audiences, journeys, campaign concepts, email and SMS content, visual ad creatives, existing Ad Studio projects, and marketing performance context.
Hightouch
Hightouch
Hightouch belongs in Atlas because its hosted MCP combines customer-data-aware audience and journey design with campaign content generation and performance analysis inside an authenticated workspace.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaSReverse ETL / activation
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Inspect customer schemas and data, browse Ad Studio projects, analyze campaign performance, and iteratively evaluate audience, journey, content, or creative concepts.
03 · Actions and write paths
Create and save audiences, design journeys, generate email or SMS content for Lifecycle Studio, and produce or refine visual creatives in Ad Studio.
04 · Authentication and permissions
Operations run in the user's authenticated Hightouch workspace and inherit existing role-based access controls; the public page does not specify the underlying client authentication exchange.
05 · Monitoring, approval, and recovery
Workspace RBAC remains authoritative, and Hightouch exposes results for iterative review before saving; destination launch, delivery, or synchronization is not documented as an MCP action.
06 · Limits and caveats
MCP enablement is unavailable in some workspaces. Core audience and analysis capabilities serve enabled customers, while content and creative functions require Lifecycle Studio or Ad Studio.
First-party access
Documented surfaces
Warehouse SQL models ↗Hightouch runs queries directly against connected customer warehouses and databases to build models. SQL executes against the customer's source; source-specific credentials, roles, and Hightouch permissions govern access.Source: Sources overviewHightouch Reverse ETL ↗Hightouch explicitly calls its warehouse-to-destination data activation process Reverse ETL. Destination execution is a native platform capability and must not be attributed wholesale to the separately documented Hightouch MCP server.Source: Data activation conceptsMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP support
Official MCP serverHightouch hosted marketing MCPCurrent documented service
Support: Official MCP server
Read scope: Read customer schema and data context, inspect existing creative projects, compare campaign performance, and evaluate audiences, journeys, content, or campaign concepts conversationally.
Write scope: Create and save audiences, design customer journeys, draft Lifecycle Studio email or SMS content, and generate or refine Ad Studio visual creatives.
Authentication: A compatible MCP client connects to an authenticated Hightouch workspace; the reviewed page confirms workspace scoping but does not publish the token or browser authorization sequence.
Approval boundary: Review audience logic, journey design, content, and creatives before saving; separately approve any downstream synchronization, campaign launch, or delivery because those actions are not documented here.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Hightouch ships them.
Single-platform patterns
- Warehouse-native audience and activation control room
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Hightouch + CRM or commerce system: lifecycle journey debugger
- Hightouch + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
7 recorded sources
MCP / agent-role validationRepresentative source
https://hightouch.com/docs/ai-integrations/mcp ↗Workspace-scoped reads and actions, role-based access, enablement, Lifecycle Studio eligibility, and Ad Studio eligibility
- Publisher updated
- Jul 8, 2026
- BYO-UI reviewed
- Jul 22, 2026
Hightouch MCP scope, RBAC, and product eligibility reviewed 2026-07-22
APISource inventory
https://hightouch.com/docs/api-reference ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://hightouch.com/docs ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://hightouch.com/docs/sources/overview ↗Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://hightouch.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://hightouch.com/docs/events/sources/webhook ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Sep 20, 2024
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Hightouch Reverse ETLTargeted review
Data activation concepts ↗Hightouch explicitly calls its warehouse-to-destination data activation process Reverse ETL. Destination execution is a native platform capability and must not be attributed wholesale to the separately documented…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.