Busymail

app.busymailPublished by busymail.appOfficial publisherv1.0.0Updated Oct 25, 2026

Read, organise and send from your existing email accounts. Nothing sends without your approval.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Busymail connects an assistant to your existing email accounts so it can read, organise and send mail, with sending held for your approval.

What you can do
Read mail from your existing email accounts and review what is there. Organise messages in those accounts. Prepare outgoing email, which is sent only after you approve it.
When to use it
Useful when you want an assistant to triage, sort or draft replies across email accounts you already use, while keeping a human check before anything is sent.
Requirements
A remote MCP endpoint reached over streamable HTTP. Authentication is required: a bearer token created under Settings, MCP in Busymail, supplied in the Authorization header.
Before you install
The Authorization bearer token is a secret granting access to your email accounts; keep it private and revoke it if exposed. The server can organise and send mail, so review proposed changes and outgoing messages before approving them.

Installation

In SourceWeft

  1. Open Busymail in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/app.busymail%2Fbusymail/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.

{
  "mcpServers": {
    "busymail": {
      "type": "http",
      "url": "https://busymail.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 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.