gemini-cli-extensions / gemini-cli-extensions/workspace
Feature Request: Gmail Filter Management Tools (listFilters, createFilter, deleteFilter)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 638
- Forks
- 107
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Gmail integration and its existing OAuth scope, token caching, and refresh handling. Compare the requested tools with the Gmail users.settings.filters API reference; done means the four listed filter operations are exposed with the required scope and support the stated criteria, actions, and filter IDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100