agentsbase — Email for AI Agents

net.agentsbasePublished by agentsbase.netv1.0.1Updated Oct 24, 2026

Email for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant create email mailboxes, send and receive messages, and automatically extract verification codes.

What you can do
This local MCP server gives an assistant its own email capability. According to the registry description, it can create mailboxes, send and receive emails, and automatically extract verification codes from incoming messages. It runs as a local process over stdio, so the assistant talks to it on the same machine.
When to use it
Worth considering when an assistant needs its own inbox, for example to receive sign-up or login verification codes, or to send and read email as part of a workflow. It is a desktop-only local process, so it is not usable from a web client.
Requirements
Runs as a local process over stdio, installed from the npm package agentsbase-mcp, so Node.js and npm are needed on the machine. The manifest declares no authentication, environment variables, or headers, and it is desktop only.
Before you install
The manifest declares no credentials, but the server handles email: it can send messages on your behalf and read incoming mail, including verification codes. Treat any mailbox it creates as untrusted, and review what it sends or reads before relying on it. No payment, wallet, or key handling is described.

Installation

In SourceWeft

  1. Open agentsbase — Email for AI Agents 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. v1.0.1LatestSep 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.