Give an AI agent its own inbox — receive email as a webhook, send over a verified domain.
Give an AI agent its own inbox — receive email as a webhook, send over a verified domain. The agent mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need one environment variable: MAILKITE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by dev.mailkite; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"mailkite": {
"command": "npx",
"args": ["-y", "@mailkite/mcp"],
"env": { "MAILKITE_API_KEY": "mk_live_…" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MAILKITE_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.