logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

mcp-electronic-mail-gateway

Facilitates the composition and dispatch of electronic mail messages, supporting multiple recipients and file attachments. This server component additionally offers functionality to query local file systems for artifacts matching specified naming conventions, all while enforcing secure communication via the SMTP protocol.

Author

mcp-electronic-mail-gateway logo

Shy2593666979

MIT License

Quick Info

GitHub GitHub Stars 56
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

smtpmcpemailsmcp serverserver emailemail compose

MCP Electronic Mail Dispatcher

This Model Context Protocol (MCP) server component furnishes comprehensive electronic mail capabilities. It empowers Large Language Models (LLMs) to formulate and transmit correspondence, alongside performing targeted searches for associated files within designated storage locations. 1742711978001

1742712768132

Core Capabilities

  • Transmission of missives to numerous addressees concurrently
  • Provision for incorporating supplementary digital documents (attachments)
  • Utility for locating files within specified directories based on pattern matching criteria
  • Enforcement of secure data exchange protocols utilizing SMTP

Accessible Functions

  • dispatch_message - Sends electronic correspondence utilizing supplied subject, body content, and destination addresses.
  • addressees (list of strings, mandatory): Enumeration of recipient email identifiers
  • payload (string, mandatory): The primary textual content of the communication
  • topic (string, mandatory): The subject identifier for the correspondence
  • enclosures (list of strings or single string, optional): Digital assets accompanying the message (referenced by filename)

  • locate_artifacts - Scans a designated file system path for files whose names conform to a supplied textual template.

  • template (string, mandatory): The textual expression used to match against file names

Usage Instructions (Prompts)

  • dispatch_message
  • Initiate the transmission of an electronic message, optionally including attached items
  • Parameters:

    • addressees (required): The roster of target email identifiers
    • payload (required): The main textual substance of the communication
    • topic (required): The designation line for the electronic mail piece
    • enclosures (optional): Attached digital documents
  • locate_artifacts

  • Perform a search for digital items matching a specific template
  • Parameters:
    • template (required): The search criterion for file nomenclature

Deployment

Via Pip Installation

Install necessary prerequisites:

pip install pydantic python-dotenv

Electronic Mail Configuration

A configuration file named email.json containing SMTP server specifications:

[
  {
    "domain": "@gmail.com",
    "server": "smtp.gmail.com", 
    "port": 587
  },
  {
    "domain": "@outlook.com",
    "server": "smtp.office365.com",
    "port": 587
  },
  {
    "domain": "@yahoo.com",
    "server": "smtp.mail.yahoo.com",
    "port": 587
  }
]

Operationalizing

Initiating the Dispatcher Service

Launch the MCP Electronic Mail Dispatcher via:

python -m mcp_email_server (--dir /path/to/artifact/repository)

Configuration for Claude.app Integration

Incorporate the following structure into your Claude settings:

Conda Environment Setup

{
  "mcpServers": {
    "email": {
      "command": "D:\\conda\\envs\\mcp\\python.exe",
      "args": [
        "C:\\Users\\YourUserName\\Desktop\\servers\\src\\email\\src\\mcp_server_email",
        "--dir",
        "C:\\Users\\YourUserName\\Desktop"
      ],
      "env": {
        "SENDER": "2593666979q@gmail.com",
        "PASSWORD": "tuogk......."
      }
    }
  }
}

UV Environment Setup

{
  "mcpServers": {
    "email": {
      "command": "uv",
      "args": [
        "~\\servers\\src\\email\\src\\mcp_server_email",
        "--dir",
        "C:\\Users\\YourUserName\\Desktop"
      ],
      "env": {
        "SENDER": "2593666979q@gmail.com",
        "PASSWORD": "tuogk......."
      }
    }
  }
}

Security Considerations

  • App-specific credentials might be mandatory for services such as Gmail.
  • The service implements restrictions on the categories of digital file types permitted as enclosures for enhanced security.

Permitted File Formats

The dispatcher accepts the subsequent digital asset extensions:

  • Documentation: doc, docx, xls, xlsx, ppt, pptx, pdf
  • Compressed Archives: zip, rar, 7z, tar, gz
  • Plain Text Items: txt, log, csv, json, xml
  • Visual Media: jpg, jpeg, png, gif, bmp
  • Miscellaneous: md

Illustrative Examples

Transmitting an Electronic Message

{
  "addressees": ["recipient@example.com"],
  "topic": "Test Electronic Correspondence from MCP Dispatcher",
  "payload": "This is a validation transmission sent via the MCP Electronic Mail Dispatcher.",
  "enclosures": ["document.pdf", "visual_asset.jpg"]
}

Searching for Digital Attachments

{
  "template": "summary_data"
}

Collaboration

We welcome community contributions to enhance and expand the capabilities of the MCP Electronic Mail Dispatcher. Whether introducing novel functions, refining current features, or improving documentation, your input is highly valued.

For reference regarding other MCP service implementations and design patterns, consult: https://github.com/modelcontextprotocol/servers

Submissions for merging changes are encouraged! Feel free to propose novel concepts, report defects, or suggest improvements to elevate the utility of the MCP Electronic Mail Dispatcher.

Licensing Information

The MCP Electronic Mail Dispatcher is distributed under the terms of the MIT License. This grants users the latitude to employ, modify, and redistribute the software, subject to the stipulations outlined in the MIT License.

WIKIPEDIA: Cloud computing is defined by ISO as "a framework for facilitating network-accessible, scalable, and flexible pools of shared physical or virtual assets, featuring automated provisioning and management capabilities on demand." It is colloquially known as "the cloud".

== Defining Attributes == In 2011, the United States' National Institute of Standards and Technology (NIST) specified five 'essential characteristics' for cloud environments. The precise definitions from NIST are:

On-demand self-service: "A purchaser can independently allocate computational resources, like server time and network storage, as required, automatically, without necessitating human intervention from the service provider for each request." Broad network access: "The capabilities are accessible over the network via standardized methods that encourage utilization across various client platforms, whether thin or robust (e.g., mobile devices, tablets, personal computers, and workstations)." Resource pooling: " The supplier's computational assets are aggregated to support multiple consumers within a multi-tenant structure, wherein distinct physical and virtual resources are dynamically allocated and reallocated based on consumer demand." Rapid elasticity: "Resources can be flexibly provisioned and decommissioned, occasionally automatically, to scale up or down swiftly in correlation with demand fluctuations. To the consumer, the available resources often appear limitless and can be appropriated in any quantity instantaneously." Measured service: "Cloud systems automatically regulate and optimize resource consumption by employing metering functions at an abstraction layer suitable for the service type (e.g., storage capacity, processing power, data transfer rate, and active user accounts). Resource utilization is trackable, controllable, and reportable, ensuring transparency for both the service provider and the consumer regarding the consumed resources." By 2023, the International Organization for Standardization (ISO) had broadened and refined this set of criteria.

== Historical Progression ==

The genesis of cloud computing traces back to the 1960s, with the initial concepts of time-sharing gaining traction through remote job entry (RJE). The 'data center' paradigm, where users submitted computational tasks to human operators for execution on mainframe systems, predominated during this period. This era was marked by exploration and trial regarding methods to extend large-scale computation access to a wider user base via time-sharing, optimizing the underlying infrastructure, software platforms, and applications, thereby boosting end-user productivity. The figurative representation of 'the cloud' for virtualized services originated in 1994, employed by General Magic to depict the spectrum of 'locations' that mobile software agents operating in the Telescript ecosystem could navigate to. This metaphor is attributed to David Hoffman, a communications specialist at General Magic, drawing inspiration from its established use in telecommunications and networking contexts. The term 'cloud computing' gained broader recognition in 1996 when Compaq Computer Corporation formulated a strategic business outline for forthcoming computational models and the Internet. The enterprise aspired to achieve superch

See Also

`