emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 4/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 7/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 0/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 11/100 |
品質: 基本チェック 3/4 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
チェック 3/4 合格 · あなたのパソコンで動きます
一部のコマンドを隠しています
URL でつなぐ:確認時にサーバーのアドレスが応答しませんでした
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください · 作者のインストール手順 · 同じカテゴリのほかのサーバー
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude はまだ Agent Email List — Free SMTP Relay for AI Agents につなげません
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
ChatGPT はまだ Agent Email List — Free SMTP Relay for AI Agents につなげません
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
B · チャット・メール の中で ChatGPT につなげる別のサーバー
同じカテゴリでよく使われているものから、キーなしでアドレスだけでつなげるものを選びました
Claude Code はまだ Agent Email List — Free SMTP Relay for AI Agents につなげません
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
Cursor はまだ Agent Email List — Free SMTP Relay for AI Agents につなげません
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
VS Code はまだ Agent Email List — Free SMTP Relay for AI Agents につなげません
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
確認を通った方法がまだありません。作者の説明を見るか、同じカテゴリの別のサーバーを選んでください
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月20日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
create_accountCreate 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_domainsList the sending domains on this account, with their verification state and how much of today's sending allowance each has left.
add_domainRegister 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_domainRe-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_emailSend 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_limitsHow 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_messagesRecent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.
get_delivery_eventsWhat 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.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック
レジストリ名はドメイン ai.agentemaillist.com で確認済みです(レジストリがドメインの所有を確認しています)
コードの最終更新:2 か月前
対象外:ai.agentemaillist.com の所有者が自ら運営するクラウドのサーバーで、リポジトリのコードを実行しません
チェックしたとき、6秒以内に応答がありませんでした
チェックしたとき、6秒以内に応答がありませんでした
8件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/agentemaillist-free-transactional-email-smtp-relay)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック4項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は2 か月前、最新バージョン(0.2.0)がレジストリに届いたのは2 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| これ Agent Email List — Free SMTP Relay for AI Agents | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドで動き、インストール不要 | クラウドでもパソコンにインストールでも使える | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | はい | いいえ |
| 基本チェック | 3/4 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| ライセンス | – | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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
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"}'
| Tool | Does | Needs a key |
|---|---|---|
create_account | Open an account, get an API key | No |
add_domain | Register a sending domain, get its DNS records | Yes |
verify_domain | Re-read DNS and activate the domain | Yes |
send_email | Send a message, with a test mode that costs nothing | Yes |
list_domains | Domains and how much each can send today | Yes |
get_sending_limits | Today's cap and what graduates it | Yes |
list_messages | Sent and received mail | Yes |
get_delivery_events | What actually happened to a message | Yes |
Send the key as Authorization: Bearer on every call after the first.
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.
| Limit | Figure |
|---|---|
| Accounts per IP address | 5 an hour, 20 a day |
| Domains per account | 3, rising to 50 once any one of them is verified |
| API requests per account | 600 a minute — a pace limit, not a sending limit |
| Sending per domain | starts at 10 a day and climbs the warmup ladder |
| Screening refusals | sending 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.
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'
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.
| This | Mailgun | SendGrid | Amazon SES | |
|---|---|---|---|---|
| An agent can sign up alone | Yes | No | No | No |
| MCP server | Yes | No | No | No |
| Free tier | Free, no clock | Limited | Trial, then paid | Pay per message |
| Inbound mail | Yes | Yes | Yes | Via S3 |
| Self-hostable | Yes | No | No | No |
A longer comparison, including Brevo, Resend and SMTP2GO, is at ai.agentemaillist.com/free-smtp-relay.
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.
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 .
Everything below is for someone running their own copy.
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.
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
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
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.
| Variable | Meaning | Default |
|---|---|---|
OPENAI_API_KEY | Key for the moderation endpoint | none — screening is skipped |
SSA_UID | SeriouslySimpleAnalytics account id for adoption reporting | unset — nothing is reported |
MODERATION_ENABLED | Turn screening off entirely | true |
MODERATION_ON_ERROR | block to fail closed when screening is unreachable | allow |
SMTP_RELAY | Smarthost for outbound mail | unset — mail is written to priv/local_mail |
SMTP_PORT / SMTP_USERNAME / SMTP_PASSWORD | Smarthost credentials | 587, none |
SPF_HOST | What customers put in their SPF include | mail.example.com |
MX_HOST | What customers point their MX at | mx.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.
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.
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