Claude + Marketo: What the Integration Can (and Can't) Do in 2026
Yes — Adobe ships an official Marketo Engage MCP server, but read the fine print before you count on it. It’s a real, hosted remote MCP server exposing 100+ Marketo operations. The catches are big: it’s in limited beta (request access via a form, not open GA), and its authentication passes your credentials in HTTP headers rather than OAuth. That header-based auth means it works in Claude Desktop and Claude Code — but not the claude.ai web app, which requires OAuth for custom connectors. And like every Claude integration, it only works inside a conversation you start: no triggers, nothing watching Marketo, nothing running while you’re away.
Here’s exactly what the official MCP does, the self-serve BYO-key alternative, where the limits bite, and what to use if you want Marketo work that runs on its own.
What Adobe’s official Marketo MCP does
Adobe is pushing MCP as its default agent protocol across products, and Marketo Engage now has its own server:
- Endpoint:
https://marketo-mcp.adobe.io/mcp— hosted, no local install. - Coverage: 100+ operations across forms, programs, smart campaigns, leads, emails, lists, and folders.
- Auth: credentials passed in HTTP headers each request — either
X-Marketo-Client-Id/X-Marketo-Client-Secret/X-Marketo-Munchkin-Id, or an IMS bearer token withx-gw-ims-org-id. This is not OAuth, which is why it can’t be a claude.ai web custom connector; it runs in Claude Desktop, Claude Code, and similar clients (Cursor, VS Code Copilot). - Status: Limited Availability (beta). You request access via a form — it is not open GA, and it is not a one-click entry in Anthropic’s connectors directory.
There’s also a community option: alexleventer/marketo-mcp, a local server that wraps Marketo’s REST API using your Client ID, Secret, and Munchkin ID. It predates Adobe’s official server and uses the same credential-header style.
The self-serve route: BYO-key against Marketo’s REST API
If you don’t want to wait on the beta, Marketo’s REST API is self-serve for anyone with admin access to the instance — no Adobe partner approval needed:
- In Marketo, go to Admin → Users & Roles and create an API-Only user plus a role.
- Go to Admin → Integrations → LaunchPoint → New Service → Custom to generate a Client ID and Secret.
- Your Munchkin ID scopes the instance. Exchange the Client ID/Secret for a bearer token from Marketo’s Identity endpoint (tokens live 3,600 seconds).
Two things to flag: it requires admin rights to set up (and Marketo is enterprise-priced), and the older access_token query-parameter auth is being removed after July 31, 2026 — new integrations must send the token in the Authorization header. Build header-auth from the start.
The limits that actually matter
Whichever route you take, the MCP shape is “an assistant you operate,” not “an agent that runs.” The limits:
- No triggers, no monitoring. The MCP tools only run inside a conversation you start. There’s no “when a lead hits a score threshold, add them to a nurture program” or “when a form is submitted, sync to the CRM.” Nothing fires on a Marketo event — you have to be there, prompting.
- Conversation-only. Claude reads and updates when you ask; it doesn’t sit watching lead activity and acting on it. Close the chat and nothing continues.
- Beta and Desktop-bound. The official server is beta, request-access, and — because of header auth — not usable on claude.ai web. The nearest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on marketing-ops agent.
So Claude is great for “pull the leads in this smart list and draft an email” and not built for “run our lead lifecycle as things happen.”
If you want Marketo work that runs on its own: Carly
The moment you want something to happen around Marketo without you in the chat — sync a new lead to the CRM the instant a form is submitted, kick off a nurture when a score crosses a threshold, roll up campaign numbers into a Monday email — you’ve crossed past what Claude’s MCP is for, beta or not.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud — when a lead is created or scored, Carly acts; your laptop doesn’t need to be awake.
- Connects Marketo to the rest of your stack — route a new lead into your CRM, create follow-up tasks, and drop campaign metrics into a Sheet as one workflow.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, updates your CRM, and records meetings.
- Builds the workflow for you — tell it “I’d like a system that syncs every new Marketo lead to our CRM and alerts sales” in plain English; it interviews you, then builds it with you. No prompt engineering.
Carly reaches Marketo through your own API key — set up an API-Only user and a LaunchPoint custom service, then paste the credentials on carlyassistant.com/integrations. We take the key and can do whatever Marketo’s REST API allows. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations.
Claude vs Carly
| Claude (Marketo MCP) | Carly | |
|---|---|---|
| Read leads, lists, campaigns | Yes (beta) | Yes |
| Update Marketo records | Yes (beta) | Yes |
| Works on claude.ai web | No (Desktop/Code only) | N/A (cloud service) |
| Acts on triggers / events | No | Yes |
| Runs a lead lifecycle on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Adobe’s MCP is a Marketo cockpit inside a desktop chat — powerful, but beta and hands-on. Carly is a teammate that runs the lifecycle on its own.
Frequently Asked Questions
Does Claude work with Marketo?
Yes, with caveats. Adobe ships an official Marketo Engage MCP server exposing 100+ operations, but it’s in limited beta (request access via a form), and its header-based auth means it works in Claude Desktop and Claude Code, not the claude.ai web app. You can also connect via BYO-key against Marketo’s self-serve REST API. Either way, it only works inside a conversation you start.
Why won’t the Marketo MCP work in Claude’s web app?
Because it authenticates with credentials in HTTP headers, not OAuth. Custom connectors on claude.ai web require OAuth, so Adobe’s Marketo MCP is limited to desktop clients like Claude Desktop, Claude Code, Cursor, and VS Code Copilot.
How do I connect Claude to Marketo without the beta?
Set up a self-serve REST integration: in Marketo, create an API-Only user (Admin → Users & Roles), then a LaunchPoint custom service (Admin → Integrations → LaunchPoint) to get a Client ID and Secret. This requires admin access. Note that query-parameter token auth is being removed after July 31, 2026 — use the Authorization header.
Can Claude run our lead lifecycle automatically?
No. The MCP tools respond inside a chat and don’t act on Marketo events. For automatic, trigger-based lifecycle work — syncing leads, kicking off nurtures, alerting sales — use an agent platform like Carly, which fires on events 24/7 in the cloud. AI agents start at $35/month.
More: Claude connectors · Claude + HubSpot · Claude + ActiveCampaign · Can Claude send emails · Claude vs Carly · Best AI CRM tools
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
