Mailroom

io.github.darrylmosherPublished by GitHub account darrylmosherv1.4.5Updated Oct 26, 2026

Self-hosted gateway between your iCloud mailbox and your AI assistant, with safety built in

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Self-hosted gateway that connects an AI assistant to your iCloud mailbox through your own mailroom server, with tiered read, write and send access.

What you can do
  • Connect the assistant to a self-hosted mailroom server that fronts your iCloud mailbox.
  • Work with mail through whichever tools the API key's tier exposes: read-only, write, or send.
  • Point the client at a local or tailnet HTTPS mailroom URL rather than at iCloud directly.
When to use it
Useful if you already run or plan to run a self-hosted mailroom server for an iCloud mailbox and want an assistant to read or act on that mail under a controlled access tier.
Requirements
Runs locally over stdio via uvx from the mailroom-icloud PyPI package, on desktop only. Needs a reachable mailroom server, set by MAILROOM_URL (for example a local address or a tailnet HTTPS URL), and a mailroom API key in MAILROOM_KEY.
Before you install
MAILROOM_KEY is a secret whose tier decides whether the assistant can write or send mail, so issue a read-only key unless sending is intended. The server can act on real mailbox data, and mail content passes through your mailroom server, so host it and expose it over HTTPS deliberately.

Installation

In SourceWeft

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

3
  1. v1.4.5LatestOct 13, 2026
  2. v1.4.3Oct 13, 2026
  3. v1.1.0Oct 11, 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.