Agent Mail

dev.mailkitePublished by mailkite.devOfficial publisherv0.12.0Updated Oct 24, 2026

Give an AI agent its own inbox — receive email as a webhook, send over a verified domain.

VerifiedStreamable HTTPWeb executableDeveloper Tools Communication & Collaboration

Server details

Identifier: dev.mailkite/agent-mail
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mailkite.dev, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.mailkite%2Fagent-mail.svg)](https://sourceweft.com/mcp/dev.mailkite%2Fagent-mail?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

MailKite's hosted email MCP server that lets an AI assistant send mail over a verified domain, manage domains, search docs, and run its own inbox.

What you can do: Send email and manage sending domains through the MailKite API methods exposed as tools, one tool per API method per the shared contract. Give an agent its own inbox: route inbound mail to a built-in inbox agent that answers, files, or escalates. Search the MailKite documentation from the assistant. The full tool list and schemas are published in MailKite's library docs rather than in this listing.
When to use it: Use it when you want an assistant to send transactional or product email from a verified domain, or to receive and triage inbound mail through a dedicated agent inbox, without writing your own email integration.
Requirements: A remote MCP endpoint at mcp.mailkite.dev reached over streamable HTTP, with OAuth authentication required (one-click browser sign-in). A MailKite account and a verified sending domain are implied by the described features. A local npm variant exists that uses a MAILKITE_API_KEY environment variable instead of OAuth.

Before you install

The server can send email and manage domains, so actions are outward-facing and hard to undo. Inbound mail can be routed to an inbox agent that answers, files, or escalates on its own, which may act without review. The hosted endpoint requires OAuth sign-in; the local variant needs a MailKite API key passed in an environment variable. Message content and domain settings are handled by MailKite's service.

Installation

In SourceWeft

Open Agent Mail in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.mailkite%2Fagent-mail/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agent-mail": {
      "type": "http",
      "url": "https://mcp.mailkite.dev/mcp?ref=agent-mail"
    }
  }
}

README

[MailKite]

@mailkite/mcp

Email for every product you ship — receive email as a webhook, send over a verified domain, give an AI agent its own inbox.
The official MailKite library for AI agents (MCP).

Docs · Library guide · mailkite.dev · AI agents

[npm] [MailKite MCP server – quality and maintenance score on Glama]

Read-only mirror. This repo is a generated, release-time mirror of the MailKite monorepo (the private source of truth) — development doesn't happen here. Install from npm and open issues against the MailKite docs.

Install

json

{  "mcpServers": {    "mailkite": {      "command": "npx",      "args": ["-y", "@mailkite/mcp"],      "env": { "MAILKITE_API_KEY": "mk_live_…" }    }  }}

{  "mcpServers": {    "mailkite": {      "command": "npx",      "args": ["-y", "@mailkite/mcp"],      "env": { "MAILKITE_API_KEY": "mk_live_…" }    }  }}

Tools

One tool per MailKite API method, generated from the shared contract. Full list + schemas: https://mailkite.dev/docs/libraries#mcp.

Use it from an AI agent — MCP + Agent connectors

MailKite speaks the Model Context Protocol: every API method is a tool your AI assistant (Claude, Cursor, …) can call — send mail, manage domains, search the docs, and give an agent its own inbox. Full guide: https://mailkite.dev/docs/ai-agents.

Hosted (recommended) — one-click OAuth, no key to copy:

In Claude Code you can also install the plugin:

Any chat/UI agent: "Add the MCP server at https://mcp.mailkite.dev/mcp and authenticate in the browser when prompted."

Local (static key, offline / CI):

json

{ "mcpServers": { "mailkite": { "command": "npx", "args": ["-y", "@mailkite/mcp"], "env": { "MAILKITE_API_KEY": "mk_live_…" } } } }

{ "mcpServers": { "mailkite": { "command": "npx", "args": ["-y", "@mailkite/mcp"], "env": { "MAILKITE_API_KEY": "mk_live_…" } } } }

Give an agent its own inbox. Route inbound mail to a built-in inbox agent (the agent route action) and it answers, files, or escalates on its own — see https://mailkite.dev/docs/ai-agents.

All MailKite libraries

Same contract, every language — pick the one for your stack (full list: https://mailkite.dev/docs/libraries):

Library	Repo	Distribution
MailKite for Node.js	`mailkite-node`	npm
MailKite for Python	`mailkite-python`	PyPI
MailKite for Ruby	`mailkite-ruby`	RubyGems
MailKite for Java	`mailkite-java`	Maven Central
MailKite for PHP	`mailkite-php`	Packagist
MailKite for Go	`mailkite-go`	Go modules
@mailkite/cli	`mailkite-cli`	npm
@mailkite/mcp (this repo)	`mailkite-mcp`	npm
@mailkite/client	`mailkite-js`	npm
@mailkite/expo	`mailkite-expo`	npm
MailKiteClient	`mailkite-swift`	Swift Package Manager
dev.mailkite:mailkite-client	`mailkite-kotlin`	Maven Central
mailkite_client	`mailkite-flutter`	pub.dev

Docs & links

📚 Documentation: https://mailkite.dev/docs
📦 This library's guide: https://mailkite.dev/docs/libraries#mcp
🤖 AI agents (MCP + inbox agents): https://mailkite.dev/docs/ai-agents
🌐 Website: https://mailkite.dev
🧭 All libraries: https://mailkite.dev/docs/libraries

_{Generated from the shared MailKite API contract. © MailKite.}

Source: README.md at commit 2131014

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.12.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.