Automations, contacts, content assets, data extensions and rows, email, journeys, push, SMS, engagement results, and utility operations.
Marketing CloudEngagement
Marketing Cloud Engagement is included for Salesforce's GA hosted MCP, which lets authorized agents inspect and manage automations, contacts, content, data extensions, email, journeys, push, and SMS through Marketing Cloud APIs.
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.
Inspect content and contact data, data-extension schemas and rows, journey and automation configuration, message assets, engagement results, dependencies, and status across the connected organization.
Create or update content, data extensions and rows, journeys, automations, and messages; sequence multi-step workflows; and perform permitted destructive or send operations through wrapped Marketing Cloud APIs.
A dedicated installed package produces an organization- and package-specific MCP URL. The client uses Marketing Cloud OAuth, and effective access is the intersection of package scopes and the authenticated user's permissions.
Grant only required package scopes, review agent output for accuracy, and use dry runs or planned-code previews for destructive tools. Require explicit confirmation before deletion, broad data-extension updates, journey activation, or any send.
Marketing Cloud API limits still apply. Some tools are asynchronous and require status polling, open-world data extensions have variable schemas, and destructive annotations warn the agent but do not prevent execution when permissions allow it.
First-party access
Documented surfaces
Agent access
MCP support
Support: Official MCP server
Read scope: Read content, contacts, data extensions, journeys, automations, messages, engagement results, dependencies, and operational status allowed by package and user permissions.
Write scope: Create or modify supported content, data extensions, rows, journeys, automations, and messages; permitted tools can also delete data or trigger sends.
Authentication: Marketing Cloud OAuth through an organization- and installed-package-specific hosted MCP URL, yielding a limited-lived token for the signed-in user.
Approval boundary: Preview the organization, business context, object identifiers, dependency impact, and planned tool sequence; require explicit approval before destructive changes, journey activation, transactional messaging, or broad row updates.
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.
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 Salesforce ships them.
Single-platform patterns
- Journey, content, subscriber, and automation cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Marketing Cloud Engagement + CRM or commerce system: lifecycle journey debugger
- Marketing Cloud Engagement + 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.
6 recorded sources
Official Salesforce documentation confirms GA and an organization/package-specific hosted server. Effective access is the intersection of installed-package scopes and user permissions; destructive tools require…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
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.
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.
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.
First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 30, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
- 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.
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.