NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
MCP server · Marketing automation

Account Engagement (Pardot) MCP server

Account Engagement (Pardot) in any MCP client, through Memtro: Account Engagement (Pardot) does not publish this server. Memtro's Account Engagement (Pardot) connector reads Account Engagement (Pardot) 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 Salesforce Marketing Cloud Account Engagement: prospects with score, grade and activity history, campaigns, lists, forms and form handlers, and list emails with send/open/click statistics.

Reads

  • pardot_prospectsAccount Engagement prospects: one by id or exact email, or a list filtered by update/creation/last-activity date or assigned user, with name…
  • pardot_prospect_activitiesVisitor activities for one prospect, newest first: email sends/opens/clicks, form submissions, page visits, file downloads, unsubscribes, bounces…
  • pardot_campaignsAccount Engagement campaigns with cost, parent campaign and linked Salesforce campaign id, most recently updated first…
  • pardot_listsMarketing lists (static and dynamic) with visibility flags and campaign, most recently updated first.
  • pardot_formsForms or form handlers with their campaign and folder, most recently updated first.
  • pardot_list_emailsList emails (marketing sends) most recently sent first, by default with statistics for the first 10: sent, delivered, opens, unique opens, clicks…

Connect it

First connect Account Engagement (Pardot) on Dashboard → Connections, then add Memtro to your client once. The Account Engagement (Pardot) 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 Account Engagement (Pardot) 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 is the score and grade of maria@globex.com and what did she do last?
  • › Which list emails went out this month and what were their open rates?
  • › How many submissions did the Contact Us form get in the last 30 days?
  • › Which prospects were updated today?

Questions

Is this an official Account Engagement (Pardot) MCP server?
No. It is Memtro's MCP server with Memtro's Account Engagement (Pardot) connector behind it: the connector reads Account Engagement (Pardot) through its API with the credentials you connect on Dashboard → Connections, and Account Engagement (Pardot) 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 Account Engagement (Pardot)?
Not yet. Today every Account Engagement (Pardot) 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.

Other MCP servers · Marketing automation