MailBeast.ai

ai.mailbeastPublished by mailbeast.aiOfficial publisherv1.0.2Updated Oct 26, 2026

Run MailBeast.ai cold email from your AI assistant: campaigns, leads, mailboxes, replies, analytics.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MailBeast.ai MCP server that lets an AI assistant run cold email campaigns, leads, mailboxes, replies and analytics.

What you can do
  • Manage cold email campaigns through the assistant
  • Work with leads and mailboxes
  • Review replies and campaign analytics
  • No tool list is published, so exact actions are not documented
When to use it
Useful if you already run cold email outreach on MailBeast.ai and want to check or drive campaigns, leads, replies and analytics from an AI assistant instead of the web app.
Requirements
Remote MCP endpoint at mcp.mailbeast.ai over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A MailBeast.ai account is implied.
Before you install
The server can act on live outreach data such as campaigns, leads and mailboxes, so changes may send email or alter prospect records. OAuth grants access to your MailBeast.ai account. Tool-level behavior is not documented here, so review permissions before connecting.

Installation

In SourceWeft

  1. Open MailBeast.ai 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/ai.mailbeast%2Fmailbeast/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": {
    "mailbeast-ai": {
      "type": "http",
      "url": "https://mcp.mailbeast.ai/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

2
  1. v1.0.2LatestOct 19, 2026
  2. v1.0.1Oct 19, 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.