Marketo MCP Server

A Model Context Protocol server for Adobe Marketo Engage. Give Claude Desktop, Cursor, and other MCP-compatible clients direct, authenticated access to the Marketo REST API — read and write forms, smart lists, channels, leads, activities, and lists with natural language.

Why

Marketing ops, growth, and RevOps teams spend hours clicking through the Marketo UI to clone a form, approve assets, look up a lead, or audit a smart list. The Marketo MCP Server wires those same REST API operations into an LLM agent, so you can say:

• "Clone form 1234 into the Q2 Webinars folder and approve it."

• "Show me recent activities for lead alex@example.com."

• "Create a new email channel called 'Lifecycle Nurture'."

…and the model executes the actual Marketo API calls on your behalf.

Related MCP server: Xero MCP Server

Table of Contents

• Features

• Quick start

• Prerequisites

• Configuration

• Available tools

• Usage with Claude Desktop

• Usage with Cursor / other MCP clients

• Troubleshooting

• Development

• Contributing

Features

• Form management — list, inspect, clone, and approve forms via the Marketo Asset API

• Smart list operations — list and inspect smart lists

• Channel CRUD — create, read, update, and delete channels

• Lead database — get leads by ID or email, create or update leads in bulk, delete leads

• Activity & change logs — fetch activities and field changes for any lead

• List membership — add or remove leads from static lists

• Automatic auth — OAuth 2.0 client-credentials flow with token caching & refresh

• Stdio transport — works out of the box with Claude Desktop, Cursor, and any MCP client that speaks stdio

Quick start

Option A — Smithery (recommended)

npx -y @smithery/cli install @alexleventer/marketo-mcp --client claude

Follow the prompts to paste in your Marketo base URL, client ID, and client secret.

Option B — npx (no install)

Add the following to your MCP client's config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "marketo": {
      "command": "npx",
      "args": ["-y", "marketo-mcp"],
      "env": {
        "MARKETO_BASE_URL": "https://123-ABC-456.mktorest.com/rest",
        "MARKETO_CLIENT_ID": "your-client-id",
        "MARKETO_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Option C — from source

git clone https://github.com/alexleventer/marketo-mcp.git
cd marketo-mcp
npm install
npm run build

Copy the config block printed by the build into your MCP client.

Prerequisites

• Node.js 18 or higher

• Marketo API credentials (client ID & client secret from a LaunchPoint service)

• A Marketo instance with REST API access enabled

• An MCP-compatible client — Claude Desktop, Cursor, Cline, or any other

Obtaining Marketo API credentials

1. Log into Marketo admin

2. Admin → Integration → LaunchPoint

3. New → New Service, set service type to Custom and pick a display name (e.g. MCP Server)

4. Assign an API-only user with the permissions you need (Read-Only Assets, Read-Write Lead, etc.)

5. Save the Client ID and Client Secret

6. Your base URL is under Admin → Integration → Web Services → REST API Endpoint (strip /rest/v1/* — keep just https://<munchkin>.mktorest.com/rest)

Configuration

All configuration is via environment variables:

Copy .env.example to .env for local development.

Available tools

Each tool accepts typed arguments validated with zod and returns the raw Marketo JSON response. See the Adobe Marketo REST API reference for field-level details.

Usage with Claude Desktop

1. Install Claude Desktop

2. Open the config at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

3. Paste the mcpServers block from Quick start

4. Restart Claude Desktop

Usage with Cursor / other MCP clients

Any MCP client that supports stdio servers will work. Point it at the built binary:

{
  "mcpServers": {
    "marketo": {
      "command": "npx",
      "args": ["-y", "marketo-mcp"],
      "env": { "MARKETO_BASE_URL": "...", "MARKETO_CLIENT_ID": "...", "MARKETO_CLIENT_SECRET": "..." }
    }
  }
}

Troubleshooting

You can inspect tool calls locally with the MCP inspector:

npm run inspector

Development

src/
├── index.ts       # MCP server + all tool registrations
├── auth.ts        # OAuth token manager (caches until expiry)
└── constants.ts   # Env var bindings

npm run dev          # Run with ts-node + .env
npm run typecheck    # Type-check without emit
npm run lint         # ESLint
npm run format       # Prettier
npm run build        # Compile to build/

Contributing

Issues and pull requests welcome at github.com/alexleventer/marketo-mcp.

1. Fork the repo

2. Create a feature branch

3. npm run lint && npm run typecheck

4. Open a PR

License

ISC — see LICENSE.

Keywords: marketo mcp server, marketo model context protocol, marketo claude, marketo ai, adobe marketo mcp, marketo api claude desktop, marketo automation llm, marketo engage mcp