searchLABSCO SUMMARY
Your task list, editable from wherever you are already talking.
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.
What it is
A server over the Google Tasks API covering the whole task lifecycle: searching, listing, creating, updating, deleting and clearing completed items.
What you get
- 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/zcaceres/gtasks-mcp.git
USE CASES
01
Capturing an action item as it comes up
Add the task with notes and a due date in the same turn you agreed to it.
02
Finding the task you half remember
Search by whatever words you do recall and get the matching tasks with their details.
03
Closing out a batch of work
Mark the finished items done, then clear the completed ones off the list.
04
Reviewing what is outstanding
Walk the whole list, paging through it, and see what is still open.
05
Cleaning up something added by mistake
Remove the task outright rather than leaving it to clutter the list.
6 tools
Listed in project docs. Your client may show a different list.
listcreateupdatedeleteclearBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- Bun (the build and auth scripts run it)
- Node.js
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/zcaceres/gtasks-mcp.git
cd gtasks-mcp
npm installCreate a new Google Cloud project
Enable the Google Tasks API
Configure an OAuth consent screen ("internal" is fine for testing)
Add scopes https://www.googleapis.com/auth/tasks
Create an OAuth Client ID for application type "Desktop App"
Download the JSON file of your client's OAuth keys
Rename the key file to gcp-oauth.keys.json and place it in the root of the gtasks-mcp folder.
TERMINAL
npm run build
npm run start authComplete the sign-in that opens in your browser; the credentials are saved in the root of the gtasks-mcp folder.
Point the block below at dist/index.js inside the gtasks-mcp folder.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"gtasks": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FILE>/dist/index.js"
]
}
}
}
