Skip to main content
Glama
asisrasyid

SheetMaster Todo MCP

by asisrasyid
README.md
# SheetMaster Todo MCP

Codex plugin for the SheetMaster Todo Google Apps Script API.

## Authentication

Set the API key in the environment before starting Codex:

```bash
export SHEETMASTER_API_KEY="your_new_key"
```

Do not commit the key or put it in `.mcp.json`.

## Deploy to Vercel

1. Import this repository into Vercel.
2. Add `SHEETMASTER_API_KEY` in Project Settings → Environment Variables.
   Optionally add `SHEETMASTER_TIMEOUT_MS=240000` (four minutes).
3. Deploy and use `https://YOUR_PROJECT.vercel.app/api/mcp` as the remote MCP URL.
4. Verify `/api/health` returns a successful health response.

The Vercel MCP function allows up to five minutes. Calls to Google Apps Script
wait up to four minutes, leaving time for MCP to return a controlled response.
Write operations are never retried automatically, preventing duplicate tasks.

## Tools

- `get_boards`, `get_board`
- `create_task`, `update_task`, `move_task`, `delete_task`
- `create_subtask`, `update_subtask`, `delete_subtask`
- `create_label`, `add_task_label`, `remove_task_label`
- `add_assignee`, `remove_assignee`

TDQS

B3.3/5.0

Scored across 14 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues