Safe Gmail MCP Terms

Last updated: May 27, 2026

Safe Gmail MCP is a local tool that connects compatible Model Context Protocol clients to selected Gmail actions. By installing or using it, you agree to these terms.

Local software:

Safe Gmail MCP runs on your machine. You are responsible for the MCP client you connect to it, the Gmail account you authorize, and the local files stored under ~/.safe-gmail-mcp/.

Permitted use:

• Use Safe Gmail MCP only with Gmail accounts you own or are authorized to access.
• Review email-send previews and digests before confirming any send.
• Keep your local machine, MCP client, and OAuth credentials secure.

Prohibited use:

• Do not use Safe Gmail MCP to send spam, phishing, harassment, or unlawful messages.
• Do not use it to access another person's Gmail account without authorization.
• Do not bypass Gmail, Google, or recipient consent rules.

Experimental status:

Safe Gmail MCP was initially built as an internal Bliss AI tool and has been developed with AI assistance. It is provided as-is, without warranties. Review the code and configuration before using it for sensitive workflows.

No guaranteed delivery or inbox placement:

Gmail API access does not guarantee delivery, inbox placement, or recipient engagement. Google may limit, reject, or flag messages according to its own systems and policies.

Security reports:

Report suspected security issues privately by emailing dhruv@meditatewithbliss.com. Do not include real OAuth tokens, private email bodies, or attachment contents in reports.

Changes:

We may update these terms as Safe Gmail MCP changes. The updated date on this page will show the latest version.