Skip to content
BranchesTags
 
 

Repository files navigation

Google Tasks MCP Server

A Model Context Protocol (MCP) server that brings your Google Tasks into Claude and other MCP-compatible clients. Manage your tasks, task lists, and to-dos through natural conversation.

🔒 Privacy First: This repository is public to demonstrate transparency. The code shows that no personal information is logged or stored maliciously. All sensitive data (tokens) is encrypted at rest and automatically redacted from logs. You can review the entire codebase to verify this commitment to privacy.

⚠️ Disclaimer: This server is provided as-is without any guarantees or warranties. While every effort has been made to ensure security and privacy, no guarantees are made about availability, data integrity, or security. Use at your own risk. For production use cases, consider self-hosting your own instance.

Table of Contents

What Can You Do With This?

This MCP server gives Claude access to your Google Tasks data, allowing you to:

  • Manage task lists: Create, read, update, and delete task lists
  • Manage tasks: Create, read, update, delete, and move tasks
  • Organize tasks: Create subtasks, set due dates, add notes
  • Mark completion: Mark tasks as complete or incomplete
  • Batch operations: Clear all completed tasks from a list
  • Query tasks: Filter tasks by completion status, due date, and more
  • Natural language: Interact with your tasks through conversation with Claude

All through natural conversation with Claude or any other MCP-compatible client.

For End Users: Using the Hosted Server

If you just want to use this MCP server with Claude Desktop without hosting anything yourself, follow these steps:

Prerequisites

  1. A Google Account with Google Tasks
  2. Claude Desktop or any other MCP-compatible client installed on your computer

Setup Instructions

Step 1: Add Connector in Claude Desktop

  1. Open Claude Desktop
  2. Go to Settings (gear icon in the bottom-left corner)
  3. Navigate to the Connectors tab
  4. Click Add Custom Connector
  5. Fill in the following details:
    • Name: Google Tasks (or any name you prefer)
    • Remote MCP server URL: https://your-deployed-domain.com/mcp
  6. Click Add

Step 2: Connect and Authorize

  1. In the Connectors settings, find the Google Tasks connector you just added
  2. Click Connect next to the connector
  3. Your web browser will open with the Google authorization page
  4. Log in to your Google account
  5. Review and approve the permissions requested
  6. You'll be redirected back and the connection will be complete

After authorization, Claude will have access to your Google Tasks!

Available Tools

Once connected, Claude can use these tools to access your data:

Task Lists Management

  • list_task_lists - Returns all the authenticated user's task lists
  • get_task_list - Returns a specific task list
  • insert_task_list - Creates a new task list
  • update_task_list - Updates a task list (full update)
  • patch_task_list - Updates a task list (partial update)
  • delete_task_list - Deletes a task list

Tasks Management

  • list_tasks - Returns all tasks in a task list
  • get_task - Returns a specific task
  • insert_task - Creates a new task
  • update_task - Updates a task (full update)
  • patch_task - Updates a task (partial update)
  • delete_task - Deletes a task
  • clear_completed_tasks - Clears all completed tasks from a list
  • move_task - Moves a task to a different position or parent

Example Conversations

Try asking Claude:

  • "What task lists do I have?"
  • "Show me all tasks in my Work list"
  • "Create a new task list called 'Personal Projects'"
  • "Add a task 'Review Q4 reports' to my Work list with due date next Friday"
  • "Mark the task 'Buy groceries' as completed"
  • "Move 'Write proposal' task to be a subtask of 'Client project'"
  • "Clear all completed tasks from my Shopping list"
  • "What tasks are due this week?"

Privacy & Security

  • Encrypted tokens: All authentication tokens are encrypted using AES-256-GCM before storage
  • No logging of personal data: The code is public - you can verify that no sensitive information is logged
  • Automatic redaction: All user IDs, tokens, and credentials are automatically redacted from system logs
  • OAuth 2.0: Industry-standard secure authentication with Google
  • You're in control: Revoke access anytime from your Google account settings

For Developers: Self-Hosting

Want to run your own instance? Here's how to deploy this MCP server yourself.

Prerequisites

  1. Node.js 18+ and npm installed
  2. Deno CLI installed for deployment
  3. A Google Cloud Platform account

Step 1: Create Google Cloud Project

  1. Go to Google Cloud Console
  2. Create a new project or select an existing one
  3. Enable the Google Tasks API:
    • Go to APIs & Services → Library
    • Search for "Google Tasks API"
    • Click Enable
  4. Create OAuth 2.0 credentials:
    • Go to APIs & Services → Credentials
    • Click Create Credentials → OAuth client ID
    • Choose Web application
    • Add authorized redirect URIs: https://your-domain.com/callback
    • Note your Client ID and Client Secret
  5. Configure OAuth consent screen:
    • Go to APIs & Services → OAuth consent screen
    • Add required scopes: https://www.googleapis.com/auth/tasks

Step 2: Clone and Setup

# Clone the repository
git clone https://github.com/akutishevsky/google-tasks-mcp.git
cd google-tasks-mcp

# Install dependencies
npm install

# Generate encryption secret
npm run generate-secret
# Copy the output - you'll need it for environment variables

Step 3: Local Development

Note: Google requires a publicly accessible URL for OAuth callbacks. For local development, use a tunneling service (like ngrok) to expose your local server or deploy to a staging environment for testing.

# Copy environment template
cp .env.example .env

# Edit .env with your values
# GOOGLE_CLIENT_ID=your_client_id
# GOOGLE_CLIENT_SECRET=your_client_secret
# GOOGLE_REDIRECT_URI=https://your-tunnel-url.com/callback
# ENCRYPTION_SECRET=paste_generated_secret_here
# PORT=3000

# Build the project
npm run build

# Run with Deno
deno task dev

Make sure your redirect URI in the .env file matches the publicly accessible URL pointing to your local server.

Step 4: Deploy to Production

Deploy to Deno Deploy

  1. Install Deno Deploy CLI:
deno install -A --unstable https://deno.land/x/deploy/deployctl.ts
  1. Deploy the project:
# Build first
npm run build

# Deploy to Deno Deploy
deployctl deploy --project=google-tasks-mcp build/index.js
  1. Set environment variables in Deno Deploy dashboard:
    • Go to your project settings
    • Add all required environment variables
    • Restart the deployment

Step 5: Update Google OAuth Settings

Go back to your Google Cloud Console OAuth client and update the redirect URI to match your deployed URL: https://your-domain.com/callback

Step 6: Configure Your MCP Client

For Claude Desktop:

  1. Open Claude Desktop
  2. Go to Settings → Connectors tab
  3. Click Add Custom Connector
  4. Fill in the following details:
    • Name: Google Tasks (or any name you prefer)
    • Remote MCP server URL: https://your-domain.com/mcp
  5. Click Add
  6. Click Connect next to the connector to authorize

For Other MCP Clients:

Configure your MCP client with the following connection details:

  • Server URL: https://your-domain.com
  • Transport: Server-Sent Events (SSE)
  • Endpoint: /mcp
  • Authentication: OAuth 2.0
  • Discovery URL: /.well-known/oauth-authorization-server

Environment Variables Reference

Variable Required Description
GOOGLE_CLIENT_ID Yes Your Google OAuth client ID
GOOGLE_CLIENT_SECRET Yes Your Google OAuth client secret
GOOGLE_REDIRECT_URI Yes OAuth callback URL (must match Google Cloud Console settings)
ENCRYPTION_SECRET Yes 32+ character secret for token encryption (generate with npm run generate-secret)
PORT No Server port (default: 3000)
LOG_LEVEL No Logging level: trace, debug, info, warn, error (default: info)
ALLOWED_ORIGINS No Comma-separated list of allowed CORS origins for browser clients

Development Commands

npm run build            # Compile TypeScript to JavaScript
npm run dev              # Watch mode - recompile on changes
npm run generate-secret  # Generate encryption secret for ENCRYPTION_SECRET env variable

Project Structure

src/
├── auth/              # OAuth 2.0 authentication & token storage
├── server/            # Hono app, MCP endpoints, middleware
├── tools/             # MCP tools for Google Tasks API (tasklists, tasks)
├── transport/         # Custom SSE transport for MCP
├── google/            # Google Tasks API client
├── utils/             # Logger and encryption utilities
└── index.ts           # Main entry point

Security Features

Token Encryption

All Google access and refresh tokens are encrypted at rest using AES-256-GCM:

  • Algorithm: AES-256-GCM (authenticated encryption)
  • Key Derivation: PBKDF2 with 100,000 iterations
  • Defense in Depth: Even if the database is compromised, tokens remain protected

Important: Keep your ENCRYPTION_SECRET:

  • At least 32 characters long
  • Randomly generated (use npm run generate-secret)
  • Secure and never committed to version control
  • Consistent across server restarts

Privacy-Safe Logging

The custom logger automatically redacts all sensitive information:

  • ✅ Operational events and errors logged
  • ❌ No tokens, credentials, or auth codes
  • ❌ No user IDs or personal information
  • ❌ No API request/response payloads with sensitive data

You can review the logging implementation in src/utils/logger.ts.

Contributing

This is a personal project, but contributions are welcome! Please:

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Submit a pull request

License

MIT License - see LICENSE file for details.

Support

Acknowledgments

Built with:

About

MCP server for Google Tasks API integration

gtasks-mcp.com

Resources

Readme
License
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages