Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Marketo to Claude Code

Make Claude build programs and manage leads in Marketo. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Marketo to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Marketo, you add a Marketo MCP server: a small hosted service that exposes Marketo's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Marketo account. No API keys pasted into config files.

claude mcp add --transport http marketo https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Marketo once connected?

Full read-write Marketo access lets Claude create and update lead records, add or remove members from static lists, build and edit email programs, and request a smart campaign run once you approve. The campaign setup and lead hygiene that used to mean clicking through the UI happen where the data already lives.

  • Create or update lead records and their field values from a brief
  • Add or remove leads from a static list to stage a segment
  • Build or edit an email program and its assets
  • Clone and rename a smart campaign before a launch
  • Activate a smart campaign and request a run after you approve it
  • Pull program performance and propose follow-up nurture steps

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Marketo access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Marketo API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Marketo changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Marketo connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Marketo connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Marketo account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Marketo's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Marketo?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Marketo account it signs in with. Revoking access is one click in Marketo.

More on the Marketo connector

Marketo connector for claude.aiMailchimp + Claude CodeKlaviyo + Claude CodeActiveCampaign + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us