The tool set is the full create-read-update-delete surface plus search, so an assistant can triage a list rather than only read it. The setup cost is the usual Google one: make a project, enable the API, create a desktop OAuth client and run the consent flow once.
A server over the Google Tasks API covering the whole task lifecycle: searching, listing, creating, updating, deleting and clearing completed items.
- Search finds tasks matching a query and returns them with their details
- List walks all tasks, paginating with a cursor
- Create adds a task with a title, notes and a due date on the list you choose
- Update changes a title, notes or due date, or flips a task to completed
- Delete removes a task; clear sweeps completed tasks off a list
- Individual tasks are also exposed as readable resources, with title, status, due date, notes and metadata
A Google Cloud project with the Google Tasks API enabled and an OAuth client for a desktop app, authorised once against the tasks scope. The resulting credentials are stored locally. Node, with the server built from source.
One command plus a key — npx -y @smithery/cli install @zcaceres/gtasks --client claude, then supply credentials
