Email Automation for OpenClaw with Transmit

TL;DR for AI Agents & Humans

Transmit's remote MCP server gives your OpenClaw agent full access to send emails, manage campaigns, templates, and contacts. No API keys stored in config files.

18 MCP tools covering the entire Transmit email API.
Remote server: nothing to install, API key entered once in the browser and encrypted server-side.
Works with OpenClaw, Claude Desktop, Cursor, Windsurf, ChatGPT, and more.
Edge-deployed on Cloudflare Workers, available in 300+ cities worldwide.

Why your AI agent needs a dedicated email API

OpenClaw is everywhere right now, and one of the first things people try is email automation. The default approach is connecting your personal Gmail, but there are real problems with that.

Giving an AI agent broad access to your entire inbox is a security risk. Researchers have demonstrated prompt injection attacks through crafted emails, where a malicious message in your inbox can manipulate what your agent does next. Beyond security, you also hit rate limits, token expiration issues, and the general messiness of mixing personal email with programmatic sending.

The better approach: a dedicated email API. No inbox exposure. No shared credentials. Your agent gets purpose-built tools for sending and managing email, with proper authentication and rate limits designed for programmatic use.

Why remote MCP matters

Most email MCP servers today are local. You run npx some-mcp-server, store an API key in an environment variable, and hope nobody reads your config file. Every time there is an update, you have to pull a new version.

Transmit takes a different approach. Our MCP server is remote, hosted on Cloudflare Workers at mcp.xmit.sh. The first time you connect, your browser opens and you enter your API key once. It gets encrypted and stored server-side. Your config file has nothing but a URL. No packages to install, no versions to manage.

Local MCP (most providers)

✗ npm install or npx required
✗ API key in plaintext env var
✗ Manual updates
✗ Runs on your machine

Transmit MCP (remote)

✓ Just a URL
✓ API key entered once in browser, encrypted server-side
✓ Always up to date
✓ Edge-deployed, 300+ locations

Setting up Transmit MCP with OpenClaw

The setup takes about 30 seconds.

Step 1: Create a Transmit account

If you do not have one yet, create a free Transmit account. The free tier includes 3,000 emails per month. Grab your API key from the dashboard (Settings → API Keys).

Step 2: Add the MCP server

Add the Transmit MCP server to your MCP client config. For OpenClaw, add it in your MCP settings. For Claude Desktop, Cursor, or any other client, paste this config:

MCP Config

{ "mcpServers": { "transmit": { "type": "http", "url": "https://mcp.xmit.sh/mcp" } } }

That is the entire config. No API key, no environment variables, no binary path.

Step 3: Enter your API key

The first time your agent connects, your browser opens to mcp.xmit.sh/authorize. Paste your API key (the one from Step 1), click Authorize, and you are done. Your key gets encrypted and stored server-side. The access token refreshes automatically, so you never have to do this again.

Step 4: Start prompting

Your agent now has access to 18 email tools. Here are some things you can ask it to do:

“Send a welcome email to new-user@acme.com using our onboarding template”

“Create a product launch campaign for next Tuesday and send to the beta-users list”

“Build an HTML email template for order confirmations with orderId and customerName variables”

“Check if bounce@example.com is suppressed”

“List all my senders and duplicate last month's newsletter with an updated subject”

What tools does your agent get?

The Transmit MCP server exposes 18 tools covering the full platform API, plus 2 guided workflows for common tasks.

Category	Tools
Email	`send_email`
Campaigns	`list` `get` `create` `update` `delete` `duplicate`
Templates	`list` `get` `create` `update` `delete`
Contacts	`add_contact`
Senders	`list` `get`
Lists	`get_lists`
Suppressions	`list` `check`
Workflows	`create-campaign` `create-template`

How the auth works under the hood

When your agent first connects, here is what happens:

1Your MCP client connects to mcp.xmit.sh/mcp and gets a 401. It discovers the OAuth endpoints via /.well-known/oauth-authorization-server.

2The client registers itself via dynamic client registration, then opens mcp.xmit.sh/authorize in your browser.

3You enter your Transmit API key and authorize. Your key is encrypted and stored in the OAuth grant (never in plaintext, never in your config).

4The client receives an access token (valid 1 hour) and a refresh token (never expires). When the access token expires, it silently refreshes. You never have to re-authenticate.

Security note: Your API key is encrypted with AES and stored server-side in the OAuth grant. Even if someone could read the KV store directly, they cannot decrypt it without the token. Your config file contains zero secrets.

Real-world use cases

Here are some practical workflows that work great with OpenClaw + Transmit:

Daily briefing emails

Have your agent compile news, weather, or project updates and send you a formatted email every morning.

Customer onboarding

When a new user signs up, your agent can add them as a contact, create a personalized welcome email from a template, and send it immediately.

Campaign management

Ask your agent to duplicate last week's newsletter, update the subject line and content, schedule it for Thursday, and check delivery stats after it sends.

Bounce monitoring

Your agent can check suppressions, identify problematic addresses, and help you maintain list hygiene without touching a dashboard.

Get started

Transmit's MCP server is open source and free to use. The free tier includes 3,000 emails per month, which is more than enough to start automating.

Daily briefing emails

Customer onboarding

Campaign management

Bounce monitoring

Related Articles