mcpField
E
email-agent

email-agent

Remote
mailkite.devCommunication0Updated 7w ago

About email-agent

email-agent is MailKite’s email MCP server for AI agents, covering mail sending, domain and template management, and agent inboxes. It exposes MailKite API methods as MCP tools.

Key features

  1. 01Send email
  2. 02Manage domains and templates
  3. 03Search documentation
  4. 04Set up agent inboxes
  5. 05Route and handle inbound mail

Use cases

  1. 01Let an AI agent send email
  2. 02Give an agent its own inbox
  3. 03Manage email domains and templates

MCP support

It exposes MailKite API methods as tools to MCP clients, with hosted HTTP access or local operation using an API key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.mailkite.dev/mcp?ref=email-agent
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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

{
  "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:

claude mcp add --transport http mailkite https://mcp.mailkite.dev/mcp

In Claude Code you can also install the plugin:

/plugin marketplace add mailkite/claude-code
/plugin install mailkite@mailkite

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):

{ "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):

LibraryRepoDistribution
MailKite for Node.jsmailkite-nodenpm
MailKite for Pythonmailkite-pythonPyPI
MailKite for Rubymailkite-rubyRubyGems
MailKite for Javamailkite-javaMaven Central
MailKite for PHPmailkite-phpPackagist
MailKite for Gomailkite-goGo modules
@mailkite/climailkite-clinpm
@mailkite/mcp (this repo)mailkite-mcpnpm
@mailkite/clientmailkite-jsnpm
@mailkite/expomailkite-exponpm
MailKiteClientmailkite-swiftSwift Package Manager
dev.mailkite:mailkite-clientmailkite-kotlinMaven Central
mailkite_clientmailkite-flutterpub.dev

Docs & links

Generated from the shared MailKite API contract. © MailKite.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.