mcp server
dev.mailkite/agent-mail
Give an AI agent its own inbox — receive email as a webhook, send over a verified domain.
Description as published by the maintainer. Source
- version 0.12.0
- active
- workflow automation
active — Most recent push to the repository was 2026-08-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-05 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.12.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
dev.mailkite/email-agent
— last commit 2026-08-05, shares email, email-api, mailkite
Email for AI agents — send, receive as a webhook, manage domains, templates, routing.
-
dev.mailkite/inbound-email
— last commit 2026-08-05, shares email, email-api, mailkite
Turn inbound email into a webhook — verify, parse, route, and store incoming messages.
-
dev.mailkite/mail-receive
— last commit 2026-08-05, shares email, email-api, mailkite
Receive inbound email as clean JSON — manage domains, routes, and webhooks. MailKite.
-
dev.mailkite/mail-send
— last commit 2026-08-05, shares email, email-api, mailkite
Send transactional email over a verified domain — templates, attachments, custom headers.
-
dev.mailkite/mailkite
— last commit 2026-08-05, shares email, email-api, mailkite
Send email, manage domains, DNS, webhooks, templates, and inbound routing on MailKite
-
com.tinysend/tinysend
— last commit 2026-06-23, shares email, email-api
Email for agents: newsletters, subscribers, contacts, broadcasts. OAuth sign-in, no API key.
-
e2a — email for AI agents
— last commit 2026-08-06, shares email, email-api
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
-
Dead Simple Email
— last commit 2026-07-30, shares email, email-api
Give an agent its own inbox: send, receive, and pull signup codes from real email.
-
SenderKit
— last commit 2026-08-06, shares email-api
Build and send email, SMS, and push straight from your AI agent.
-
Courier
— last commit 2026-06-13, shares email-api
Continuity protocol for autonomous AI agents. Agent messaging with SMTP bridge and LN payments.
These share tags the maintainers applied themselves, such as email, email-api, mailkite. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agents, email, email-api, llm-tools, mailkite, mcp, mcp-server, model-context-protocol.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab