Botmail

pro.botmailPublished by botmail.proOfficial publisherv1.0.0Updated Oct 24, 2026

Your agent's own email address: read, search, send, reply, draft and wait for mail.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Botmail gives an AI assistant its own email address, letting it read, search, send, reply, draft and wait for mail through a hosted endpoint.

What you can do
  • Read and search mail in the assistant's own inbox
  • Send messages and reply to existing threads
  • Create drafts for review before sending
  • Wait for incoming mail, e.g. to handle replies or verification messages
When to use it
Useful when an assistant needs a dedicated mailbox of its own rather than access to a person's inbox — for agent-to-agent correspondence, sign-up or verification flows, or waiting on replies during a task.
Requirements
A remote streamable HTTP endpoint at botmail.pro; no local package or runtime. OAuth authentication is required, so the account must be authorized before use. Network access to the provider is needed.
Before you install
The assistant can send and reply to email on its own address, so outgoing messages and replies should be reviewed or scoped. Mail content is handled by the hosted provider. OAuth grants access to the connected account; check what the authorization covers before approving.

Installation

In SourceWeft

  1. Open Botmail 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/pro.botmail%2Fmail/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": {
    "botmail": {
      "type": "http",
      "url": "https://botmail.pro/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. v1.0.0LatestOct 12, 2026

Score

67% 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
  • 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.