Marketo

io.github.ZLeventerPublished by GitHub account ZLeventerv1.0.1Updated Oct 24, 2026

MCP server for Marketo — 32 tools for leads, programs, emails, forms, lists, and bulk export.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work with Marketo marketing data through 32 tools covering leads, programs, emails, forms, lists, and bulk export.

What you can do
This local MCP server exposes Marketo's REST API to an assistant through 32 tools. The tool set spans leads, programs, emails, forms, lists, and bulk export, so an assistant can query and act on marketing automation records rather than only read them. It runs as a local process over stdio and is intended for desktop use.
When to use it
Worth adding when an assistant needs to work directly with a Marketo instance — for example looking up or managing leads, inspecting programs, emails, forms, or lists, or running bulk exports. It suits marketing operations and demand-generation workflows rather than general browsing.
Requirements
Runs locally over stdio, installed from the npm package marketo-mcp-server, so Node.js is needed. Requires a Marketo REST endpoint base URL (MARKETO_BASE_URL, found under Admin, Integration, Web Services) plus a LaunchPoint REST API client ID (MARKETO_CLIENT_ID) and client secret (MARKETO_CLIENT_SECRET). Network access to the Marketo instance is required.
Before you install
The server needs Marketo API credentials: MARKETO_CLIENT_ID and MARKETO_CLIENT_SECRET, which are secrets and should be supplied through environment variables rather than committed to files. The tools cover leads, programs, emails, forms, lists, and bulk export, so some operations may create, modify, or export marketing data; confirm what each tool does before granting broad use. Bulk export can move large volumes of lead data out of Marketo.

Installation

In SourceWeft

  1. Open Marketo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.