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 통과 · 내 컴퓨터에서 실행돼요
명령 일부를 숨겼어요
주소로 연결: 확인할 때 서버 주소가 응답하지 않았어요
아직 확인을 통과한 설치 방법이 없어요. 만든 사람의 안내를 보거나 같은 분류의 다른 서버를 고르세요 · 만든 사람의 설치 안내 · 같은 분류의 다른 서버
먼저: 어떤 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를 받는 앱에서도 쓸 수 있어요. 예: 웹 ChatGPT(Business 이상은 전체 MCP, Pro는 읽기 전용).
같은 카테고리에는: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도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