SheetMaster Todo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHEETMASTER_API_KEY | Yes | Your SheetMaster Todo API key. Required to authenticate with the SheetMaster Todo Google Apps Script API. | |
| SHEETMASTER_TIMEOUT_MS | No | Optional timeout in milliseconds for calls to Google Apps Script. For example, 240000 (four minutes). |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_boardsB | List all Todo boards available to the authenticated user. |
| get_boardB | Get a board with its columns, tasks, members, and labels. |
| create_taskC | Create a task in a specific board column. |
| update_taskC | Update one or more fields of an existing task. |
| move_taskC | Move a task to another column. Approval may be required. |
| delete_taskC | Permanently delete a task. |
| create_subtaskC | Create a subtask under a task. |
| update_subtaskB | Update a subtask title or completion state. |
| delete_subtaskB | Permanently delete a subtask. |
| create_labelC | Create a label on a board. |
| add_task_labelC | Attach a label to a task. |
| remove_task_labelC | Remove a label from a task. |
| add_assigneeC | Assign a user to a task. |
| remove_assigneeC | Unassign a user from a task. |
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 14 tools
Each tool targets a distinct resource and action: boards, tasks, subtasks, labels, and assignees. The only potential confusion is get_boards versus get_board, but the plural/singular distinction and descriptions clearly separate list-all from fetch-one.
All tools follow a clean snake_case verb_noun pattern (get_, create_, update_, move_, delete_, add_, remove_). The use of add/remove for label and assignee operations is semantically appropriate and consistent with the pattern.
With 14 tools, the set covers a complete task-management workflow without bloat. Each tool maps to a meaningful operation, and the count is well within the ideal 3-15 range.
The tool surface covers full CRUD for tasks and subtasks, plus label and assignee management. The main gaps are board lifecycle operations like create/delete board and label deletion/update, but these may be intentionally managed outside this MCP.