01 · Records and state owned
Forms and fields, smart campaigns and flow steps, leads, static lists and membership, programs, emails and snippets, folders, channels, tags and activity types, plus bulk lead-export jobs.
Adobe
Adobe MarketoEngage
Included because Adobe's hosted Marketo MCP exposes more than 100 operations across campaign assets, people, lists, programs, bulk exports, and instance configuration through the same REST permission boundary.
Marketing automation, lifecycle & CDPSystem of engagementAgent-accessible SaaS
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
Browse campaign assets and instance structure, inspect smart-campaign activity and flow steps, find leads, inspect list membership, and export lead data or check bulk-job status.
03 · Actions and write paths
Create, clone, modify, and approve forms; create and activate or deactivate smart campaigns; create or update leads and list membership; create or clone programs; and create or edit emails and snippets.
04 · Authentication and permissions
Each request carries either an Adobe IMS bearer token plus IMS Org ID or Marketo client credentials plus Munchkin ID. Marketo credentials derive permissions from a dedicated API-only user's role and workspace access.
05 · Monitoring, approval, and recovery
Use a dedicated least-privilege API user, keep the target Munchkin instance visible, separate production and staging connections, track quota by API user, and review every MCP-initiated action and response before relying on it.
06 · Limits and caveats
Access is limited availability and requires an enabled, allowlisted Marketo instance with REST API access. Calls inherit the instance's API rate limits, and Adobe provides the MCP integration as-is for customer-elected use.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverAdobe-hosted Marketo Engage MCP serverLimited availability; access must be requested for an eligible Marketo instance
Support: Official MCP server
Read scope: Read forms, programs, smart campaigns, leads, lists, emails, snippets, folders and instance configuration, and run supported lead-export workflows.
Write scope: Create and modify campaign assets, leads, list membership, programs and content, including form approval and smart-campaign activation or deactivation.
Authentication: Remote streamable HTTP with per-request Adobe IMS token and Org ID headers or Marketo Client ID, Client Secret, and Munchkin ID headers; the server refreshes Marketo OAuth tokens automatically.
Approval boundary: Show the target instance, workspace, asset or audience, proposed field changes, and activation state before approving a form, activating a campaign, editing message content, or changing lead and list data.
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 access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
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 Adobe ships them.
Single-platform patterns
- B2B campaign and marketing-operations cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Adobe Marketo Engage + CRM or commerce system: lifecycle journey debugger
- Adobe Marketo Engage + 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.
3 recorded sources
MCP / agent-role validationRepresentative source
https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/mcp-server ↗Official Adobe documentation confirms a public remote endpoint, IMS-token or Marketo client-credential authentication and an evolving operation catalog. Marketo release notes label it Open Beta; distinguish…
- Publisher updated
- Apr 27, 2026
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developer.adobe.com/marketo-apis/ ↗First-party API reference or API overview recorded for this platform.
- 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://business.adobe.com/products/marketo/adobe-marketo.html ↗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.
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.