FFF.GS Mail MCP. Last updated 20 August 2026.
FFF.GS Mail MCP is a personal tool. It is installed and run by one operator on their own computer, against Gmail accounts that the same operator owns. It is not offered to the public and has no other users.
When the operator authorises an account, FFF.GS Mail MCP receives an OAuth refresh token for that account. Using that token it can read and change data in that mailbox: messages, threads, drafts, labels, attachments, and Gmail settings such as filters, forwarding, and the vacation responder.
Nowhere. Mail content is requested from the Gmail API, handed to the AI assistant that asked for it, and discarded. FFF.GS Mail MCP has no database, no analytics, no logging service, and no backend of its own. Nothing is transmitted to the developer or to any third party other than Google and the assistant the operator chose to run it with.
Refresh tokens are the only data written to disk. They are stored in
accounts.json in the operator's home directory on the operator's own
machine.
FFF.GS Mail MCP's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, data obtained through Google APIs is not used for advertising, is not sold, is not transferred to anyone except as needed to provide the tool's function to the operator, and is not read by humans other than the operator.
FFF.GS Mail MCP does not request the https://mail.google.com/ scope, so
it cannot delete mail permanently. It requests only these scopes:
gmail.modifygmail.composegmail.sendgmail.settings.basicA refresh token stays on disk until the operator deletes it or revokes the app's access. Access can be revoked at any time from Google Account permissions, which invalidates the stored token immediately.