Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_TASKS_MCP_HOMENoOverride the directory where the Tasks-only token is stored (default is ~/.config/google-tasks-mcp).

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_task_listsA

List the user's Google Tasks lists (id and title).

tasks_contextB

Snapshot of all open tasks across every list for use as conversation context: overdue, due within days_ahead days, without a due date, later, and the open tasks Claude created earlier (candidates for automatic completion).

list_tasksA

List tasks in one list. tasklist is a list id or title (default list if omitted). query filters by text in title/notes; due_before (YYYY-MM-DD) keeps tasks due on or before that date.

create_taskA

Create a task (marked as created by Claude). due is YYYY-MM-DD; tasklist is a list id or title; parent_task_id makes it a subtask.

update_taskA

Change a task's title, notes or due date (YYYY-MM-DD; empty string clears it). Only fields that are passed are changed.

complete_taskA

Mark a task completed. Without user_requested=true only tasks created by Claude can be completed; set it only when the user explicitly asked to complete this task.

reopen_taskC

Mark a completed task as not done again (same ownership rule as complete_task).

Prompts

Interactive templates invoked by user choice

NameDescription
with_my_tasksStart a conversation with the user's open Google Tasks loaded as context.

Resources

Contextual data attached and managed by the client

NameDescription
context_resourceOpen tasks for the next 7 days, as JSON.

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct actions (create, update, complete, reopen), and list_task_lists is unique. The only potential overlap is list_tasks versus tasks_context, since both return task data, but their descriptions clearly distinguish single-list filtered listing from a cross-list contextual snapshot.

Naming Consistency4/5

Six of seven tools follow a clear verb_noun pattern (create_task, update_task, complete_task, reopen_task, list_task_lists, list_tasks). The outlier tasks_context is a noun phrase rather than an action, which is a minor inconsistency but remains understandable.

Tool Count5/5

Seven tools is well-scoped for a Google Tasks integration, covering task creation, modification, completion lifecycle, and listing. No tool feels redundant or extraneous.

Completeness3/5

Core task lifecycle operations are covered, but there is no delete_task or get_task operation, and list management only supports listing rather than creating, renaming, or deleting task lists. These are notable gaps for full Google Tasks coverage, though common assistant workflows can mostly work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues