Integration
MCP for Marketo: the straight answer, and what works without one.
Adobe hosts its own MCP for Marketo Engage, though published accounts of its availability disagree. Orbit ships no Marketo tools and takes no credential. What it does instead, the instance audit, the segment reasoning, the email build, runs on an export you already know how to produce.
A Marketo instance that's been running for a few years is a museum of good intentions. Programs named three different ways by three different people who've since left. Channels applied inconsistently, so the reporting rolls up wrong. Tokens defined once and then ignored, with the same values hardcoded across a dozen emails. You know it needs a clean-up, and you know roughly where the bodies are, but pulling the whole picture together by clicking through the tree, program by program, is a week you don't have. Ask Claude for help and you get a sensible checklist for auditing Marketo. A generic one. It has never seen your instance. If you searched "MCP for Marketo" hoping to fix that, this page owes you the honest version of what the search finds, including the part where the live connection isn't ours, and the part where you don't need one to get the audit done this week.
What "MCP" actually means here.
MCP stands for Model Context Protocol, an open standard from Anthropic that lets Claude reach outside the chat window: a plugin system where the plugins give Claude real capabilities. Two facts before any pitch, and the first comes with an asterisk. Adobe hosts its own MCP for Marketo Engage. It exists; what we can't tell you is whether you can use it, because Adobe's own documentation reads as generally available while at least one widely circulated third-party guide calls it a limited beta. We're not going to resolve that in our favour and call it shipped, so ask your Adobe account team. Second fact, no asterisk: Orbit ships no Marketo tools. Nothing in Orbit takes a client id, a secret, or a REST endpoint. What Orbit is, is the lifecycle layer that runs on an export, the audit, the segment reasoning, the email build, with no credential in the loop. The full walk-through of what an MCP is and how it changes the work lives on the MCP for marketing page →.
What works beside Marketo today.
No hand-waving. Each row names who provides it and how your data gets there: the live-read row is Adobe's to fill and we mark it exactly as uncertain as it is, the audit and email rows are Orbit's and run locally on an export, and the row that doesn't exist says so. We'd rather name a gap than paper over it with a capability nobody can use.
Read your instance live through Adobe's own MCP
Partial: named limitAdobe hosts an MCP for Marketo Engage. It exists, but its availability is contested in public, with Adobe's documentation and third-party write-ups describing different things, so we won't tell you it's ready. Ask your Adobe account team what your subscription has access to. Whatever they say, this row is Adobe's to fill, not ours.
Audit program naming, channels, and tags
Works todayOrbit's side, from an export, no key needed. Export the program list with its channels and tags and Claude reads all of it at once: the three conventions fighting each other, the test programs never archived, the launch that never got its date prefix, the channel that skews a quarterly roll-up. A naming standard is only worth having if you can see where it's broken.
Review token and personalisation hygiene
Works todayHand over your my.token definitions and the emails that should be using them, and Orbit finds the drift: the value hardcoded in nine places, the token defined once at folder level and ignored ever after, the personalisation that silently falls back to nothing for half the database.
Turn smart-list logic into a lifecycle cut
Works todayExport the smart list definitions and Orbit's lifecycle skills do the translation: what the audience actually resolves to, where two lists overlap enough to double-message someone, and what the segment should be if you were designing it today rather than inheriting it.
Build and QA the email Marketo will send
Works todayOrbit's local pipeline: MJML compiled to clean, dark-mode-safe HTML, a render gate that catches clipping and inbox breakage before anything ships, subject-line and preheader scoring. Runs on your machine with no credential from anyone, and the output pastes into Marketo's editor.
Analyse lead and activity data
Partial: named limitBy export, and the shape of that export is Marketo's doing. There's no one-call email-stats endpoint; delivered, opened, and clicked live as activity records, so performance comes out of the Bulk Activity Extract, asynchronous and metered against a 500MB daily ceiling. You run the job, Claude reasons over the file. Genuine analysis; the transport is a file.
Call Marketo's REST API from Orbit's own tools
Not available todayNot shipped, and not a credential Orbit takes. Every tool an MCP carries costs context in every conversation, and a Marketo set hasn't earned its seat under that size budget yet. Worth saying separately: even if it ships, triggering a smart campaign against a live B2B database is not a thing we'd put in an unattended loop. If the tools land, this page changes then.
The short version: the audit and the email work exist today, from Orbit, locally, on an export. The live connection is Adobe's question to answer, not ours. And the thing most Marketo teams actually need help with, deciding what's wrong with four hundred programs, turns out not to require a live connection at all.
What the audit is actually for.
An export is a worse transport than an API and a much better one than nothing. Three audits pay for themselves the first time you run them on a mature instance, and each starts with a file you can produce in an afternoon:
- Program naming hygiene. Export the program list and Claude reads every name at once, which is the thing a human can't do, and the reason the drift survives. The three conventions fighting each other, the test programs nobody archived, the launch that never got its date prefix.
- Channel and tag consistency. Every program carries a channel and its tags, and your reporting rolls up through them. Claude checks the channel against what the program actually does and flags the mismatches that skew a quarterly report before anyone notices they've been reading the wrong number all year.
- Database and token health. Field completeness, duplicate patterns, smart lists whose logic no longer matches their name, tokens that should exist and don't. Read against your real export, not a checklist of things that might be wrong in some other instance.
None of this is Claude guessing. Every finding points at a named program, token, or list you can open in Marketo and check, which is the standard any audit should be held to, connected or not.
How to set it up.
One step, and it doesn't involve Marketo.
- Install Orbit. It's free, and there is no Marketo credential step, because no Orbit tool would use one. The audit protocols, the segment reasoning, the email pipeline, and the QA gate all run immediately. Then export whatever you want reviewed and hand it to Claude.
- Separately, ask Adobe about theirs. If a live read matters to you, put the question to your Adobe account team rather than to a comparison page, including ours. They can tell you what your subscription has today; we can only tell you the public record disagrees with itself.
If Orbit ships its own Marketo tools later, the connection step will appear here, and it will start read-only, because that's the posture everywhere else Orbit connects.
A word on the quota, whoever ends up spending it.
Marketo's API limits are lower than most SaaS platforms and they're shared across every integration touching your instance, your CRM sync included. The documented defaults: 50,000 API calls a day, 100 calls per 20 seconds, 10 concurrent calls, and a separate 500MB daily ceiling on Bulk Extract for lead and activity data.
That matters here for one reason. Any tool you connect that talks to the REST API is drawing on the same budget as the sync your sales team depends on, and an AI assistant asked an open-ended question is exactly the kind of client that can spend a lot of calls quickly. Worth asking before you connect anything, ours or anyone else's. The export path this page describes spends none of it: the extract is a job you already control, and the reasoning happens on your machine.
What's deepest on Braze, and why we say so.
Orbit's deepest single-platform integration is Braze, where the write path runs end to end. A handful of its tools are built around concepts that only exist in Braze, Canvas flows, Content Blocks, its media library, and those stay Braze-named on purpose. Faking a Marketo equivalent would just be a worse version of something Marketo models its own way.
For a Marketo team, the honest fit is the judgement rather than the plumbing: a practitioner's standard applied to your real programs, and an email pipeline that produces something worth putting in them. That's the work most enterprise B2B teams are short of, and none of it depends on which server holds the credential.
The half that isn't about the API at all.
A connection is one half, and on this page it's the missing half. The reason to bother anyway is what Claude does with the reading. Orbit ships 88 lifecycle skills, structured protocols for the actual jobs: auditing a program, laddering a nurture, scoring a subject line, sizing a test. Those are platform-agnostic; they work the same whether the instance underneath is Marketo or anything else.
Underneath sit 136 tools, an MJML pipeline that compiles to clean, dark-mode-safe HTML, a render-and-QA gate that catches the clipping and inbox breakage before you send, and the calculators a real analysis needs: sample size, holdout maths, LTV and payback. Marketo runs the enterprise sends. Orbit is the practitioner sitting next to the instance, reading what you hand over the way an experienced operator would on their first day auditing your account.
Is this for you?
This is for the B2B marketing-ops person who owns a Marketo instance and wants a second set of eyes that has actually read it, the person who knows the naming has drifted, suspects the channels are wrong, and can't face clicking through four hundred programs to prove it. Export the list, hand it over, and Orbit points at the problems by name. It's a weaker fit if what you wanted was an Orbit tool that logs into your instance and reads it live; that doesn't exist, and we won't pretend otherwise. What you get instead is the audit itself, this week, plus a straight answer about what is and isn't connected, rarer than it should be.
Try it.
Every Orbit plan includes every skill and tool, on every ESP. Install it, export your program list, and you have a named list of what's wrong with your instance the same afternoon, no credential handed over, nothing to revoke later.
Frequently asked.
What is an MCP for Marketo?
An MCP, Model Context Protocol, an open standard from Anthropic, gives Claude real tools instead of general knowledge. For Marketo there are two honest answers, and one of them comes with an asterisk. Adobe hosts its own MCP for Marketo Engage; it exists, but published accounts of its availability disagree, so whether your instance can use it today is a question for your Adobe account team rather than for us. Orbit ships no Marketo tools at all; nothing in Orbit takes a client id, a secret, or a REST endpoint. What Orbit is, is the lifecycle layer that runs on an export: the program, channel, and token audit, smart-list logic turned into lifecycle cuts, and a local email pipeline, none of it needing a credential from anyone. Orbit is not an official Adobe product; it is an independent MCP, and the only Marketo data it sees is what you hand it.
Is there an official Marketo MCP?
Adobe hosts one, and that is as far as we will go. It exists, but its status is genuinely contested in public: Adobe's own Experience League documentation reads as generally available, while at least one widely circulated third-party guide describes a limited beta. We have no way to settle that from the outside, so we are not going to pick the flattering reading and call it shipped. If you want Claude reading your instance live, ask your Adobe account team what your subscription actually has access to, and take the answer from them rather than from a landing page.
Does Orbit connect to Marketo directly?
No. Orbit ships no Marketo tools and takes no Marketo credential: no LaunchPoint client id, no secret, no REST endpoint. An earlier version of this page described that connection in some detail, down to the token refresh, and it was wrong; correcting it matters more than looking consistent. The reason for the gap is a size budget: every tool an MCP carries costs context in every conversation, and a Marketo set has not yet earned its seat against the tools people use daily. If those tools ship later, this page changes then.
What can Orbit do for a Marketo team without a connection?
The audit and the email, which, on a mature instance, is most of the work. Export your program list, your channel and tag assignments, your token definitions, or a smart list you want a second opinion on, and Claude runs the review a marketing-ops lead would: the three naming conventions fighting each other, the test programs nobody archived, the channel that quietly skews a quarterly roll-up, the value hardcoded across a dozen emails that should have been a token. Then there is the send itself: a local email pipeline that compiles MJML to dark-mode-safe HTML, a render gate that catches clipping and inbox breakage, subject-line scoring, and deliverability strategy for the domain you send from. All of it runs on your machine.
Can Orbit read Marketo email performance?
From an export you run, not from a connection. This one is worth knowing regardless of tooling: Marketo has no simple email-stats REST endpoint the way it has one for reading a program. Delivered, opened, clicked, and unsubscribed live as activity records, so real performance numbers come out of the Bulk Activity Extract, an asynchronous, quota-metered job. You run that extract and hand Claude the file. The analysis on the real numbers is genuine: send-over-send trends, the emails carrying a program, the ones quietly dragging it. The transport is a file instead of a credential, and we would rather name that than imply a connection that does not exist.