Benchmark Email MCP server
Benchmark Email in any MCP client, through Memtro: Benchmark Email does not publish this server. Memtro's Benchmark Email connector reads Benchmark Email 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
Benchmark Email marketing: contact lists with their sizes, which lists an email address is on and whether it is unsubscribed, segments, email campaigns with their status, and campaign reports (sent, opens, clicks, bounces, unsubscribes); can add or update a contact on a list, unsubscribe them to Do Not Contact, remove them from a list, send a test of a campaign, copy, trash or restore a campaign, and delete a segment.
Reads
benchmarkemail_list_listsBenchmark Email contact lists: id, name, how many contacts, description, and when created and last changed.benchmarkemail_find_contactWhich Benchmark Email lists hold an email address, with the contact id on each list and whether the address is on the master unsubscribe…benchmarkemail_list_segmentsBenchmark Email segments: id, name, the list each is built on, contact count and description.benchmarkemail_list_emailsBenchmark Email campaigns (emails): id, name, subject, status (Incomplete, Scheduled, Sending, Sent…), sender name, target lists, schedule…benchmarkemail_email_reportsBenchmark Email campaign reports, newest first: for each sent campaign, how many were sent, opened, unopened, clicked, bounced, unsubscribed…benchmarkemail_email_reportOne Benchmark Email campaign's report by email id: sent, opens, unopened, clicks, bounces, unsubscribes, complaints, forwards, lists and dates.
Acts, when you ask
These change something in Benchmark Email. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
benchmarkemail_add_contactAdds a contact to a Benchmark Email list, so they receive campaigns sent to it.benchmarkemail_update_contactChanges a contact's email address or name on one Benchmark Email list.benchmarkemail_unsubscribe_contactMoves a Benchmark Email contact to Do Not Contact, the account's master unsubscribe list, so they stop receiving every campaign from every list.benchmarkemail_remove_contactRemoves a contact from one Benchmark Email list.benchmarkemail_send_test_emailSends a test of a Benchmark Email campaign to the addresses given (at most 5), with a short note on top.benchmarkemail_copy_emailCopies a Benchmark Email campaign as a new email with the given name, for editing and sending in Benchmark.benchmarkemail_trash_emailMoves a Benchmark Email campaign to the Trash.benchmarkemail_restore_emailRestores a Benchmark Email campaign from the Trash.benchmarkemail_delete_segmentDeletes a Benchmark Email segment.
Connect it
First connect Benchmark Email on Dashboard → Connections, then add Memtro to your client once. The Benchmark Email tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
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 Benchmark Email 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
- › How did last week's newsletter perform?
- › Which lists is maya@northwind.example on, and is she unsubscribed?
- › Which campaigns are scheduled to send this month?
- › How many contacts are on the customers list?
- › Send a test of the March newsletter to me.
Questions
- Is this an official Benchmark Email MCP server?
- No. It is Memtro's MCP server with Memtro's Benchmark Email connector behind it: the connector reads Benchmark Email through its API with the credentials you connect on Dashboard → Connections, and Benchmark Email 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 Benchmark Email?
- Only when you ask, and only what it has been granted: add a contact to a list; update a contact's email or name on a list; unsubscribe a contact (move to Do Not Contact); remove a contact from a list; send a test of a campaign to named addresses; copy a campaign as a new draft; move a campaign to the Trash; restore a campaign from the Trash; delete a segment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- 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.