Say “Claude, what replied today” and mean it.

An MCP server that puts your campaigns, contacts, mailboxes and replies in front of any agent that speaks the protocol. Seventeen tools. Nine of them read. Eight of them write. None of them can send an email, because there is no send tool to call.

In build The surface below is settled and the spec is public. It is not live yet, and we are not going to pretend otherwise on a marketing page.

Three things people will actually ask

Every tool call below is one your agent would really make, with the arguments it would really send.

The conversation

What came back {{stamp}}

Seventeen tools, and one that is missing

The absence is the design. An agent cannot send from Hisendy because the verb was never exposed.

Reads Nine, no confirmation

list_campaigns Every campaign with status, sent, replies, stopped

get_campaign One campaign, its steps, its schedule and its numbers

search_contacts Contacts by field, tag, campaign or reply state

get_contact One contact, their fields and their whole history with you

list_replies Replies in a window, with the label and the confidence

get_thread One thread, trimmed, from your workspace only

list_mailboxes Each mailbox, its daily cap, where it is in the ramp, its health

get_usage Credits spent this cycle, by action, against the allowance

get_report Sends, opens off, replies, bookings, over a date range

Writes Eight, each confirmed

create_campaign Creates a draft. Unscheduled, unsendable, yours to approve

update_sequence Edits the words in a draft step. Never a live step mid send

import_contacts Adds rows, deduplicated against every list you already hold

add_suppression Blocks a domain or an address everywhere, instantly

pause_campaign Stops sending now. The one write nobody should have to confirm

resume_campaign Restarts it at the pace it was on, not from zero

draft_reply Writes a reply into the thread. Unsent, always

label_reply Sets or corrects one of the four labels

Deliberately absent Not gated, absent

send_campaign There is no code path from the protocol to the SMTP call. Scheduling is a human action in the app, and it stays one.

delete_contacts An agent with a bad plan should not be able to destroy the asset you spent a year building. Suppression is reversible. Deletion is not.

update_billing Nothing that touches a card is reachable from a tool call. Buying credits is a page with a button on it.

Two lines to connect it

Remote, over HTTP OAuth

claude mcp add --transport http hisendy \
  https://mcp.hisendy.com/v1

You approve the workspace in a browser once. No key is ever pasted into a config file, and access is revoked from Settings the moment you want it gone.

Local, over stdio API key

{ "mcpServers": { "hisendy": {
    "command": "npx",
    "args": ["-y", "@hisendy/mcp"],
    "env": { "HISENDY_API_KEY": "hs_live_..." }
} } }

A read only key is a different key. Issue one of those if all you want is an agent that reports.

Three things we will not quietly leave out.

We are not first Lemlist already ships an MCP server. We are not going to put a first on this page and hope you do not check. What we can say is that Instantly and Smartlead do not have one, and that ours refuses to send, which theirs need not.

An agent inherits your permissions, not more A member who cannot see another client workspace in the app cannot see it through a tool call either. The server is the same authorisation layer the interface uses, not a side door around it.

Every write is logged as a write Your audit trail records the tool name, the arguments, the agent and the human account behind it. When something odd happens at two in the morning you want to be able to read exactly what asked for it.

The agent can read everything. It still cannot press send.

That is the whole posture. Start free, connect a mailbox, and decide later how much of it you want to hand over.

Start free See the plans

No card. 2 mailboxes, 100 sends and 100 AI credits to start.