Marketo Engage MCP server
Marketo Engage in any MCP client, through Memtro: Marketo Engage does not publish this server. Memtro's Marketo Engage connector reads Marketo Engage through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read-only B2B marketing automation: leads with fields and activity history, programs with members and costs, email assets with send/open/click performance, and smart campaigns.
Reads
marketo_leadsLook up Marketo leads by email address(es) or lead id(s) — exact matches only, up to 50 at once — returning name, company, title, status, score…marketo_lead_activitiesActivity history for one lead since a date (default 30 days): web visits, form fills, link clicks, emails sent/delivered/opened/clicked…marketo_programsPrograms (events, email sends, nurtures, webinars…) with type, channel, status, workspace, costs and tags, most recently updated first…marketo_emailsEmail assets with subject, sender, approval status and folder, most recently updated first; or one email by id…marketo_smart_campaignsSmart campaigns (batch and trigger) with status, active flag, parent program and folder, most recently updated first; or one by id.
Connect it
First connect Marketo Engage on Dashboard → Connections, then add Memtro to your client once. The Marketo Engage tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
One command registers the server; the tools are then available in every session.
claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
--header "Authorization: Bearer sk-memtro-..."Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Marketo Engage connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What has jordan@contoso.com done in Marketo in the last 30 days?
- › Which programs were created this quarter and what did they cost?
- › How did the Q3 webinar invite email perform?
- › Which trigger campaigns are active right now?
Questions
- Is this an official Marketo Engage MCP server?
- No. It is Memtro's MCP server with Memtro's Marketo Engage connector behind it: the connector reads Marketo Engage through its API with the credentials you connect on Dashboard → Connections, and Marketo Engage publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Marketo Engage?
- Not yet. Today every Marketo Engage tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.