Summary
Request to add Gmail filter management capabilities to the Google Workspace MCP server.
Requested Tools
| Tool |
Description |
gmail_listFilters |
List all filters for the authenticated user |
gmail_createFilter |
Create a new filter with criteria and actions |
gmail_getFilter |
Get a specific filter by ID |
gmail_deleteFilter |
Delete a filter by ID |
Use Cases
- Automate inbox organization setup
- Programmatically manage email routing rules
- Set up filters for specific projects or workflows
- Bulk filter management
Technical Reference
Gmail API supports filter management via users.settings.filters resource:
https://developers.google.com/gmail/api/reference/rest/v1/users.settings.filters
OAuth Scope
Requires: https://www.googleapis.com/auth/gmail.settings.basic
Why This Belongs Upstream
Building a separate MCP server for Gmail filters would require either:
- Duplicating OAuth authentication (users log in twice)
- Sharing tokens between MCP servers (fragile, non-standard)
- Building an OAuth proxy (adds complexity)
Since the google-workspace MCP already has Gmail auth, token caching, and refresh logic, adding filter tools there is ~50-100 lines vs ~300-400 lines + auth complexity for a separate server.
Summary
Request to add Gmail filter management capabilities to the Google Workspace MCP server.
Requested Tools
gmail_listFiltersgmail_createFiltergmail_getFiltergmail_deleteFilterUse Cases
Technical Reference
Gmail API supports filter management via
users.settings.filtersresource:https://developers.google.com/gmail/api/reference/rest/v1/users.settings.filters
OAuth Scope
Requires:
https://www.googleapis.com/auth/gmail.settings.basicWhy This Belongs Upstream
Building a separate MCP server for Gmail filters would require either:
Since the google-workspace MCP already has Gmail auth, token caching, and refresh logic, adding filter tools there is ~50-100 lines vs ~300-400 lines + auth complexity for a separate server.