Mails.ai — Agent Email

ai.mailsv0.2.10Updated Oct 3, 2026

A real inbox for AI agents: send, receive and thread email, behind a prompt-injection firewall.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Gives an AI assistant its own email inbox to send, receive and thread messages, with a prompt-injection firewall.

What it does
Mails.ai provides an email inbox for AI agents, letting an assistant send, receive and thread email conversations. It is described as placing a prompt-injection firewall in front of that inbox. It runs as a local stdio process, so the assistant starts it on the user's machine.
When to use it
Worth adding when an assistant needs to handle real email — sending messages, reading replies, and keeping threads together — rather than only drafting text. The firewall is aimed at the risk of hostile content arriving in an inbox.
Requirements
A local runtime able to run the npm package @mailsai/mcp-server over stdio, on a desktop machine. A mails.ai API key in the MAILS_API_KEY environment variable is required; an mk_test_ key targets the sandbox and an mk_live_ key sends real mail. MAILS_BASE_URL optionally overrides the API base URL for staging or self-hosted deployments.
Before you install
MAILS_API_KEY is a secret and must be supplied by environment variable. An mk_live_ key sends real email to real recipients, so an assistant using it can act outside the sandbox; use an mk_test_ key while testing. Incoming mail is untrusted content and may attempt prompt injection, which is what the described firewall addresses.

Installation

In SourceWeft

  1. Open Mails.ai — Agent Email in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.2.10LatestOct 3, 2026