MyAgentMail

com.myagentmailPublished by myagentmail.comOfficial publisherv1.0.0Updated Oct 24, 2026

Email inboxes and calendars for AI agents: send, receive, search, draft and schedule.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server giving AI agents their own email inboxes and calendars to send, receive, search, draft and schedule.

What you can do
  • Send and receive email from agent-owned inboxes
  • Search and draft messages
  • Schedule and manage calendar events
  • Connect over a hosted remote endpoint with OAuth sign-in
When to use it
Useful when an assistant needs to handle email or calendar work itself — sending or replying to messages, searching an inbox, drafting mail, or scheduling events — without a separate mail integration.
Requirements
A remote MCP endpoint at mcp.myagentmail.com; no local package or runtime. OAuth authentication is required, so a MyAgentMail account is needed. Network access to the hosted endpoint.
Before you install
The server can send email and create calendar events on the agent's behalf, so actions are externally visible and hard to undo. Access is granted through OAuth to an account; review the scopes granted. Message and calendar content is handled by the hosted provider.

Installation

In SourceWeft

  1. Open MyAgentMail 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.myagentmail%2Fmyagentmail/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": {
    "myagentmail": {
      "type": "http",
      "url": "https://mcp.myagentmail.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.0.0LatestSep 17, 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.