Connect Adobe Marketo Engage to Claude Code
Give Claude Code governed access to Adobe Marketo Engage’s 118 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Adobe Marketo Engage to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.
- 1
Add Adobe Marketo Engage to Runlayer
Adobe Marketo Engage isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Adobe Marketo Engage’s 118 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code setup guide - 3
Sign in to Adobe Marketo Engage
Sign in the way Adobe Marketo Engage requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Adobe Marketo Engage from Claude Code
Adobe Marketo Engage’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
118 Adobe Marketo Engage tools in Claude Code
Runlayer policy decides which of these Claude Code users can call.
Activate smart campaign
Activate a smart campaign to start processing leads.
Add field set
Add a field set (field group) to a form.
Add field to form
Add a new field to a form.
Add field visibility rule
Add visibility rules to a form field.
Add flow step
Add a flow step to a smart campaign at the specified index.
Add flow step choice
Add a conditional choice branch to an existing flow step, so the step can do different things for different leads ("if the lead is in California send email A, otherwise send email B").
Add leads to list
Add existing leads to a static list (list membership).
Add rich text field
Add a rich text element to a form.
Control
What Runlayer can see and stop in Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every Adobe Marketo Engage call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more