Skip to content

45 gmail mcp#54

Open
songmeo wants to merge 38 commits into46-wiki-apifrom
45-gmail-mcp
Open

45 gmail mcp#54
songmeo wants to merge 38 commits into46-wiki-apifrom
45-gmail-mcp

Conversation

@songmeo
Copy link
Contributor

@songmeo songmeo commented Jan 16, 2026

No description provided.

@songmeo songmeo linked an issue Jan 17, 2026 that may be closed by this pull request
- Conversation model now handles email checking and draft preparation
- Integrates with Gmail MCP (extended tier) for email operations
- Integrates with Shopify MCP for order detail lookup
- Posts drafts to #sell-or-die channel for human approval
- Archives emails after sending
- Keeps reasoner focused on complex tasks only
- Keep conversation prompt generic about email handling capability
- User-specific workflow (channels, format) belongs in user system prompt
- Maintains separation: code defines capabilities, user defines workflow
- Clarify that 'via' field controls message destination
- Clarify that 'attachments' field controls file attachments
- Makes it explicit how conversation model can route messages
- Show concrete example of message schema for posting to channels
- Clarify that Bro can proactively post messages
- Makes it clear how to format responses to send to specific channels
- Specify using modify_gmail_message_labels to mark emails as read
- Explain removing UNREAD label marks as read
- Explain removing INBOX label archives the email
…ndler

- List all Gmail MCP tools available (search, read, send, modify_labels)
- Provide concrete examples of modify_gmail_message_labels usage
- Show exact JSON syntax for marking as read, archiving, and both
- Clarify that conversation handler should use Gmail tools directly
- Prevent delegation to reasoner for simple email label operations
…plate

- Extract EMAIL_MANAGEMENT_WORKFLOW to separate variable
- Add workflow for promotional emails/bills/invoices/receipts (auto mark as read)
- Add customer inquiry workflow with Slack notification template
- Include order lookup via Shopify when order-related
- Template includes order details (number, date, items) if applicable
- Remove Gmail tools list (tools provided dynamically by MCP server)
- Add rule: only ONE message block per response
- Use Slack-compatible bold formatting (*text* not **text**)
- Keep email workflows in conversation handler (not reasoner)
- Add thread_ts field to ReceivedMessage dataclass
- Capture thread_ts from incoming Slack messages (continue existing thread or start new)
- Update SlackConnector.send() to accept optional thread_ts parameter
- Reply in thread for public channels, send normally for DMs
- Track current thread_ts in conversation handler
- Automatically determine if channel is DM (starts with 'D') to skip threading
- Remove _EMAIL_MANAGEMENT_WORKFLOW from conversation.py (business logic)
- Add example email workflow to README under Google Workspace section
- Users should add custom workflows to ~/bro/system_prompt.txt
- Keeps core Bro code generic and reusable
- Condense step-by-step instructions into concise bullet points
- Remove redundant explanations
- Keep essential information only
- Reduce from ~70 lines to ~25 lines
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GMAIL MCP

1 participant