gtasks

This MCP server provides a Google Tasks integration that lets clients list, read, search, create, update, delete, and clear tasks in Google Tasks through a set of dedicated tools. The server exposes actions via the gtasks tools: search to find tasks by a query, list to enumerate tasks with optional pagination, create to add new tasks (with optional list, notes, and due date), update to modify an existing task (including title, notes, status, and due date), delete to remove a task, and clear to remove all completed tasks from a list. Each task is accessible as a resource at gtasks:///<task_id> and includes metadata like title, status, due date, notes, and other fields. You can leverage these tools via a client app or scripts to perform common task management operations against Google Tasks from the MCP server. For desktop integrations, configure the server in your app by pointing to the Node.js entry file (dist/index.js) and invoking the appropriate tools through the MCP protocol.

Prerequisites:

• Node.js and npm installed on your system
• Access to the repository containing the gtasks MCP server (or a clone of it)

Install and build:

1. Install dependencies npm install

2. Build or prepare the distribution bundle (choose one):

   • Build once: npm run build
   • Watch for changes during development: npm run watch

3. Run or use via MCP integration:

   • If running directly: npm run start
   • If using through Smithery or an MCP client, ensure the entry path to the built server is correctly configured (see Dist/index.js path in the mcp_config example).

4. Authenticate with Google Tasks as described in the README (setup OAuth and save credentials in the project root).

5. Optional: Install via Smithery for claude or other clients as described in the README: npx -y @smithery/cli install @zcaceres/gtasks --client claude

Environment and configuration tips:

• Ensure you have enabled the Google Tasks API and configured OAuth credentials as described in the Getting started section of the README.
• When deploying, point the MCP client to the absolute path of the built index file (for example, /Users/you/project/dist/index.js) as shown in the desktop app integration example.
• The authentication flow saves credentials in the repository root; guard this file and consider adding it to your .gitignore.
• If using npm run build, ensure the output path matches what your deployment expects (dist/index.js by default).
• For production deployments, consider setting up environment variables for Google API credentials and token storage location if supported by your environment.