Mail for Bots

com.mailforbotsPublished by mailforbots.comOfficial publisherv0.2.0Updated Oct 24, 2026

Email inboxes for AI agents: send, reply, read verification codes, human-approved drafts.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote email service that gives an AI assistant its own inbox to send, reply, read verification codes and manage human-approved drafts.

What you can do
Send and reply to email from an agent-owned inbox, including reading verification codes and handling human-approved drafts. Connect over a remote endpoint with OAuth sign-in or an API key.
When to use it
Useful when an assistant needs its own email address for sign-ups, verification codes, correspondence or draft-and-approve workflows rather than acting through a person's mailbox.
Requirements
A remote streamable HTTP endpoint; no local package. OAuth sign-in on connect for clients that support it, otherwise a Mail for Bots API key sent as a bearer token in the Authorization header, created in the webmail.
Before you install
The Authorization header carries a secret API key; keep it private. The assistant can send and reply to email, so messages leave the account and reach third parties; review outbound mail and drafts before allowing autonomous sending.

Installation

In SourceWeft

  1. Open Mail for Bots in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.mailforbots%2Fmailforbots/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mail-for-bots": {
      "type": "http",
      "url": "https://mailforbots.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestOct 13, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.