Mailyond

에이전트에서 동일한 도메인의 앱 이메일을 보내고 답장에 응답하세요: 연결된 모든 도메인에서 스레드를 나열, 읽기, 답장하고 send_email도 지원합니다. API 키 인증.

mailyond.com에서 보기

호스팅형 MCP 서버

npx add-mcp 'https://mailyond.com/mcp'

Claude Code, Codex, Cursor 등에 설치됩니다

문서

One inbox for every domain you own.

Read and answer mail for all your domains in one place. Send from your app with one API key.

One DNS setup per domain. No forwarding rules, no second service for sending.

Connect your first domain

7 days free on the Basic plan.

Inbox

project1project2project3

tom@acme.cosupport@project1.com

Can't reset password

2m

sara@company.iosupport@project2.com

Billing question

8m

dev@startup.cosupport@project3.com

API rate limits?

14m

hello@corp.comsupport@project1.com

Feature request

1h

A customer emails support@yourproduct.com. Then what?

Right now it hits a forwarding rule, shows up in your personal inbox two days later, and your reply goes out as the wrong person.

Two services per domain

One service sends mail from your app. Something else catches what comes back. Both get set up again for every domain you add.

A different place for every domain

Each domain ends up with its own mailbox, login or forwarding rule, so answering five customers means checking five places.

Replies go out as the wrong you

Forwarding gets the mail to your Gmail. Answering as support@yourdomain.com is the part that keeps failing DMARC.

Reply as the right brand

Answer from the address they wrote to.

The Mailyond inbox with a message list, per-domain tags on each email, and an open support request with reply, reply all and forward buttons.

Built for founders and small teams running more than one product

Every address on every domain you own, arriving in the same inbox.

Every domain, one inbox

Mail for all your domains lands in a single inbox, color tagged so you know which project it came from.

Threaded conversations

Conversations stay threaded, and reply all and forward work the way you expect.

Same domains, one API

Send transactional mail from your app with one POST. No second vendor, no second DNS setup.

Your main inbox doesn't have to move

you@yourdomain.com stays exactly where it is. Point support.yourdomain.com at Mailyond and nothing about your current setup changes.

you@domain.comstays on Gmail

support.domain.comhandled by Mailyond

How it works

01

Add three DNS records

DKIM, Return-Path and MX. Paste them in, hit verify, about 5 minutes.

02

Mail starts arriving

Anything sent to any address on that domain shows up in your inbox.

03

Reply, or send from code

Answer in the dashboard, or POST to the API with your workspace key.

Send from your app with one POST

No SDK to learn, no config file. One API key per workspace.

fetch("https://mailyond.com/api/external/emails", {
  method: "POST",
  headers: { "Authorization": "Bearer myond_..." },
  body: JSON.stringify({
    to: "user@example.com",
    from: "support@yourdomain.com",
    subject: "Welcome",
    html: "<h1>Hello!</h1>"
  })
})

Already on Resend? You can keep it and use Mailyond for the inbox. If you'd rather have sends and replies on one bill, point the Resend SDK at https://mailyond.com/api/external, swap in your myond_ key, and resend.emails.send() keeps working.

Read and answer replies from Claude or Grok Bot

Mailyond runs an MCP server, so your agent reads the inbox across every domain you have connected and replies in the right thread. Same API key you already use for sending.

claude mcp add --transport http \
  mailyond https://mailyond.com/mcp \
  --header "Authorization: Bearer myond_..."

Setup Mailyond mcp server from https://mailyond.com/mcp using API key myond_...
  • list_conversations What came in, across every domain or just one of them. Sent and spam on request.
  • get_conversation The whole thread as plain text.
  • reply_to_conversation Answers in-thread, from the address the mail arrived at.
  • send_email A new message from any connected domain.
  • list_domains Which domains that key can read and send on.

There is nothing to install. Cursor, Windsurf and VS Code take the same URL and header in their own mcp.json, and the same key works over plain HTTP if you would rather write the calls yourself.

Pricing

Basic

$10/month

  • Up to 5 domains
  • 3,000 emails / month
  • $1.80 / 1,000 extra emails
  • No per-inbox pricing

Five domains in one inbox, sending and receiving, on one bill and one DNS setup each. That is $2 a domain.

Start 7 days free

Agency

$40/month

  • Up to 30 domains
  • 15,000 emails / month
  • $1.30 / 1,000 extra emails
  • No per-inbox pricing
  • Up to 10 workspace members

Thirty domains under one login, at a flat rate instead of a separate mailbox bill for each one.

Start 7 days free

Need more?

Tell us how many domains and how much volume, and we'll put a plan together.

Contact us

Before you connect anything

Why this exists

I run five products, each on its own domain. Customer mail reached me through a forwarding rule and I answered it from my personal Gmail, so customers got replies from an address that had nothing to do with the product they bought. I built Mailyond because I wanted this inbox to exist for myself. It handles my domains before it handles yours.

Rares, founder

Connect your first domain

7 days free on the Basic plan.