MCP server · Email outreach

A virtual inbox your agent controls — send, read, reply, follow up.

OpenHelm gives your assistant a real email environment: research the recipient, compose and send from your connected account, then monitor and handle the reply thread to completion. Not just a send endpoint — the agent runs the whole conversation. Zero-install via MCP.

Email Outreach
Tool call
Sandbox
Result
Call research_recipient from my assistant.

now

Assistant called research_recipient
OpenHelm spun up a cloud sandbox
Working through the task…
Evidence-backed result returned
Where shall we steer?
Email Outreach · live

What it does

The Email Outreach server gives your assistant a complete email environment in the cloud. It researches the recipient using a stealth browser for real, current hooks, sends from your connected email account, and then monitors the inbox for replies — deciding on each one whether to answer, advance the objective, or escalate to a human. The agentic system manages the multi-turn conversation from first touch to resolution.

It is built for founders, sales and ops teams, and autonomous agents who want the whole outbound conversation handled, not just a send endpoint. Real data only: it never fabricates a recipient, a send, or a fact about your organisation, and it escalates rather than guessing when a reply asks something it cannot verify.

Endpoint

Add this URL to your MCP client.

Remote MCP URL
https://mcp.openhelm.ai/email/mcp
Local bridge (optional)
npx mcp-remote https://mcp.openhelm.ai/email/mcp

Tools

What your assistant can call.

Available on https://mcp.openhelm.ai/email/mcp

research_recipient

Research a person/business from public sources to personalise outreach, with sources.

draft_outreach_email

Draft (without sending) a personalised email for a stated objective.

send_outreach_email

Compose and send a personalised email via your connected account.

triage_inbox

Scan recent replies and classify each: summary, sentiment, needs-human, next action.

draft_reply

Draft a reply that advances the objective, flagging anything that needs a human.

check_result

Retrieve the finished result of a longer-running email task.

Get started

Connect in under a minute.

  1. 1

    Add the remote server

    In ChatGPT, Claude, Cursor or any MCP client, add a remote connector pointing at https://mcp.openhelm.ai/email/mcp. No install, no terminal, no Node setup. For clients that need a local bridge, run npx mcp-remote https://mcp.openhelm.ai/email/mcp.

  2. 2

    Connect your OpenHelm account

    Click Connect and you are sent to app.openhelm.ai/connect to authorise via OAuth 2.1. Your encrypted OpenHelm API key is wrapped in a signed token, the server itself stores no secrets.

  3. 3

    Add a card to start the trial

    New accounts add a card to activate a 14-day free trial (you are not billed during the trial). This keeps the shared cloud compute protected from multi-account abuse.

  4. 4

    Run tasks from your assistant

    Ask your assistant in plain English. It calls the right tool, OpenHelm spins up an isolated cloud browser sandbox, and returns evidence-backed structured results, polling check_result for longer runs.

Want recurring sequences and always-on reply handling instead of one-shot calls? The Email Outreach strategy runs it on a schedule.

Set up an always-on outreach agent

Common questions about the Email Outreach server

Want it run for you instead?

The MCP servers put the tools in your assistant. If you'd rather we run the whole workflow as a managed service, book a 20-minute call and we'll scope it.