Mails.ai — Agent Email

io.github.RolloutsAIPublished by GitHub account RolloutsAIv0.2.9Updated Oct 2, 2026

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

The publisher's own server: Mails.ai — Agent Email

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that gives an AI assistant its own email inbox on mails.ai: sending, receiving and threading mail behind a prompt-injection firewall.

What you can do
Send email from the assistant's own mails.ai inbox, using a test key for sandbox runs or a live key for real mail delivery. Receive incoming mail and keep conversations threaded so the assistant can follow a back-and-forth. Screen message content through a prompt-injection firewall before it reaches the assistant. Point the server at a staging or self-hosted API instead of the hosted one when needed.
When to use it
Use it when an assistant needs a real email address to send and receive messages, for example handling correspondence or replying within threads, and you want incoming content filtered against prompt injection. It is less relevant if the assistant only needs to draft text without sending or receiving mail.
Requirements
Runs as a local process over stdio, installed from the npm package @mailsai/mcp-server, so Node.js is needed. Requires a mails.ai API key in the MAILS_API_KEY environment variable; a free key is available from the provider. An optional MAILS_BASE_URL variable overrides the API base URL for staging or self-hosted deployments. Network access to the mails.ai API is required.
Before you install
The server needs a mails.ai API key, which is a credential; keep it out of shared configuration. A key with the live prefix sends real mail, so use the test prefix for sandbox work and confirm before letting the assistant send. Incoming email is untrusted third-party content, and the prompt-injection firewall is the only stated safeguard. Mail content and addresses are sent to the mails.ai API.

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
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.9LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Mails integrations

Mails.ai — Agent Email

ai.mailsOfficial publisher

Mails.ai gives an AI agent its own email inbox: send, receive and thread mail, with a prompt-injection firewall in front of incoming messages.

Streamable HTTPWeb executableAuth
Communication & CollaborationCredential requiredOct 24, 2026

Zyntra - Temp e-mails MCP

Published by GitHub account dd77ss

Lets an assistant create disposable email inboxes, wait for incoming mail, and extract message content or links.

Streamable HTTPWeb executableAuth
Communication & CollaborationCredential requiredOct 24, 2026