Email Agent Workflows (CLI First, MCP Fallback)

This guide defines the default execution pattern for email-focused tasks in Brainforge agent workflows.

1) Default operating model

For email-oriented operations (primarily Gmail and Calendar, with optional Drive/Docs/Sheets context):

Use Google Workspace CLI (gws) first
Use Google Workspace MCP as fallback when:
- gws is not installed/authenticated
- The MCP tool is clearly better suited
- The user explicitly asks to use MCP

References:

Task type	Primary path	Fallback path
Search client email threads	`gws gmail users messages list/get`	Gmail MCP tools (if available)
Draft follow-up email from context	`gws` read context, draft in chat/markdown	MCP read tools + chat draft
Create/update calendar events	`gws calendar events insert/update`	Calendar MCP tools (if available)
Read client docs/sheets	`gws drive/docs/sheets`	Google Workspace MCP

If Gmail/Calendar MCP tools are unavailable in a given environment, keep the workflow on gws and note the fallback limitation.

Use these docs when generating content:

Communication standards (calendar titles, Zoom links, email writing):
email-communication-standards.md
Execution SOP for agents:
email-client-comms-sop.md

Never invent credentials or API keys; use configured auth only.
Never send client email automatically unless the user explicitly confirms.
Keep a single canonical meeting link in calendar invites (avoid duplicate Zoom/Meet links).
Follow naming conventions exactly for calendar titles and email subject lines.