Marketo
NPM · MARKETO-MCP-SERVER
MCP server for Marketo — 32 tools for leads, programs, emails, forms, lists, and bulk export.
Available components
Last scanned (19 hours ago)
Scores higher than 46% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 33 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 189 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2436 tokens (~76/item across 32 items; 32 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "marketo_delete_lead" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/marketo-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
marketo_add_leads_to_list ~62
Add one or more leads to a static list by lead IDs. Max 300 leads per call.
| Name | Type | Req | Description |
|---|---|---|---|
| leadIds | array | yes | Array of lead IDs to add (max 300) |
| listId | number | yes | Static list ID |
No output schema declared.
No examples provided.
marketo_approve_form ~44
Approve a Marketo form draft, making it the live version. The form must be in draft status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Form ID to approve |
No output schema declared.
No examples provided.
marketo_clone_email ~91
Clone an existing Marketo email asset. Creates a draft copy with the specified name in the target folder.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description for the cloned email |
| folderId | number | yes | Destination folder ID |
| folderType | string | – | Type of destination folder |
| id | number | yes | ID of the email to clone |
| name | string | yes | Name for the cloned email |
No output schema declared.
No examples provided.
marketo_clone_form ~94
Clone an existing Marketo form. Creates a new form with the same fields and settings under the specified name and folder.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description for the cloned form |
| folderId | number | yes | Destination folder ID |
| folderType | string | – | Type of destination folder |
| id | number | yes | ID of the form to clone |
| name | string | yes | Name for the cloned form |
No output schema declared.
No examples provided.
marketo_clone_landing_page ~96
Clone an existing Marketo landing page. Creates a draft copy with the specified name in the target folder.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description for the cloned landing page |
| folderId | number | yes | Destination folder ID |
| folderType | string | – | Type of destination folder |
| id | number | yes | ID of the landing page to clone |
| name | string | yes | Name for the cloned landing page |
No output schema declared.
No examples provided.
marketo_clone_program ~100
Clone an existing Marketo program. Creates a copy with all local assets (emails, LPs, smart campaigns) under the specified name and folder.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description for the cloned program |
| folderId | number | yes | Destination folder ID |
| folderType | string | – | Type of destination folder |
| id | number | yes | ID of the program to clone |
| name | string | yes | Name for the cloned program |
No output schema declared.
No examples provided.
marketo_create_bulk_export_leads ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | Lead field API names to export |
| filter | object | yes | Date range filter - use createdAt or updatedAt (required) |
| format | string | – | Export file format |
No output schema declared.
No examples provided.
marketo_create_channel ~91
Create a new channel in Marketo. Channels define program types and their progression statuses (e.g. Invited > Registered > Attended for a Webinar channel).
| Name | Type | Req | Description |
|---|---|---|---|
| applicableProgramType | string | yes | Program type this channel applies to (e.g. 'event', 'default', 'email') |
| name | string | yes | Channel name |
| progressionStatuses | array | yes | Ordered list of progression statuses |
No output schema declared.
No examples provided.
marketo_create_or_update_leads ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Sync action |
| input | array | yes | Array of lead objects (max 300). Each must include a dedup key like 'email'. |
| lookupField | string | – | Field used for deduplication |
No output schema declared.
No examples provided.
marketo_delete_lead ~40
Delete a lead from Marketo by lead ID. This is permanent and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Lead ID to delete |
No output schema declared.
No examples provided.
marketo_enqueue_bulk_export ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | Export job ID returned from create |
No output schema declared.
No examples provided.
marketo_get_bulk_export_file ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | Export job ID (must be in Completed status) |
No output schema declared.
No examples provided.
marketo_get_bulk_export_status ~57
Check the status of a bulk export job. Returns status (Created/Queued/Processing/Completed/Failed/Cancelled), file size, number of rows, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | Export job ID |
No output schema declared.
No examples provided.
marketo_get_channel_by_id ~41
Get a single Marketo channel by ID. Returns channel metadata including progression statuses and their step numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Channel ID |
No output schema declared.
No examples provided.
marketo_get_channels ~74
List all channels in Marketo. Channels define the program type taxonomy (e.g. Webinar, Tradeshow, Email Send). Returns channel names, progression statuses, and applicability.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReturn | number | – | Max channels to return (1-200, default 20) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
marketo_get_email_by_id ~52
Get a single Marketo email asset by ID. Returns full email metadata including HTML content, subject line, from/reply-to, and module structure.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Email asset ID |
No output schema declared.
No examples provided.
marketo_get_emails ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReturn | number | – | Max emails to return (1-200, default 20) |
| offset | number | – | Pagination offset |
| status | string | – | Filter by approval status |
No output schema declared.
No examples provided.
marketo_get_form_by_id ~46
Get a single Marketo form by its ID. Returns full form metadata including fields, submit button label, and visibility rules.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Form ID |
No output schema declared.
No examples provided.
marketo_get_forms ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReturn | number | – | Max forms to return (1-200, default 20) |
| offset | number | – | Pagination offset |
| status | string | – | Filter by approval status |
No output schema declared.
No examples provided.
marketo_get_landing_page_by_id ~50
Get a single Marketo landing page by ID. Returns full LP metadata including template, URL, content sections, and form embeds.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Landing page ID |
No output schema declared.
No examples provided.
marketo_get_landing_pages ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReturn | number | – | Max landing pages to return (1-200, default 20) |
| offset | number | – | Pagination offset |
| status | string | – | Filter by approval status |
No output schema declared.
No examples provided.
marketo_get_lead_activities ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activityTypeIds | array | – | Filter to specific activity type IDs |
| batchSize | number | – | Number of results per page (max 300) |
| leadId | number | yes | Lead ID to get activities for |
| nextPageToken | string | – | Pagination token from previous response |
No output schema declared.
No examples provided.
marketo_get_lead_by_email ~61
Look up a lead by email address. Uses filterType=email on the leads endpoint. Returns matching lead records.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to search for | |
| fields | array | – | List of field API names to return |
No output schema declared.
No examples provided.
marketo_get_lead_by_id ~75
Get a single lead by Marketo lead ID. Optionally specify which fields to return. Returns lead record with all requested fields.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | List of field API names to return (e.g. ['email','firstName','company']) |
| id | number | yes | Marketo lead ID |
No output schema declared.
No examples provided.
marketo_get_lead_lists ~88
Get leads that are members of a specific static list. Supports pagination via nextPageToken and batchSize.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | number | – | Number of results per page (max 300) |
| fields | array | – | Lead field API names to return |
| listId | number | yes | Static list ID |
| nextPageToken | string | – | Pagination token from previous response |
No output schema declared.
No examples provided.
marketo_get_program_by_id ~47
Get a single Marketo program by ID. Returns full program metadata including channel, status, costs, tags, and folder location.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Program ID |
No output schema declared.
No examples provided.
marketo_get_program_members ~96
Get members (leads) of a Marketo program. Supports pagination via nextPageToken and batchSize. Optionally specify which lead fields to return.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | number | – | Number of results per page (max 300) |
| fields | array | – | Lead field API names to return |
| nextPageToken | string | – | Pagination token from previous response |
| programId | number | yes | Program ID |
No output schema declared.
No examples provided.
marketo_get_programs ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| earliestUpdatedAt | string | – | ISO 8601 datetime — only programs updated after this |
| filterType | string | – | Filter type: id, programType, folder, or tag |
| filterValues | string | – | Comma-separated filter values |
| latestUpdatedAt | string | – | ISO 8601 datetime — only programs updated before this |
| maxReturn | number | – | Max programs to return (1-200, default 20) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
marketo_get_smart_list_by_id ~46
Get a single Marketo smart list by ID. Returns full smart list metadata including filter definitions and rule logic.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Smart list ID |
No output schema declared.
No examples provided.
marketo_get_smart_lists ~68
List smart lists in Marketo. Returns smart list metadata including name, folder, created/updated dates, and filter rules summary.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReturn | number | – | Max smart lists to return (1-200, default 20) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
marketo_remove_leads_from_list ~62
Remove one or more leads from a static list by lead IDs. Max 300 leads per call.
| Name | Type | Req | Description |
|---|---|---|---|
| leadIds | array | yes | Array of lead IDs to remove (max 300) |
| listId | number | yes | Static list ID |
No output schema declared.
No examples provided.
marketo_send_sample ~91
Send a sample/test email to an email address. Optionally render personalization tokens using a specific lead's data. Useful for QA before approving.
| Name | Type | Req | Description |
|---|---|---|---|
| emailAddress | string | yes | Recipient email address for the sample |
| id | number | yes | Email asset ID |
| leadId | number | – | Lead ID whose data to use for token rendering |
| textOnly | boolean | – | Send text-only version |
No output schema declared.
No examples provided.
How do I install the Marketo MCP server?
Marketo runs locally as an npm package, launched with npx -y marketo-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · marketo-mcp-server
claude mcp add zleventer-marketo-mcp-server -- npx -y marketo-mcp-server
What is the Marketo MCP server?
Marketo is an MCP server listed in the public MCP registry as io.github.ZLeventer/marketo-mcp-server. MCP server for Marketo, 32 tools for leads, programs, emails, forms, lists, and bulk export. This page covers its npm package (marketo-mcp-server).
Is the Marketo MCP server safe to use?
Marketo scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Marketo MCP server expose?
Marketo exposes 32 tools: marketo_get_forms, marketo_get_form_by_id, marketo_clone_form, marketo_approve_form, marketo_get_lead_by_id, and 27 more. Their descriptions and schemas cost roughly 2,436 tokens of context every time the server is loaded.
Is the Marketo MCP server still maintained?
Marketo is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Marketo MCP server under?
Marketo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.