Dovemails

com.dovemailsPublished by dovemails.comOfficial publisherv1.1.0Updated Oct 24, 2026

Email inboxes for AI agents: send, wait for mail, reply in thread, forward and label.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Dovemails gives an AI assistant its own email inbox: send mail, wait for incoming messages, reply in a thread, forward and label.

What you can do
  • Send email from an agent-owned inbox
  • Wait for incoming mail and read what arrives
  • Reply within an existing thread
  • Forward messages and apply labels to organize them
When to use it
Useful when an assistant needs to handle email itself, such as sending notifications, waiting for a reply or verification message, or triaging and labeling incoming mail in a dedicated inbox.
Requirements
A remote MCP endpoint at app.dovemails.com over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The assistant can send, forward and label email on your behalf, so messages may reach real recipients. Access is granted through OAuth to a Dovemails account; review which inbox and scopes you authorize. Mail content passes through the Dovemails service.

Installation

In SourceWeft

  1. Open Dovemails 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.dovemails%2Fmcp/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": {
    "dovemails": {
      "type": "http",
      "url": "https://app.dovemails.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. v1.1.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.