"author:Raoof128" matching MCP servers:

Moves attachments to and from the local disk without their bytes passing through the model's context, and manages several mail accounts under one owner so every write names its account explicitly. Enforces a server-side allow/ask/deny policy where risky writes create a pending action a person must approve in the browser, with no tool able to permanently delete mail.

A Gmail MCP server for Claude: attachment support in both directions, multi-account, and every mailbox mutation behind a server-enforced permission model.