ProtonMail SMTP Gateway Service (MCP Implementation)

This Model Context Protocol (MCP) intermediary is developed by amotivv, inc., the engineers behind Memory Box.

This server component leverages Protonmail's Simple Mail Transfer Protocol (SMTP) for sending emails. It authorizes integrations such as Claude Desktop and the Cline VSCode add-on to dispatch communications utilizing your authenticated Protonmail account credentials.

Supported Platforms

This relay is operational across the following environments: - Claude Desktop Client: The native application supporting Claude interactions. - Cline Visual Studio Code Extension: The dedicated extension for VSCode environments.

The unified implementation ensures cross-platform compatibility due to adherence to the Model Context Protocol (MCP) standard.

Core Capabilities

• Transmit electronic messages to single or multiple designated recipients.
• Capability to include Carbon Copy (CC) and Blind Carbon Copy (BCC) recipients.
• Full support for crafting messages in both unformatted text and HyperText Markup Language (HTML).
• Robust error detection mechanisms and comprehensive activity logging.

Necessary Parameters

The operational server requires the configuration of several environment variables within the respective MCP configuration manifests for both Claude Desktop and Cline:

Claude Desktop Configuration File Location

Path: /Users/your-username/Library/Application Support/Claude/claude_desktop_config.json

Cline VSCode Extension Configuration File Location

Path: /Users/your-username/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Both locations mandate the following key-value pairs:

• PROTONMAIL_USERNAME: Your registered Protonmail address.
• PROTONMAIL_PASSWORD: Your specific SMTP authentication credential (distinct from the primary account password).
• PROTONMAIL_HOST: The SMTP server address (default value: smtp.protonmail.ch).
• PROTONMAIL_PORT: The communication port (standard defaults: 587 for STARTTLS, 465 for SSL/TLS).
• PROTONMAIL_SECURE: Connection security flag (default: "false" for port 587, "true" for port 465).
• DEBUG: Toggle for verbose logging (set to "true" to activate detailed output, "false" to suppress).

For comprehensive details on accessing Protonmail's SMTP features, particularly obtaining the correct SMTP password, consult the official Protonmail SMTP documentation.

Operational Usage

Once the server is provisioned correctly, emails can be dispatched using the following tool invocation structure:

send_email Tool

Initiates the transmission of an electronic message via your configured Protonmail SMTP account.

Input Arguments:

• to: Target email address(es). Multiple targets should be comma-delimited.
• subject: The title line of the electronic correspondence.
• body: The core textual or HTML content of the message.
• isHtml: (Optional) Boolean indicator specifying if body is formatted as HTML (defaults to false).
• cc: (Optional) Secondary recipient(s) for carbon copy, comma-separated.
• bcc: (Optional) Tertiary recipient(s) for blind carbon copy, comma-separated.

Invocation Example:

smtp-relay-proton send_email { "to": "contact@corp.com", "subject": "System Notification", "body": "

Alert: System Check Complete

Processing finished successfully.

", "isHtml": true, "cc": "manager@corp.com" }

Troubleshooting Guide

Should issues arise with the relay service, systematically check the following points:

1. Confirm the accuracy of the SMTP access credentials within both configuration files.
2. Check local network security policies to ensure the SMTP port is not restricted by a firewall.
3. Investigate if the associated Protonmail account has any imposed transmission limits.
4. Review system logs for error reports:
5. Logs generated by the Claude Desktop application.
6. Output panel within the Cline VSCode extension.
7. After applying any configuration updates, execute a soft restart (reload VSCode window or restart Claude Desktop).

Development Workflow

To compile the source code:

bash cd protonmail-mcp npm install npm run build

Modifications to the server logic should occur within the src directory, followed by recompilation.

Deployment Instructions

This relay can be integrated into both the Claude Desktop client and the Cline VSCode add-on environment. The procedure for integration is as follows:

Manual Setup

1. Obtain a local copy of the source repository: bash git clone https://github.com/your-username/protonmail-mcp.git cd protonmail-mcp

2. Install dependencies and execute the build routine: bash npm install npm run build

3. Update the relevant MCP settings files with the server connection details (refer to the Configuration section).

Automated Installation via Cline

Cline supports automated cloning and compilation of MCP services directly from GitHub URLs:

1. Provide Cline with the target GitHub repository URL.
2. Allow Cline to execute the clone and build steps.
3. Supply necessary credential inputs (e.g., SMTP credentials) as prompted.

Refer to the Cline MCP Server Installation Documentation for comprehensive instructions on GitHub-based deployment.

References

• Official Guide: Protonmail SMTP Integration - Essential details for SMTP usage.
• Nodemailer Project - The underlying library powering the email transmission.
• Model Context Protocol Specification - Documentation for the communication framework.
• Download Claude Desktop - Access the standalone Claude application.
• Install Cline VSCode Extension - Obtain the VSCode extension.
• Cline Documentation: MCP Quickstart - Cline's guide for setting up MCP solutions.
• Cline Guide: Installing from GitHub - Steps for repository-based installation.

Discovering Additional MCP Services

Explore these repositories and directories for other available MCP servers:

• Official MCP Server Repository - Centralized collection of endorsed services.
• Awesome-MCP Servers List - Community-maintained catalog.
• mcpservers.org - Web directory for service discovery.
• mcp.so - Alternative portal for locating MCP solutions.

Licensing

This project is distributed under the terms of the MIT License (see the accompanying LICENSE file for full stipulations).

== Strategic Business System Context == Enterprise management solutions encompass all applications, controls, computational frameworks, operational methodologies, etc., leveraged by organizations to effectively navigate dynamic marketplaces, secure competitive advantage, and enhance overall corporate performance.

=== Functional Classification Overview === Tools address various organizational divisions and can be systematically categorized based on management facets. Examples include tools for foresight (planning), workflow management (process), record-keeping, human resource administration, executive decision support, and oversight (control).

A functional breakdown typically identifies these core operational areas:

Systems for data input verification across all departments. Frameworks designed for monitoring and optimizing business procedures. Applications focused on data aggregation and strategic determination.

Contemporary management utilities have experienced rapid transformation over the last decade, driven by swift technological progression, making the selection of optimal business instruments for specific organizational contexts increasingly complex. This difficulty is fueled by persistent pressures to reduce operational expenditures, maximize revenue streams, deepen comprehension of client requirements, and consistently deliver required products in the precise manner demanded by the end-user.

Within this environment, leadership must adopt a strategic posture regarding management tools, moving beyond simple adoption of the newest available technology. Managers often integrate tools wholesale without customization, resulting in operational instability. Prudent selection and subsequent tailoring of business management tools to align precisely with organizational necessities—rather than adapting the organization to the tool—is critical.

== Prominent Management Techniques (Historical Data) == A 2013 analysis by Bain & Company surveyed the global application of management tools, reflecting regional needs influenced by market conditions. The leading ten methodologies identified were:

Strategic Planning Frameworks Client Relationship Management (CRM) Personnel Feedback Surveys (Engagement) Competitive Benchmarking Performance Monitoring via Balanced Scorecard Defining Core Capabilities Outsourcing Strategy Organizational Transition Programs (Change Management) Logistics and Materials Flow Oversight (SCM) Corporate Mandate and Vision Articulation Customer Group Definition (Segmentation) Comprehensive Quality Assurance (TQM)

== Business Software Applications == Collections of computer programs utilized by personnel to execute varied enterprise functions are known as business software or enterprise applications. These applications serve to elevate productivity metrics, quantify performance indicators, and execute diverse organizational tasks with precision.

This field evolved from foundational Management Information Systems (MIS) into comprehensive Enterprise Resource Planning (ERP) systems. Subsequently, Customer Relationship Management (CRM) capabilities were integrated, leading to the current paradigm of cloud-based enterprise management suites.

While a tangible connection exists between Information Technology investment and organizational outcomes, two factors are paramount for value creation: the efficacy of the deployment process and the meticulous selection and adaptation of the chosen technological assets.

== Solutions Tailored for Small and Medium Enterprises (SMEs) == Tools specifically addressing the needs of SMEs are vital as they offer avenues to curtail operational expenditure and enhance administrative efficiency...