Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Agent Email List — Free SMTP Relay for AI Agents

✓ service owner · ai.agentemaillist.com

by lbesecker195version 0.2.0i★ 1iRuns in the cloudOfficial site ↗
Registry namecom.agentemaillist.ai/free-transactional-email-smtp-relay

How to install

What it does

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

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity4/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score11/100

Quality: Passed 3/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/4 checks · Runs on your computer

We hid some of the commands

Connect by URL: the server address did not answer when we checked

No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect Agent Email List — Free SMTP Relay for AI Agents yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

ChatGPT cannot connect Agent Email List — Free SMTP Relay for AI Agents yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

What you can do instead

B · Others in Chat & email that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Agent Email List — Free SMTP Relay for AI Agents yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

Cursor cannot connect Agent Email List — Free SMTP Relay for AI Agents yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

VS Code cannot connect Agent Email List — Free SMTP Relay for AI Agents yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

No install path has passed yet. See the maker’s instructions or pick another server in this category

Stuck? Ask people who use Agent Email List — Free SMTP Relay for AI Agents💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ ai.agentemaillist.com
Licencei
No licence stated
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.2.0
Published to registryi
Sep 15, 2026
Code last changedi
Sep 19, 2026
Last checked
Nov 20, 2026
Maker
lbesecker195
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

Tool names and descriptions exactly as the server reported them on Nov 20, 2026. The maker wrote them, not us; we show them as plain text.

  • 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.

  • list_domains

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

  • 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.

  • 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.

  • 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 f

  • 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

  • list_messages

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

  • 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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain ai.agentemaillist.com (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • – Not applicable

    Has a licence

    Not applicable: a cloud server run by the owner of ai.agentemaillist.com; you don't run code from the repo

  • ✕ Fail

    Endpoint responds

    Did not respond within 6 seconds when we checked

  • – Not applicable

    Sign-in with OAuth

    Did not respond within 6 seconds when we checked

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 8 tool descriptions and found no hidden instructions to the AI

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/agentemaillist-free-transactional-email-smtp-relay.svg)](https://mcp.popnx.com/en/servers/agentemaillist-free-transactional-email-smtp-relay)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 83% of the other 2038 servers in this category
  • Published to the registry more recently than 27% of the other 2038 servers in this category
  • Basic checks equal to or better than 50% of the other 2038 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Email List — Free SMTP Relay for AI Agents safe?

It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 6 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 24 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
Agent Email List — Free SMTP Relay for AI Agents
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereRuns in the cloud, nothing to installCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/45/54/44/44/44/4
License–MITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Free SMTP Relay and Email API for AI Agents

An email service an AI agent can sign up for on its own. No credit card, no sales call, no human with a corporate account. Free, with an MCP server, a Mailgun-shaped REST API, DKIM signing, automatic sending warmup and inbound mail.

Live at [ai.agentemaillist.com](https://ai.agentemaillist.com) · Source available · Built in Elixir and Phoenix


For AI agents: start here

This is a remote MCP server. Add it and the whole service arrives as tools:

https://ai.agentemaillist.com/mcp

JSON-RPC 2.0 over HTTP POST. The important part:

`create_account` needs no credentials. An agent that has just found this

server can call it, get an API key back, and start sending. Every other

transactional email provider stops an agent at a payment form or an identity

check. This one does not.

See what is available before committing to anything:

curl -X POST https://ai.agentemaillist.com/mcp \

-H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The tools
ToolDoesNeeds a key
create_accountOpen an account, get an API keyNo
add_domainRegister a sending domain, get its DNS recordsYes
verify_domainRe-read DNS and activate the domainYes
send_emailSend a message, with a test mode that costs nothingYes
list_domainsDomains and how much each can send todayYes
get_sending_limitsToday's cap and what graduates itYes
list_messagesSent and received mailYes
get_delivery_eventsWhat actually happened to a messageYes

Send the key as Authorization: Bearer on every call after the first.

Two things that will stop you

A domain must be verified in DNS before it can send. Publishing DNS usually needs a human with registrar access, so start it early. Until then every send returns a refusal explaining exactly that.

A newly verified domain starts at 10 messages a day and climbs as it proves itself, because a domain that opens at full volume gets filtered by receivers. Call get_sending_limits before planning a bulk send rather than finding out part way through.

Use test_mode: true on your first send. It runs the whole pipeline, screening included, sends nothing, and spends none of the daily allowance.

The limits, so you never meet one by surprise
LimitFigure
Accounts per IP address5 an hour, 20 a day
Domains per account3, rising to 50 once any one of them is verified
API requests per account600 a minute — a pace limit, not a sending limit
Sending per domainstarts at 10 a day and climbs the warmup ladder
Screening refusalssending pauses at 8 in 24 hours, and lifts by itself

get_sending_limits reports all of these live, with no domain argument needed. Every 429 carries a Retry-After. Opening a second account does not get you more: accounts are limited by address, so both come out of one budget.


For developers: the REST API

Mailgun-shaped, so most Mailgun client libraries work against it unchanged by pointing at a different base URL.

# An account and an API key, in one request

curl -X POST https://ai.agentemaillist.com/v1/accounts \ -d 'email=you@company.com' -d 'password=a sufficiently long password'

Send

curl -X POST https://ai.agentemaillist.com/v3/yourdomain.com/messages \ --user 'api:YOUR_KEY' \ -F from='you@yourdomain.com' \ -F to=someone@example.com \ -F subject='Hello' \ -F text='Hello there.'

Full API reference, written for machines to read: [ai.agentemaillist.com/llms.txt](https://ai.agentemaillist.com/llms.txt). Its sending limits are generated from the running service, so they are the limits you will actually meet rather than a number written down once.

There is also a web console at ai.agentemaillist.com/signup for setting up a domain by hand.


What it does

  • Free SMTP relay and email API. No trial clock, no card.
  • Send over SMTP or REST. Adding a domain issues SMTP credentials; the REST API is Mailgun-shaped.
  • Receive mail too. A real SMTP server on port 25, with inbound routing to your webhook. Not just sending.
  • DKIM signing, RSA-SHA256 with relaxed canonicalisation, and a keypair minted per domain.
  • Automatic sending warmup, a published ladder from 10 a day to unlimited, so a new domain builds reputation instead of being filtered.
  • Content screening in both directions, refusing outbound and filing inbound as spam.
  • Delivery events for every message, plus signed webhooks.
  • Limits that open as you prove yourself, rather than a flat cap: verifying a domain is what buys headroom, because it is the one thing a throwaway account cannot fake at scale.

Compared to the alternatives

ThisMailgunSendGridAmazon SES
An agent can sign up aloneYesNoNoNo
MCP serverYesNoNoNo
Free tierFree, no clockLimitedTrial, then paidPay per message
Inbound mailYesYesYesVia S3
Self-hostableYesNoNoNo

A longer comparison, including Brevo, Resend and SMTP2GO, is at ai.agentemaillist.com/free-smtp-relay.

Self-hosting

It is one Phoenix application and a Postgres database. One command deploys it:

sudo bash deploy/deploy.sh --domain mail.yourcompany.com --email you@company.com

That installs Postgres and nginx, builds a release, issues a TLS certificate, and sets up systemd and the firewall. DEPLOY.md explains every step it takes and what to do when one fails.

Licence

Currently unlicensed, which means all rights reserved. If you want to use or contribute to this, say so and a licence will be added.

Maintained by Logan Besecker. Questions, bug reports and cold outreach all welcome at or .


Running and operating it

Everything below is for someone running their own copy.

Running it

mix setup            # deps, database, migrations

mix phx.server # http://localhost:4005 mix test

It listens on 4005 by default, because 4000 through 4003 are taken on the machines this runs alongside. PORT overrides it.

Database

Set credentials once, in .env at the project root:

cp .env.example .env

Every mix command reads it, so nothing has to be retyped per command, and a real environment variable still overrides it: DATABASE_URL=... mix test does what it looks like. .env is gitignored; .env.example lists everything that can go in it.

Without that file, DATABASE_URL wins if it is set, which is the form that works everywhere:

DATABASE_URL=ecto://user:pass@localhost/email_provider_dev mix setup

Otherwise the standard PGUSER, PGPASSWORD, PGHOST, PGPORT and PGDATABASE variables, and only then a guess at a role named after the OS user, which is what a stock Homebrew Postgres gives you.

The guess skips the OS user when that user is root. On a server you are often root, there is rarely a Postgres role called root, and the error you get back — password authentication failed for user "root" — reads like a credentials problem when really nobody has said which credentials to use. If you hit that on a fresh box, either set DATABASE_URL or create the role:

sudo -u postgres psql -c "CREATE ROLE youruser LOGIN PASSWORD 'apassword' CREATEDB;"

On a real deployment, run the release with MIX_ENV=prod and DATABASE_URL rather than mix setup, which is a development task. One command does the whole thing, and DEPLOY.md explains every step it takes:

sudo bash deploy/deploy.sh --domain ai.agentemaillist.com --email you@example.com
On a machine that is running other things

mix setup is a developer command and it is not a good neighbour. Use this instead:

DATABASE_URL=ecto://user:pass@localhost/email_provider_dev bin/setup-server

Three differences, each of which is a way mix setup can disturb something else on the box.

It caps the build. Compiling 35 dependencies and two C NIFs fans the Elixir compiler out to one process per scheduler and make to one job per core, which on a small VPS makes the build the largest memory consumer on the machine. When memory runs out the kernel does not kill the build; the OOM killer picks the biggest process, which is usually a running application. The script serialises compilation and, under systemd as root, runs it inside a scope with a hard MemoryMax, so anything killed for memory is the build itself. Override with MEMORY_MAX=1G.

It opens two connections, not ten. Postgres has a fixed max_connections, and one that runs out answers *every* client with "sorry, too many clients already", including services that were already connected. The dev pool now defaults to 5 and reads POOL_SIZE; the script sets it to 2.

It never starts the application. mix setup boots the whole supervision tree to run priv/repo/seeds.exs, which opens a pool and starts the delivery queue. mix setup.server creates and migrates without booting anything.

If something already went offline during a mix setup, these say which of the two it was:

sudo dmesg -T | grep -i -A2 'killed process'
sudo grep -i "too many clients" /var/log/postgresql/*.log | tail
A note on PGDATABASE

Host, user and password are read from the environment. The database name is not. It is not a credential, it is which application's data this is, and PGDATABASE is a standard libpq variable that may already be exported on a shared box for some other service. Honouring it would point mix ecto.migrate at that service's database and create this application's tables inside it. To use a different database, name it in DATABASE_URL.

Environment
VariableMeaningDefault
OPENAI_API_KEYKey for the moderation endpointnone — screening is skipped
SSA_UIDSeriouslySimpleAnalytics account id for adoption reportingunset — nothing is reported
MODERATION_ENABLEDTurn screening off entirelytrue
MODERATION_ON_ERRORblock to fail closed when screening is unreachableallow
SMTP_RELAYSmarthost for outbound mailunset — mail is written to priv/local_mail
SMTP_PORT / SMTP_USERNAME / SMTP_PASSWORDSmarthost credentials587, none
SPF_HOSTWhat customers put in their SPF includemail.example.com
MX_HOSTWhat customers point their MX atmx.example.com

Without SMTP_RELAY nothing reaches the internet: the local sender writes each message to disk and logs it. That is the default on purpose.

Accounts and keys

curl -s localhost:4005/v1/accounts \

-d email=you@example.com -d password='a sufficiently long password'

The response carries an API key. It is shown once — only a SHA-256 hash is stored, so a lost key is rotated rather than looked up. Authenticate either way:

curl -s --user 'api:ep_live_...' localhost:4005/v3/domains     # Mailgun style

curl -s -H 'Authorization: Bearer ep_live_...' localhost:4005/v3/domains

Keys carry scopes (messages:send, events:read, domains:write, …). Scopes are declared per action in each controller, next to the code they guard.

Custom domains

Adding a domain generates an RSA-2048 DKIM keypair. The private half stays in the database; the public half is what the customer publishes.

curl -s --user 'api:KEY' localhost:4005/v3/domains -d name=mail.yourcompany.com

The response lists the records to publish, then:

curl -s -X PUT --user 'api:KEY' localhost:4005/v3/domains/mai

Only the beginning is shown; read the rest in the repo