marketo-mcp-server
marketo-mcp-server
A Model Context Protocol server for Marketo — give Claude and other AI assistants direct access to your Marketo instance.
Query leads, inspect programs, review emails and forms, manage static and smart lists, explore channels and landing pages, and kick off bulk exports — all through natural language.
Features
Category | What you can do |
Leads | Get by ID or email, create/update in batch, delete, retrieve activity log |
Programs | List, get by ID, clone, get members |
Emails | List, get by ID, clone, send sample/test |
Forms | List, get by ID, clone, approve |
Smart Lists | List, get by ID with full filter definitions |
Static Lists | Get members, add leads, remove leads |
Channels | List, get by ID, create with progression statuses |
Landing Pages | List, get by ID, clone |
Bulk Export | Create job, enqueue, poll status, download file |
Prerequisites
Node.js 20+
A Marketo instance with REST API access
A Marketo API-only user and LaunchPoint service with Client ID and Client Secret
Setup
1. Get your Marketo REST credentials
In Marketo Admin: Integration → LaunchPoint → create or select a service → copy Client ID and Secret. Your base URL is under Integration → Web Services (e.g. https://xxx-xxx-xxx.mktorest.com).
2. Set environment variables
MARKETO_CLIENT_ID=your_client_id
MARKETO_CLIENT_SECRET=your_client_secret
MARKETO_BASE_URL=https://xxx-xxx-xxx.mktorest.comUsage
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"marketo": {
"command": "npx",
"args": ["marketo-mcp-server"],
"env": {
"MARKETO_CLIENT_ID": "your_client_id",
"MARKETO_CLIENT_SECRET": "your_client_secret",
"MARKETO_BASE_URL": "https://xxx-xxx-xxx.mktorest.com"
}
}
}
}Claude Code
claude mcp add marketo-mcp-server npx marketo-mcp-server \
-e MARKETO_CLIENT_ID=your_client_id \
-e MARKETO_CLIENT_SECRET=your_client_secret \
-e MARKETO_BASE_URL=https://xxx-xxx-xxx.mktorest.comCursor
Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally):
{
"mcpServers": {
"marketo": {
"command": "npx",
"args": ["marketo-mcp-server"],
"env": {
"MARKETO_CLIENT_ID": "your_client_id",
"MARKETO_CLIENT_SECRET": "your_client_secret",
"MARKETO_BASE_URL": "https://xxx-xxx-xxx.mktorest.com"
}
}
}
}Docker
docker build -t marketo-mcp-server .
docker run -e MARKETO_CLIENT_ID=... -e MARKETO_CLIENT_SECRET=... -e MARKETO_BASE_URL=... marketo-mcp-serverTools reference
Leads (5 tools)
Tool | Description |
| Get a single lead by Marketo lead ID |
| Look up a lead by email address |
| Batch upsert up to 300 leads |
| Permanently delete a lead by ID |
| Get activity log for a lead (filterable by activity type) |
Programs (4 tools)
Tool | Description |
| List programs with pagination and type/date filtering |
| Get full program metadata by ID |
| Clone a program with all local assets into a target folder |
| Get leads enrolled in a program |
Emails (4 tools)
Tool | Description |
| List email assets with status filtering |
| Get full email metadata including HTML and module structure |
| Clone an email asset to a target folder |
| Send a test/sample email, optionally rendered with a lead's tokens |
Forms (4 tools)
Tool | Description |
| List forms with pagination and status filtering |
| Get form metadata including fields and visibility rules |
| Clone a form to a target folder |
| Approve a form draft to make it live |
Smart Lists (2 tools)
Tool | Description |
| List smart lists with pagination |
| Get a smart list with its full filter definitions |
Static Lists (3 tools)
Tool | Description |
| Get leads that are members of a static list |
| Add up to 300 leads to a static list |
| Remove up to 300 leads from a static list |
Channels (3 tools)
Tool | Description |
| List all channels and their progression statuses |
| Get a single channel by ID |
| Create a channel with custom progression statuses |
Landing Pages (3 tools)
Tool | Description |
| List landing pages with status filtering |
| Get full LP metadata including template and form embeds |
| Clone a landing page to a target folder |
Bulk Export (4 tools)
Tool | Description |
| Create a bulk lead export job with field list and date filter |
| Enqueue a created export job for processing |
| Poll the status of a running export job |
| Download the file from a completed export job |
Example prompts
"Show me all leads created this week from the Webinar source"
"What programs are currently active and what channel is each one under?"
"Find all forms on the Contact Us landing page and show me their fields"
"Clone the Q1 Webinar program into the Q2 folder and name it Q2 Webinar"
"Export all leads updated in the last 30 days to CSV — email, firstName, lastName, company"
"Send a sample of email ID 1234 to test@example.com rendered with lead 5678's data"
Authentication
Marketo uses OAuth 2.0 client credentials. The server obtains and caches a token automatically, refreshing it 60 seconds before expiry. No manual token management required.
License
MIT — see LICENSE.
Available Tools
32 toolsmarketo_add_leads_to_listA
Add one or more leads to a static list by lead IDs. Max 300 leads per call.
Inputs: listId (required), leadIds (required).
marketo_approve_formA
Approve a Marketo form draft, making it the live version. The form must be in draft status.
Inputs: id (required).
marketo_clone_emailB
Clone an existing Marketo email asset. Creates a draft copy with the specified name in the target folder.
Inputs: id (required), name (required), folderId (required), folderType, +1 more.
marketo_clone_formA
Clone an existing Marketo form. Creates a new form with the same fields and settings under the specified name and folder.
Inputs: id (required), name (required), folderId (required), folderType, +1 more.
marketo_clone_landing_pageA
Clone an existing Marketo landing page. Creates a draft copy with the specified name in the target folder.
Inputs: id (required), name (required), folderId (required), folderType, +1 more.
marketo_clone_programA
Clone an existing Marketo program. Creates a copy with all local assets (emails, LPs, smart campaigns) under the specified name and folder.
Inputs: id (required), name (required), folderId (required), folderType, +1 more.
marketo_create_bulk_export_leadsA
Create a bulk lead export job. Specify which fields to export and a date range filter. The job must be enqueued separately after creation. Max 500MB or 10M records per export.
Inputs: fields (required), filter (required), format.
marketo_create_channelB
Create a new channel in Marketo. Channels define program types and their progression statuses (e.g. Invited > Registered > Attended for a Webinar channel).
Inputs: name (required), applicableProgramType (required), progressionStatuses (required).
marketo_create_or_update_leadsA
Batch create or update leads in Marketo. Upserts up to 300 leads per call. Uses 'email' as the default dedup field. Set action to createOnly, updateOnly, or createOrUpdate.
Inputs: input (required), action, lookupField.
marketo_delete_leadA
Delete a lead from Marketo by lead ID. This is permanent and cannot be undone.
Inputs: id (required).
marketo_enqueue_bulk_exportA
Enqueue a previously created bulk export job for processing. The job moves from Created to Queued status. Poll status with marketo_get_bulk_export_status.
Inputs: exportId (required).
marketo_get_bulk_export_fileA
Download the file from a completed bulk export job. Returns CSV/TSV content. Only works when job status is Completed. Large files may be clipped in MCP response.
Inputs: exportId (required).
marketo_get_bulk_export_statusA
Check the status of a bulk export job. Returns status (Created/Queued/Processing/Completed/Failed/Cancelled), file size, number of rows, and timestamps.
Inputs: exportId (required).
marketo_get_channel_by_idA
Get a single Marketo channel by ID. Returns channel metadata including progression statuses and their step numbers.
Inputs: id (required).
marketo_get_channelsA
List all channels in Marketo. Channels define the program type taxonomy (e.g. Webinar, Tradeshow, Email Send). Returns channel names, progression statuses, and applicability.
Inputs: maxReturn, offset.
marketo_get_email_by_idA
Get a single Marketo email asset by ID. Returns full email metadata including HTML content, subject line, from/reply-to, and module structure.
Inputs: id (required).
marketo_get_emailsA
List email assets in Marketo. Supports pagination via maxReturn/offset and filtering by status (approved/draft). Returns email metadata including subject line, from address, and folder.
Inputs: maxReturn, offset, status.
marketo_get_form_by_idA
Get a single Marketo form by its ID. Returns full form metadata including fields, submit button label, and visibility rules.
Inputs: id (required).
marketo_get_formsA
List forms in Marketo. Supports pagination via maxReturn (max 200) and offset. Optionally filter by status (approved/draft). Returns form metadata including name, URL, status, and folder.
Inputs: maxReturn, offset, status.
marketo_get_landing_page_by_idA
Get a single Marketo landing page by ID. Returns full LP metadata including template, URL, content sections, and form embeds.
Inputs: id (required).
marketo_get_landing_pagesA
List landing pages in Marketo. Supports pagination via maxReturn/offset and filtering by status (approved/draft). Returns LP metadata including URL, template, and mobile enablement status.
Inputs: maxReturn, offset, status.
marketo_get_lead_activitiesA
Get activity log for a specific lead. Filter by activity type IDs (e.g. 1=Visit Web Page, 6=Send Email). Supports pagination via nextPageToken. Returns timestamped activity records.
Inputs: leadId (required), activityTypeIds, nextPageToken, batchSize.
marketo_get_lead_by_emailA
Look up a lead by email address. Uses filterType=email on the leads endpoint. Returns matching lead records.
Inputs: email (required), fields.
marketo_get_lead_by_idA
Get a single lead by Marketo lead ID. Optionally specify which fields to return. Returns lead record with all requested fields.
Inputs: id (required), fields.
marketo_get_lead_listsB
Get leads that are members of a specific static list. Supports pagination via nextPageToken and batchSize.
Inputs: listId (required), fields, batchSize, nextPageToken.
marketo_get_program_by_idA
Get a single Marketo program by ID. Returns full program metadata including channel, status, costs, tags, and folder location.
Inputs: id (required).
marketo_get_program_membersA
Get members (leads) of a Marketo program. Supports pagination via nextPageToken and batchSize. Optionally specify which lead fields to return.
Inputs: programId (required), fields, batchSize, nextPageToken.
marketo_get_programsA
List programs in Marketo. Supports pagination (maxReturn/offset), filtering by type (filterType: id/programType/folder/tag), and date range filtering. Returns program metadata including status, channel, costs, and tags.
Inputs: maxReturn, offset, filterType, filterValues, +2 more.
marketo_get_smart_list_by_idA
Get a single Marketo smart list by ID. Returns full smart list metadata including filter definitions and rule logic.
Inputs: id (required).
marketo_get_smart_listsA
List smart lists in Marketo. Returns smart list metadata including name, folder, created/updated dates, and filter rules summary.
Inputs: maxReturn, offset.
marketo_remove_leads_from_listA
Remove one or more leads from a static list by lead IDs. Max 300 leads per call.
Inputs: listId (required), leadIds (required).
marketo_send_sampleA
Send a sample/test email to an email address. Optionally render personalization tokens using a specific lead's data. Useful for QA before approving.
Inputs: id (required), emailAddress (required), textOnly, leadId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Each tool has a clear, distinct purpose targeting a specific Marketo resource and action. There is no ambiguity between tools like marketo_get_email_by_id and marketo_get_emails, or between create, clone, add, remove, and delete operations.
All tools follow a consistent verb_noun pattern prefixed with 'marketo_'. Verbs are lowercase and nouns are descriptive. For example, marketo_get_lead_by_id, marketo_create_or_update_leads, marketo_add_leads_to_list. No mixing of conventions.
With 32 tools, the server covers a broad domain (leads, lists, emails, forms, landing pages, programs, channels, smart lists, bulk exports). While slightly above the typical 3-15 range, the complexity of Marketo justifies the count, and each tool serves a specific function.
The server covers core CRUD for leads and lists, asset management for emails, forms, and landing pages, and program/channel operations. However, notable gaps exist: no direct update for assets (only clone and approve), no program creation/deletion, and no list management beyond add/remove. Bulk export is well-covered.
Maintenance
Related MCP Connectors
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.
Unofficial remote MCP server for Less Annoying CRM: OAuth 2.1, read-only grants, 10 tools.
MCP server for customer-io
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.