AgentMail

to.agentmailPublished by agentmail.toOfficial publisherv1.0.0Updated Oct 24, 2026

Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

AgentMail gives an AI assistant email inboxes of its own, letting it send, receive, reply to, search and manage threaded email over MCP.

What you can do
Send email from agent-owned inboxes and reply within existing threads. Receive and read incoming messages. Search and manage threaded conversations. The manifest lists no individual tools, so exact operations follow the provider's documentation.
When to use it
Use it when an assistant needs its own email address to handle correspondence, such as sending notifications, replying to inbound mail, or tracking email threads as part of a workflow.
Requirements
A remote MCP endpoint at mcp.agentmail.to reached over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The assistant can send and reply to email on your behalf, so messages may reach real recipients. It can also read and manage inbox contents. Review what it sends before enabling it on a live mailbox.

Installation

In SourceWeft

  1. Open AgentMail 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/to.agentmail%2Fagentmail/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": {
    "agentmail": {
      "type": "http",
      "url": "https://mcp.agentmail.to/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.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.