Hunter MCP server
Hunter in any MCP client, through Memtro: Hunter does not publish this server. Memtro's Hunter connector reads Hunter 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
Hunter email prospecting: the team's saved leads (search by name, company or list; when each was saved, verification and sending status), lead lists and tags, the account's credit balance, and Domain Search for the email addresses at a company (spends credits). Also reads sequences and sending accounts. Can save, update and delete leads, create, rename, delete, attach and remove tags, create and delete lead lists, and create a sequence, add steps, add or remove recipients, and start, pause, resume or archive it, when you ask.
Reads
hunter_accountThe Hunter account: plan, when credits reset, and searches, verifications and credits used and remaining this period.hunter_list_leadsThe team's saved leads in Hunter, newest first by default: name, email, position, company, website, confidence, verification and sending status…hunter_get_leadOne saved Hunter lead by id, with its notes (cut at 500 characters).hunter_list_lead_listsThe team's lead lists in Hunter, newest first: id, name, how many leads, static or dynamic, folder.hunter_list_tagsThe team's lead tags in Hunter, newest first: id, name, colour.hunter_domain_searchSPENDS HUNTER CREDITS: 1 credit per 10 email addresses returned, rounded up (nothing for a repeat of the same search in the same billing period).hunter_list_sequencesThe team's email sequences in Hunter, newest first: id, name, recipients, whether started, paused or archived, whether the key's user may edit it…hunter_list_email_accountsThe email accounts the key's user can send sequences from in Hunter: id, address, owner name, sending status (active, paused, warming)…
Acts, when you ask
These change something in Hunter. 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.
hunter_create_leadSaves one new lead in Hunter.hunter_create_tagCreates a lead tag in Hunter, shared across the team.hunter_tag_leadAttaches an existing tag (hunter_list_tags) to a saved lead.hunter_update_leadChanges fields on a saved Hunter lead (email, name, position, department, company, website, notes).hunter_delete_leadPermanently deletes a saved lead from Hunter (it cannot be undone).hunter_untag_leadRemoves one tag from one saved lead in Hunter; the tag itself stays.hunter_update_tagRenames or recolours a lead tag in Hunter, everywhere it is used.hunter_delete_tagPermanently deletes a lead tag in Hunter; it is taken off every lead that had it.hunter_create_lead_listCreates a static leads list in Hunter (leads are added to it with hunter_create_lead).hunter_delete_lead_listPermanently deletes a leads list in Hunter.hunter_create_sequenceCreates a draft email sequence in Hunter, owned by the key's user.hunter_add_sequence_stepAdds an email step to a Hunter sequence: subject, body (plain text or HTML…hunter_add_sequence_recipientsAdds people to a Hunter sequence by email (up to 50) and/or saved lead id (up to 50).hunter_remove_sequence_recipientsTakes people (by email, up to 50) out of a Hunter sequence.hunter_start_sequenceStarts a draft Hunter sequence: every recipient in it is emailed from the sequence's sender accounts on its schedule.hunter_pause_sequencePauses an active Hunter sequence; scheduled emails stop until it is resumed.hunter_resume_sequenceResumes a paused Hunter sequence; its scheduled emails to recipients start going out again.hunter_archive_sequenceArchives a started (active or paused) Hunter sequence: no further emails are sent, and the API has no way to unarchive it.
Connect it
First connect Hunter on Dashboard → Connections, then add Memtro to your client once. The Hunter 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 Hunter 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
- › Which email addresses does Hunter know at northwind.com?
- › How many Hunter credits are left this month?
- › Which of our saved leads have unverified emails?
- › Save Priya Sharma at Acme as a lead in the Q3 outreach list
- › Pause the Globex follow-up sequence
Questions
- Is this an official Hunter MCP server?
- No. It is Memtro's MCP server with Memtro's Hunter connector behind it: the connector reads Hunter through its API with the credentials you connect on Dashboard → Connections, and Hunter 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 Hunter?
- Only when you ask, and only what it has been granted: save a new lead (refused when the email is already a lead); create a lead tag; attach an existing tag to a lead; update or delete a saved lead; remove a tag from a lead, or rename, recolour or delete a tag; create or delete a leads list; create a draft email sequence and add steps to it; add people to a sequence (on an active one Hunter may email them at once), or take them out; start a sequence (emails every recipient), pause, resume or archive it. 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.