Trusted MCP Server

🚀 Trusted Gmail MCP Server

This is a Gmail MCP server running in a secure AWS Nitro encrypted computing enclave. It was initially forked from the MCP server of Claude Post. Most MCP servers run locally via stdio transport; we implemented a remote MCP server using sse transport with reference to this guide.

🚀 Quick Start

✨ Features

• Runs in a secure AWS Nitro encrypted computing enclave.
• Forked from the MCP server of Claude Post.
• Implemented a remote MCP server using sse transport.

📦 Installation

To use this MCP server, you need an app-specific password. Then simply add the following code block to the mcp.json file of your client:

    "gmail_mcp": {
      "url": "https://gmail.mcp.freysa.ai/sse/?ADDR=<your.email@gmail.com>&ASP=<your app-specific password>"
    }

Note that you may need to restart your client.

💻 Usage Examples

Basic Usage

To use this MCP server, you need an app-specific password. Then simply add the following code block to the mcp.json file of your client:

    "gmail_mcp": {
      "url": "https://gmail.mcp.freysa.ai/sse/?ADDR=<your.email@gmail.com>&ASP=<your app-specific password>"
    }

Note that you may need to restart your client.

🔧 Technical Details

Security Considerations

This implementation is a proof of concept. Passing the app-specific password via the URL is an insecure pattern for the following reasons:

• URLs may be logged by proxies, browsers, and servers.
• URLs may appear in browser history.
• URLs may be leaked to third-party websites via the Referer header. Currently, MCP clients have limitations on how to connect to the server. At the time of release, the MCP specification did not define a standard authentication mechanism for SSE servers. Therefore, we were unable to use more secure modes (such as bearer tokens or other authorization headers), which are typically preferred. For additional security, consider:

1. Creating a dedicated app-specific password for this purpose.
2. Using a secure VPN or private network for access.
3. Running your own instance using the provided instructions.

Concept

AWS Nitro Enclaves provide isolated computing environments that enhance security through hardware verification. When code executes in a Nitro Enclave, the platform generates cryptographic measurements of the code's identity and state. These measurements serve as guarantees that the code has not been modified and is running as expected, preventing unauthorized changes. For more information, see this blog post.

Verifying Code Attestation

To verify code attestation, follow these steps:

1. Build the code.
2. Run the verifier.

Command Examples:

# Run the following command in the terminal to build the code
npm install

# Run the following command in the terminal to run the verifier
node index.js

Running Your Own Instance in TEE

To set up from EC2 to download the repository and install dependencies, follow these steps:

1. Check the security group settings to ensure the ports are open.
2. Download the repository.
3. Install the dependencies.
4. Adjust the configuration.
5. Run the instance.