Agent Email List — Free SMTP Relay for AI Agents

Working · 1.4 s

com.agentemaillist.ai/free-transactional-email-smtp-relayv0.2.0 Domain verified

Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.

Communication

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://ai.agentemaillist.com/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

add_domain

Register a domain to send from, and get the DNS records that must be published before it will work. Publishing DNS usually needs a human with registrar access, so start this early. The domain cannot send until verify_domain succeeds.

namestring, required

A bare domain such as mail.yourcompany.com. A subdomain is better than the root.

This tool isn't marked read-only, so it may change something on the server or in an account you connected.

I understand, run it anyway

Tools (8)

add_domain

Argument	Type	Description
name*	string	A bare domain such as mail.yourcompany.com. A subdomain is better than the root.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "A bare domain such as mail.yourcompany.com. A subdomain is better than the root."
    }
  }
}

create_account

Create an account on this email service and get an API key back. Needs no existing credentials, so an agent with nothing can call this first. The key is returned once and never again. Free, with no card and no trial clock.

Argument	Type	Description
name	string	Optional display name.
email*	string	A contact address for the account.
password*	string	At least 12 characters. Needed only to sign in to the web console.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "email",
    "password"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Optional display name."
    },
    "email": {
      "type": "string",
      "description": "A contact address for the account."
    },
    "password": {
      "type": "string",
      "description": "At least 12 characters. Needed only to sign in to the web console."
    }
  }
}

get_delivery_events

What happened to messages on this domain: accepted, delivered, failed, and so on. A send returning success means queued, not delivered; this is where the delivery outcome actually appears.

Argument	Type	Description
event	string	Filter to one type, such as delivered or failed.
limit	integer
domain*	string
recipient	string

Input schema (JSON)

{
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "event": {
      "type": "string",
      "description": "Filter to one type, such as delivered or failed."
    },
    "limit": {
      "type": "integer"
    },
    "domain": {
      "type": "string"
    },
    "recipient": {
      "type": "string"
    }
  }
}

get_sending_limits

How much this domain may send today and what graduates it to the next rung, plus this account's standing: how many domains it may hold and whether sending is paused. New domains start at a low daily cap and climb as they prove themselves, so check this before planning a bulk send rather than discovering it part-way. Call it with no domain for the account-level answer alone.

Argument	Type	Description
domain	string	Optional. Omit for account limits without a domain's allowance.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Optional. Omit for account limits without a domain's allowance."
    }
  }
}

list_domains

List the sending domains on this account, with their verification state and how much of today's sending allowance each has left.

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

list_messages

Recent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.

Argument	Type	Description
limit	integer	Up to 100. Defaults to 25.
domain*	string
folder	string
direction	string

Input schema (JSON)

{
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Up to 100. Defaults to 25."
    },
    "domain": {
      "type": "string"
    },
    "folder": {
      "enum": [
        "inbox",
        "spam"
      ],
      "type": "string"
    },
    "direction": {
      "enum": [
        "outbound",
        "inbound"
      ],
      "type": "string"
    }
  }
}

send_email

Send a message. The domain must be verified and the from address must belong to it. Counts one against the daily allowance per recipient. Set test_mode true to run the whole pipeline, including content screening, without sending anything and without spending allowance — do that first when building.

Argument	Type	Description
to*	string	One address, or several separated by commas.
from*	string	An address at that domain.
html	string	Optional HTML body.
text	string	Plain text body.
domain*	string	The verified domain to send from.
subject	string
test_mode	boolean	Accept and screen the message but send nothing. Defaults to false.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "domain",
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "One address, or several separated by commas."
    },
    "from": {
      "type": "string",
      "description": "An address at that domain."
    },
    "html": {
      "type": "string",
      "description": "Optional HTML body."
    },
    "text": {
      "type": "string",
      "description": "Plain text body."
    },
    "domain": {
      "type": "string",
      "description": "The verified domain to send from."
    },
    "subject": {
      "type": "string"
    },
    "test_mode": {
      "type": "boolean",
      "description": "Accept and screen the message but send nothing. Defaults to false."
    }
  }
}

verify_domain

Re-read DNS now and mark the domain active if its SPF and DKIM records are visible. DNS takes minutes to hours to propagate; poll this every few minutes, not every few seconds.

Argument	Type	Description
name*	string

Input schema (JSON)

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    }
  }
}