Marketo MCP vs REST API: the shift MOps teams can’t ignore in 2026
- 1. What actually separates them
- 2. What each interface can do and where the gaps are
- 3. On deck: confirmed but not yet live
- 4. Intentionally disabled: destructive operations
- 5. What the REST API simply can't do
- 6. The right answer: use both
- 7. What this means for your team
- 8. Ready to see Marketo + AI in action for your team?
Marketo MCP vs REST API the shift MOps teams can’t ignore in 2026. REST API is Marketo’s backbone, comprehensive, developer-facing, and built around raw JSON responses. That power comes with a cost: you need to know exactly what you’re asking for, and how to ask for it. MCP works differently. Rather than constructing API calls, you describe what you need in plain language and let an AI handle the execution. It runs on top of your existing Marketo instance and exposes 130 named, self-describing tools that an AI can reason about natively, with more being added regularly. A simple way to think about it: the REST API gives full access to every corner of the platform. MCP narrows that to the tools marketing teams actually reach for, and makes them accessible without technical mediation. In practice, MCP handles the bulk of day-to-day marketing operations work. The REST API stays the right choice for data engineering, CRM integration, and anything requiring complete platform control. The table below covers both interfaces across every key capability area: what’s live in MCP today, what’s confirmed but not yet enabled, and what remains REST-only. Remember: ✅ = Available | ❌ = Not available | 🔜 = In MCP but not yet enabled (beta). REST API entries reflect current Adobe Experience League. documentation. Most comparisons only cover what’s live. That misses something important. Adobe has already built far more than what’s currently enabled. Dozens of tools exist in the MCP server right now, they’re just not switched on yet. Some are still in testing. Others touch higher-risk operations and need additional guardrails before they go live. The table below lists everything confirmed as upcoming. Not everything missing from the MCP is a gap waiting to be filled. Some operations are deliberately blocked and for good reason.These tools exist in the codebase but won’t be enabled anytime soon. The logic is straightforward: an AI executing irreversible actions at scale, deleting programs, merging leads incorrectly, wiping assets could cause serious damage to a live Marketo instance. Until there are robust safeguards in place, they stay off. A deliberate call and the right one. For operations like these, the REST API is the appropriate interface. Execution should sit with a developer or automated process that has proper safeguards, audit logging, and rollback planning in place not a conversational AI acting on a natural language prompt. Some MCP tools don’t map to anything in the REST API, they were built specifically for AI-assisted workflows and don’t exist anywhere else: At Kapturall, we don’t frame this as an either/or decision. Here’s how we think about it: Tip: Need to know how many people attended a webinar? Build a custom If you’re running Marketo integrations through the REST API today, Salesforce sync, HubSpot, custom data pipelines, nothing changes. Your existing architecture stays exactly as it is. Where MCP opens things up is AI-assisted MOps: giving marketing operations users, not just developers, the ability to query and manage Marketo through conversational AI. And with Journeys, Emails, Landing Pages, and Email Templates all on the way, that scope is growing fast! A few practical next steps to get ahead of it: At Kapturall, we’re already running MCP-integrated workflows for clients across MOps, CRM integration, and lifecycle marketing and the results are changing how teams work. Talk to us and see what’s possible for your instance.What actually separates them
What each interface can do and where the gaps are
Capability area
Functionality
REST API
MCP live
MCP upcoming
Programs
Browse, create, clone, approve, tags
✅
✅
Programs
Get creation options (channels, tag types)
❌
✅
Smart campaigns
Browse, create, schedule, flow steps
✅
✅
Smart campaigns
Flow step metadata discovery & auto-suggest
❌
✅
Smart campaigns
Deactivate smart campaign
✅
❌
🔜
Smart lists
Browse, create, rules management
✅
✅
Smart lists
Full rule catalog + auto-suggest
❌
✅
Smart lists
Add / update rules with AI
❌
❌
🔜
Smart lists
Get lead count
✅
❌
🔜
Smart lists
Delete smart list / delete rule
✅
❌
🔜
Static lists
Browse, create, members management
✅
✅
Static lists
Delete list
✅
❌
🔜
Forms
Full CRUD, fields, visibility rules
✅
✅
Forms
Update submit button / thank you page
✅
❌
Emails
Browse, create, get/update content
✅
✅
Emails
Delete, clone, unapprove, discard draft
✅
❌
🔜
Emails
Modules, dynamic content, variables, sample send
✅
❌
🔜
Email templates
Browse, get by ID, get content
✅
❌
🔜
Email templates
Create, update, approve, clone, delete
✅
❌
🔜
Landing pages
Browse, get by ID/name, get content
✅
❌
🔜
Landing pages
Create, update, approve, clone, delete
✅
❌
🔜
Landing pages
Update dynamic content, add/update/delete sections
✅
❌
🔜
Landing page templates
Browse, get, create, update, approve, clone, delete
✅
❌
🔜
Journeys
Browse, get by ID/count, node membership count
✅
❌
🔜
Journeys
Get publish graph export, abort, close, delete
✅
❌
🔜
Files / Design Studio
Browse, get by ID/name, create, update
✅
❌
🔜
Snippets
Browse, get, CRUD, approve, dynamic content
✅
✅
Leads
Get by email/ID, describe fields, activities
✅
✅
Leads
Sync (create/update), merge
✅
❌
🔜
Leads
Delete, partitions, program status, changes
✅
❌
Bulk export
Export leads (create/enqueue/status)
✅
✅
Bulk export
Export program members, activities, custom objects
✅
❌
Custom objects
Get, sync, delete, schema management
✅
❌
Companies
Get, sync, delete, field schema
✅
❌
User management
Browse, invite, update, delete users & roles
✅
❌
Faceted analysis
Aggregate & visualise data (pie charts, tables)
❌
✅
On deck: confirmed but not yet live
Capability area
Tools not yet enabled
Internal-API wrappers
add_smart_list_rules_with_ai
update_smart_list_rules_with_ai
get_smart_list_lead_count
Journeys
browse_journeys
get_journey_by_id
get_journey_count
get_journey_node_membership_count
get_publish_graph_export
abort_journey
close_journey
delete_journey
Emails
delete_email
unapprove_email
clone_email
discard_email_draft
update_email
update_email_dynamic_content
send_sample_email
Email templates
browse_email_templates
get_email_template_by_id
get_email_template_by_name
get_email_template_content
create_email_template
update_email_template
update_email_template_content
delete_email_template
approve_email_template
unapprove_email_template
clone_email_template
discard_email_template_draft
Landing pages
browse_landing_pages
get_landing_page_by_id
get_landing_page_by_name
get_landing_page_content
create_landing_page
update_landing_page
update_landing_page_content
update_landing_page_dynamic_content
delete_landing_page
approve_landing_page
unapprove_landing_page
clone_landing_page
discard_landing_page_draft
add_landing_page_section
update_landing_page_section
delete_landing_page_section
Landing page templates
browse_landing_page_templates
get_landing_page_template_by_id
get_landing_page_template_by_name
get_landing_page_template_content
create_landing_page_template
update_landing_page_template
update_landing_page_template_content
delete_landing_page_template
approve_landing_page_template
unapprove_landing_page_template
clone_landing_page_template
discard_landing_page_template_draft
Files / Design Studio
browse_files
get_file_by_id
get_file_by_name
create_file
update_file
Intentionally disabled: destructive operations
Capability area
Disabled operations
Lists
delete_list
Smart lists
delete_smart_list
delete_smart_list_rule
Smart campaigns
deactivate_smart_campaign
Programs
delete_program
Leads
merge_leads
create_or_update_leads
What the REST API simply can't do
Capability
What it does
REST equivalent
Faceted analysis
Tools like
facet_smart_campaigns and facet_snippets aggregate and visualise your Marketo data as pie charts and tables inline. The REST API returns raw records — all the analysis is on you.❌
Rule & flow step discovery
Tools like
get_smart_list_rules and get_smart_campaign_flow_step_types expose a full metadata catalog of every filter, trigger, and flow step available in your instance. Without this, an AI has no way to build campaigns correctly from scratch.❌
AI-powered smart list rules (coming soon)
add_smart_list_rules_with_ai and update_smart_list_rules_with_ai are internal-API wrappers not yet enabled — but when they are, they’ll allow an AI to construct and modify smart list rules using natural language rather than explicit filter and trigger IDs. A genuinely new capability with no REST equivalent.❌
Auto-suggest & creation options
get_smart_campaign_auto_suggest, get_smart_list_auto_suggest, and get_program_creation_options are MCP-specific abstractions that help an AI plan and configure Marketo assets correctly before executing.❌
The right answer: use both
Layer
Recommendation
Day-to-day MOps
Use MCP for day-to-day marketing operations workflows — campaign queries, smart list analysis, program management, snippet management, and soon email and landing page operations.
Data & integrations
Use REST API for data engineering, CRM integration (especially Salesforce sync), bulk operations, and anything requiring full programmatic control with audit logging.
Destructive operations
Treat disabled destructive operations as a feature, not a limitation. Keep delete, deactivate, and merge operations behind REST API calls with proper change management processes.
Bridging the gaps
Bridge remaining gaps with custom MCP tools. Most AI agent platforms that support MCP allow you to register additional tools alongside the official set — wrapping REST endpoints in custom tools for capabilities not yet in the MCP.
get_program_members_by_status tool that wraps the REST call, register it with your AI agent, and it answers that question as naturally as any other MCP tool.
What this means for your team
Ready to see Marketo + AI in action for your team?
SIGN UP FOR OUR NEWSLETTER
Juan Pablo García
Sales Manager at Kapturall
Sales professional with over three decades of experience in the tech industry. I specialize in building valuable partnerships with key players across several sectors. My strength lies in my deep understanding of customers' needs, a dedicated approach to service, and a knack for creating lasting relationships. I combine tried-and-true methods with the latest sales and marketing technologies, always focused on delivering value. I believe that every interaction, whether it results in a deal or not, is an opportunity to serve the customer and pave the way for future opportunities.
Related Content
