Bavimail

com.bavimailv1.0.1Updated Oct 15, 2026

Email for AI agents: send email, read inbound email, and manage aliases and domains.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an AI agent send and read email and manage sending aliases and domains through the Bavimail email API.

What you can do
Bavimail exposes 12 tools for agent-driven email. Agents can send a single transactional email or a batch of up to 100, cancel a queued or scheduled email, and look up or list recent outbound emails. They can also list and fetch inbound emails, list per-agent inbox aliases, and create, list, verify, and check DNS status for sending domains.
When to use it
Useful when an assistant needs to send transactional email, monitor or summarize an inbox, or manage sending identities and domains without leaving the chat. It fits agent workflows in Claude Desktop, Cursor, Cline, or another MCP host.
Requirements
Runs locally over stdio via npx @bavimail/mcp-server, so Node.js is needed. A Bavimail API key is required in BAVIMAIL_API_KEY; the server exits with an error if it is missing. Optional BAVIMAIL_API_BASE_URL overrides the API endpoint. Network access to the Bavimail API is required.
Before you install
The API key in BAVIMAIL_API_KEY grants access to send and read email; the README recommends scoped keys with low daily limits and a sandbox domain for agent use rather than production keys. Sending emails is a write action and emails_cancel is marked destructive. Inbound email is untrusted third-party content and should not be allowed to drive tool calls without review.

Installation

In SourceWeft

  1. Open Bavimail 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestOct 15, 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.