Gmail MCP
A local integration for mailbox workflows with scoped access, previews and explicit confirmation.
MCP integration development
The problem
Mailbox automation can save repetitive work, but a send, delete or settings change has consequences. A useful integration needs boundaries around what an assistant can request.
Engineering decision
The design makes permissions and confirmation part of the tool contract. Permanent deletion and administrative settings are disabled by default, and protocol output is kept separate from diagnostic logging.
Workflow overview
This is a prototype description, not a live email demo. The portfolio cannot read or send mail. Account credentials and real messages are never used as showcase material.
Workflow
- Request a scoped operation
- Preview the proposed change
- Confirm before execution
An explanation of the workflow, not an interactive application.
How it works
The local stdio server maps Gmail API operations into MCP tools. OAuth scopes determine available access; sensitive operations use dry-run previews and typed confirmations. The source includes mocked contract tests.
Collaboration & credits
Uses Google’s Gmail API and OAuth infrastructure. My work is the local tool interface and operation boundaries around that API.
Verification details
The source and setup documentation were reviewed for the catalogue. No live mailbox was connected or modified.
- Evidence date
- Not recorded
- Source revision
- Not recorded
- Working tree
- unrecorded
Source review only; a pinned runtime verification and date were not recorded.