Trusted GMail MCP Server

Created By
0xfreysaa year ago
First Trusted MCP server running on AWS Nitro Enclave Trusted Execution Environment
Overview

What is Trusted GMail MCP Server?

Trusted GMail MCP Server is a secure email server running on AWS Nitro Enclave, designed to enhance the security of email communications through the Model Context Protocol (MCP).

How to use Trusted GMail MCP Server?

To use this server, you need to create an app-specific password from your Google account and configure your client's mcp.json file with the provided URL format.

Key features of Trusted GMail MCP Server?

  • Operates within a secure AWS Nitro Enclave for enhanced security.
  • Supports remote MCP server connections using SSE transport.
  • Provides a proof of concept for secure email handling.

Use cases of Trusted GMail MCP Server?

  1. Securely handling email communications in sensitive environments.
  2. Testing and developing applications that require secure email interactions.
  3. Running personal instances for enhanced privacy and security.

FAQ from Trusted GMail MCP Server?

  • Is this server secure?

Yes, it runs in a secure AWS Nitro Enclave, but users should be cautious with app-specific passwords in URLs.

  • Can I run my own instance?

Yes, instructions are provided to set up your own instance in a TEE.

  • What is the MCP?

The Model Context Protocol (MCP) is a protocol designed for secure communication between applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
0xfreysa
Star
0
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago