Protonmail MCP Gateway Service

This integration layer is developed and maintained by amotivv, inc., the originators of Memory Box.

This Model Context Protocol (MCP) server provides robust electronic mail transmission capabilities leveraging Protonmail's dedicated Simple Mail Transfer Protocol (SMTP) backend. It empowers both the Claude Desktop client and the Cline Visual Studio Code extension to dispatch correspondence using your established Protonmail credentials.

Application Compatibility

This relay service functions seamlessly with: - Claude Desktop Application: The standalone client software for Claude interactions. - Cline VSCode Extension: The specialized extension for the Visual Studio Code editor.

The underlying conformity with the Model Context Protocol (MCP) standard ensures uniform operation across these distinct client environments.

Core Capabilities

• Transmission to a singular or a plurality of designated addressees.
• Functionality for including recipients in CC and BCC headers.
• Support for both raw text and HTML markup within the message payload.
• Built-in mechanisms for error management and comprehensive operational logging.

Setup Requirements

The gateway necessitates the specification of several environmental parameters within the MCP configuration files associated with both Claude Desktop and Cline:

Claude Desktop Initialization Path

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

Cline VSCode Extension Initialization Path

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

Both configuration dossiers mandate the following requisite variables:

• PROTONMAIL_USERNAME: Your complete Protonmail electronic mail identifier.
• PROTONMAIL_PASSWORD: Your specific SMTP authentication key (distinct from your primary account password).
• PROTONMAIL_HOST: The SMTP server address (defaults to smtp.protonmail.ch).
• PROTONMAIL_PORT: The designated SMTP connection port (587 for STARTTLS, 465 for SSL/TLS).
• PROTONMAIL_SECURE: Boolean indicator for secure connection initiation ("false" for port 587, "true" for port 465).
• DEBUG: Flag to enable verbose logging ("true" for detail, "false" for quiet operation).

For exhaustive details regarding Protonmail's SMTP interface, particularly concerning the acquisition of your necessary SMTP credential, consult the official Protonmail SMTP documentation.

Execution Protocol

Once the prerequisites are configured, message transmission is initiated via the following MCP tool invocation:

send_email

Dispatches a message utilizing your configured Protonmail SMTP credentials.

Mandatory & Optional Arguments:

• to: Target recipient email address(es). Delimit multiple addresses with commas.
• subject: The subject line of the correspondence.
• body: The textual or HTML content of the message payload.
• isHtml: (Optional) A boolean flag indicating if body contains HTML formatting (defaults to false).
• cc: (Optional) Carbon Copy addressee(s), comma-separated.
• bcc: (Optional) Blind Carbon Copy addressee(s), comma-separated.

Illustrative Example:

<use_mcp_tool>
<server_name>secure-mail-relay-proton</server_name>
<tool_name>send_email</tool_name>
<arguments>
{
  "to": "recipient@example.com",
  "subject": "Verification Message from Cline",
  "body": "This transmission confirms functionality via the Protonmail MCP gateway.",
  "cc": "oversight@example.com"
}
</arguments>
</use_mcp_tool>

Troubleshooting Guide

Should discrepancies arise during service operation, please systematically inspect the following points:

1. Confirmation that the Protonmail SMTP authentication values are precisely entered in both configuration manifests.
2. Validation that no local firewall is obstructing the configured SMTP port.
3. Review of your Protonmail account settings for any imposed outbound transmission limitations.
4. Scrutinizing the relevant diagnostic logs for explicit error reports:
5. Claude Desktop application logs.
6. Cline VSCode extension's dedicated output panel.
7. A complete restart of the Claude Desktop application or a window reload within VSCode following any configuration file modifications.

Development Workflow

To compile the service package:

cd protonmail-mcp
npm install
npm run build

Modifications to the core logic require editing files within the src directory followed by a rebuild operation.

Deployment Procedures

This relay agent can be installed within both the Claude Desktop and Cline VSCode environments. Implementation involves these steps:

Manual Installation Flow

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

2. Install requisite packages and perform the compilation: bash npm install npm run build

3. Integrate the server configuration variables into your designated MCP settings files (reference the Setup Requirements section).

Automated GitHub Integration via Cline

The Cline environment possesses native capacity for cloning and compiling MCP services directly from GitHub URLs. To leverage this:

1. Furnish Cline with the complete GitHub repository URL.
2. Permit Cline to manage the cloning and subsequent compilation processes.
3. Supply the necessary operational parameters (e.g., SMTP credentials).

Refer to the Cline MCP Server Installation Documentation for detailed guidance on invoking the GitHub-based deployment mechanism within Cline.

Supporting Information & References

• Protonmail SMTP Documentation - Official guide for utilizing Protonmail's SMTP functions.
• Nodemailer Documentation - The underlying library utilized for message delivery.
• Model Context Protocol Documentation - Specification document for the MCP framework.
• Claude Desktop Application - Direct download link for the Claude Desktop interface.
• Cline VSCode Extension - Link to install the Cline extension for VSCode.
• Cline MCP Documentation - Cline's instructional material regarding MCP servers.
• Installing MCP Servers from GitHub - Procedural guide for GitHub repository installations.

Locating Supplementary MCP Gateways

Discover additional MCP services within these indexed locations:

• Official MCP Servers Repository - A curated repository of officially sanctioned MCP services.
• Awesome-MCP Servers Repository - A community-maintained compilation of MCP services.
• mcpservers.org - A web-based index for browsing MCP services.
• mcp.so - An alternative discovery portal for MCP implementations.

Licensing

This software is distributed under the terms of the MIT License; refer to the accompanying LICENSE file for full stipulations.

WIKIPEDIA: Cloud infrastructure refers to the set of physical and software components that enable cloud computing. This infrastructure is composed of hardware (servers, storage, networking) and software (virtualization, management, orchestration) that work together to deliver computing resources as a service.

== Defining Attributes == In 2011, the U.S. National Institute of Standards and Technology (NIST) formalized five indispensable attributes characterizing cloud environments. The precise definitions provided by NIST are as follows:

On-demand self-service: "A consumer may unilaterally provision computing capacities, such as processing time and network space, as required automatically, without necessitating direct human intervention with every service vendor." Ubiquitous network access: "Capabilities are accessible via the network, utilizing standard methods that facilitate utilization across diverse client platforms, whether thin or substantial (e.g., smartphones, tablets, personal computers, and workstations)." Resource consolidation: " The vendor's computational assets are aggregated to support numerous customers via a multi-tenant architecture, wherein physical and virtual resources are dynamically allocated and reallocated based on customer demand." Elastic scalability: "Capacities can be provisioned and reclaimed elastically, sometimes automatically, to scale both outward and inward rapidly in synchronization with prevailing demand. For the customer, the available capacities often seem boundless and can be claimed in any volume at any moment." Usage metering: "Cloud systems automatically govern and optimize resource consumption by employing a measurement mechanism at an appropriate abstraction layer for the service type (e.g., capacity, CPU cycles, data transfer volume, and active user accounts). Resource consumption metrics can be observed, regulated, and reported, ensuring clarity for both the service supplier and the consuming entity. By 2023, the International Organization for Standardization (ISO) had enhanced and refined this foundational list.

== Historical Context ==

The lineage of cloud computation traces back to the 1960s, when the foundational concepts of concurrent processing (time-sharing) gained traction, largely through remote job submission (RJE) systems. The model wherein users submitted execution requests to dedicated operators for processing on large mainframe systems was predominant during this period. This era was characterized by investigation and experimentation aimed at democratizing access to substantial computational power via time-sharing, optimizing the underlying infrastructure, platform layers, and applications, thereby boosting overall end-user productivity. The term 'cloud' used to denote abstracted services originated in 1994, employed by General Magic to represent the conceptual space where mobile software agents within their Telescript environment could traverse. This analogy is attributed to David Hoffman, a communications strategist at General Magic, drawing from its established usage in telecommunications networking. The phrase 'cloud computing' gained broader visibility in 1996 when Compaq Computer Corporation drafted a strategic blueprint for future computational models and internet services. The organization aimed to achieve massive scalab