Mailcycle

email.mailcyclePublished by mailcycle.emailv0.6.2Updated Oct 24, 2026

An email address for your AI agent. Read, wait for and reply to mail, decrypted on your machine.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Gives an AI agent its own email address so it can read, wait for, and reply to mail, with messages decrypted locally.

What you can do
Mailcycle provides an email address for an AI agent. According to the description, the assistant can read incoming mail, wait for messages to arrive, and send replies. Decryption of mail happens on the user's own machine. No individual tools are listed in the supplied manifest.
When to use it
Worth considering when you want an assistant to handle email correspondence directly, such as monitoring an inbox, waiting for a specific message, or drafting and sending replies. It is a desktop-only local process, so it suits a personal machine rather than a shared or hosted environment.
Requirements
Runs as a local process over stdio, installed from the npm package mailcycle-mcp, so Node.js and npm are needed. The manifest declares no authentication, environment variables, or headers, and no accounts or API keys are listed. Desktop only; not available as a web executable.
Before you install
The server can send replies on your behalf, so outgoing mail may be delivered without further review. It handles email content and performs decryption locally; the manifest declares no credentials, but the description implies access to a mailbox, so treat message contents as sensitive. No tool list was supplied, so verify exactly what it can read and send before installing.

Installation

In SourceWeft

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

Tools

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

Version history

2
  1. v0.6.2LatestOct 15, 2026
  2. v0.6.1Oct 14, 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.