Trusted GMail MCP Server

What is Trusted GMail MCP Server?

A remote MCP server for Gmail that runs inside an AWS Nitro enclave, providing a trusted execution environment. It uses SSE transport and requires an app‑specific password for authentication.

How to use Trusted GMail MCP Server?

Configure the server URL in your client’s mcp.json with your Gmail address and app‑specific password, then restart the client. For self‑deployment, follow the repo’s instructions to build and run the server inside a Nitro enclave.

Key features of Trusted GMail MCP Server

• Runs inside an AWS Nitro enclave for hardware‑attested security
• Uses SSE (Server‑Sent Events) transport for remote connectivity
• Authenticates via Google app‑specific passwords
• Supports code attestation verification
• Open‑source and forkable

Use cases of Trusted GMail MCP Server

• Read and manage Gmail messages through an MCP‑compatible AI assistant
• Automate email workflows with verifiable trust in the execution environment
• Run a private, self‑hosted Gmail MCP server in a cloud enclave
• Verify that the deployed server matches the intended codebase via attestation

FAQ from Trusted GMail MCP Server

How do I authenticate to the server?

Use an app‑specific password from your Google account and pass it in the URL query string as ASP.

What are the security risks of passing credentials in the URL?

URLs can be logged by proxies, browsers, and servers, may appear in browser history, and can leak via the Referer header. This is a proof‑of‑concept limited by current MCP authentication standards.

How can I verify the code running in the enclave?

Clone the repo, run the included verifier, and provide the PCR2 hash and signed attestation to confirm the code identity.

Can I run my own instance?

Yes. Provision a Nitro‑enabled EC2 instance, run the setup script, allocate memory, build the enclave, and start the server using the provided make commands.