Google Tasks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google Cloud OAuth Client ID | |
| GOOGLE_REDIRECT_URI | No | The OAuth redirect URI | http://localhost:3000/oauth2callback |
| GOOGLE_CLIENT_SECRET | Yes | Your Google Cloud OAuth Client Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticateB | Get URL to authenticate with Google Tasks |
| set-auth-codeC | Set the authentication code received from Google OAuth flow |
| list-tasklistsB | List all task lists |
| get-tasklistC | Get a task list by ID |
| create-tasklistC | Create a new task list |
| update-tasklistC | Update an existing task list |
| delete-tasklistC | Delete a task list |
| list-tasksC | List all tasks in a task list |
| get-taskC | Get a specific task by ID |
| create-taskC | Create a new task in a task list |
| update-taskC | Update an existing task |
| delete-taskC | Delete a task |
| complete-taskC | Mark a task as completed |
| move-taskC | Move a task to another position |
| clear-completed-tasksC | Clear all completed tasks from a task list |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets specific resources (tasks or tasklists) and actions (create, get, list, update, delete, complete, clear, move), making it easy for an agent to select the right tool. The separation between task operations and tasklist operations is particularly clear.
The naming follows a perfectly consistent verb-noun pattern throughout all 15 tools. Every tool uses snake_case with clear action verbs (create, get, list, update, delete, etc.) followed by the resource name (task, tasklist), and multi-word resources use hyphens consistently (e.g., clear-completed-tasks).
With 15 tools, this server is well-scoped for managing Google Tasks. Each tool earns its place by covering essential CRUD operations for both tasks and tasklists, plus additional workflow actions like moving tasks and clearing completed ones. The count is appropriate for the domain without being overwhelming.
The tool surface provides complete coverage for the Google Tasks domain. It includes full CRUD operations for both tasks and tasklists, plus lifecycle actions like completing tasks, moving tasks, and clearing completed tasks. Authentication tools are also included, ensuring no dead ends for agents.