Unverified50% confidenceFactExact time
The project connects Marketing Cloud Engagement (not MC Next) with Agentforce, bridging the two sides through an MCP server, which was uncommon at the time.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/13/2026
First Seen
Valid until: 1/11/2027
Sources
Related Entities
Related Claims
UnverifiedFor teams dealing with trade secrets or compliance requirements, building a self-hosted MCP server (such as deploying an open-source implementation on a private cloud) may be a more prudent alternative path.70% similarVerifiedOpen Agent Builder natively supports the MCP protocol and can connect to existing MCP tool servers in the community.70% similarUnverifiedMCP主要解决的是Agent与工具/数据源的连接问题，而非Agent-to-Agent实时通信70% similarUnverifiedDevin Gisonno has already started trying to use an MCP server to migrate a complete journey from Marketing Cloud Engagement to MC Next; although some things need to be reconfigured after migrating to Flow (because Flow connects to Data Cloud objects rather than Data Extensions), the core structure of the journey mapping can be migrated successfully.69% similarUnverifiedUnlike AgentReach, an MCP server exposes a unified protocol endpoint as an intermediate layer, meaning every call must pass through that intermediate layer, which can become a performance bottleneck or single point of failure.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016704API
curl https://kongchang.com/api/v1/knowledge/claims/1016704MCP
get_claim(id=1016704)