home / mcp / google tasks mcp server
This Model Context Protocol (MCP) server provides a bridge between LLMs and Google Tasks, allowing you to manage your task lists and tasks directly through Claude.
Configuration
View docs{
"mcpServers": {
"arpitbatra123-mcp-googletasks": {
"command": "node",
"args": [
"/path/to/google-tasks-mcp/build/index.js"
],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id_here",
"GOOGLE_REDIRECT_URI": "http://localhost:3000/oauth2callback",
"GOOGLE_CLIENT_SECRET": "your_client_secret_here"
}
}
}
}You can manage Google Tasks directly from Claude by using this MCP server as a bridge. It lets you list, create, update, move, and complete task lists and tasks, providing a smooth workflow that integrates your tasks with Claude’s capabilities.
You interact with the Google Tasks MCP Server through your MCP client. Once authenticated, you can perform common operations on task lists and tasks without leaving Claude. Practical use patterns include listing all task lists to pick one, creating a new task in a chosen list, updating task details, reordering tasks, marking tasks as completed, and clearing completed items. The server handles authentication tokens securely and refreshes them automatically, so you can focus on your tasks rather than credential management.
Prerequisites you need before installing the MCP server:
Step by step setup and installation:
Configuration snippet you will use in Claude Desktop to register the MCP server:
{
"mcpServers": {
"google-tasks": {
"command": "node",
"args": ["/path/to/google-tasks-mcp/build/index.js"],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id_here",
"GOOGLE_CLIENT_SECRET": "your_client_secret_here",
"GOOGLE_REDIRECT_URI": "http://localhost:3000/oauth2callback"
}
}
}
}{
"mcpServers": {
"google-tasks": {
"command": "node",
"args": ["/path/to/google-tasks-mcp/build/index.js"],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id_here",
"GOOGLE_CLIENT_SECRET": "your_client_secret_here",
"GOOGLE_REDIRECT_URI": "http://localhost:3000/oauth2callback"
}
}
}
}- Authentication tokens are persisted to disk with restricted permissions for ongoing sessions. Tokens refresh automatically, so you won’t need to re-authenticate after restarts unless you revoke access or delete the credentials file.
- The OAuth redirect URI can be customized via the GOOGLE_REDIRECT_URI environment variable to fit your local or network environment.
- The server includes input validation, HTML sanitization for OAuth callbacks, and graceful shutdown handling to ensure clean resource cleanup on stop signals.
If you encounter authentication failures, verify that GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET are correctly set and that the redirect URI matches what you configured in your Google Cloud Console. Check the credentials file at the default path for consistency and permissions. If the server fails to start, review the startup logs for missing environment variables or incorrect command paths.
List all task lists available in your Google Tasks account.
Retrieve details for a specific task list.
Create a new task list.
Update properties of an existing task list.
Delete a task list.
List all tasks within a specific task list.
Get details about a specific task.
Create a new task within a list.
Update an existing task.
Delete a task.
Mark a task as completed.
Move or reorder a task within or between lists.
Remove all completed tasks from a list.