bulkCreateTaskLABSCO SUMMARY
The scheduling detail a calendar-style task list needs survives the round trip.
createTask and updateTask carry the fields that usually get lost when a task is filed through an API — starts_at and due_at alongside timeless_starts_at and timeless_due_at for tasks with no clock time, duration_minutes, location, and labels applied by name rather than by id if that is all you have. updateTask also separates add_label_ids and add_label_names from their remove counterparts, so a label edit does not overwrite the rest of the set. What the tool set does not carry is any description text of its own; every capability above is read from the tool names and their parameters.
What it is
A task-management front end for a Godspeed account, 11 tools covering tasks and the lists they sit in.
What you get
- Task creation with the scheduling fields attached: createTask takes a title, notes, list, start and due times, a timeless variant of each, duration in minutes, labels by id or name, a location and free-form metadata; bulkCreateTask takes an array of them in one call.
- Updates that address labels individually: updateTask adds or removes labels by id or name, moves start and due times, sets duration, notes, completion and cleared state, and can snooze a task until a given time.
- Completion handled in both directions: completeTask, uncompleteTask and deleteTask, with getTask for a single task by id.
- Reading the list back with filters: listTasks narrows by list, by status and by an updated_after / updated_before window.
- List-level operations: getTaskLists returns the account's lists, createTaskList makes a new one, duplicateList copies an existing list under a new name.
Requirements
A Godspeed account and the access token the server reads from the environment. Tasks and lists are addressed by id, so getTaskLists comes before anything that takes a list_id.
Setup effort
One command plus a key — npx -y godspeed-mcp, then supply credentials
USE CASES
Getting a meeting's action items into the list before they are forgotten
Pick the list they belong in, then file them in one call with owners' due times and durations attached rather than one round trip per item.
Clearing what is done and rescheduling what slipped
Read back the tasks touched since the last pass, close the finished ones, and move or snooze the rest instead of deleting them.
Starting the next cycle from the list that just closed
Copy the finished list under a new name to keep its structure, or start a clean one when the shape has changed.
11 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
completeTaskcreateTaskcreateTaskListdeleteTaskduplicateListgetTaskgetTaskListslistTasksuncompleteTaskupdateTaskBEFORE YOU INSTALL
What to know first
Tools you get
11 tools when we connected. The token can be set as GODSPEED_TOKEN or passed on the command line as --token=…; the Windows block uses the flag.
Requires
- npx on PATH
- GODSPEED_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 11 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx -y godspeed-mcpMCP Clients
Cursor — macOS, Linux
{
"mcpServers": {
"godspeed-mcp": {
"command": "npx",
"args": [
"godspeed-mcp"
],
"env": {
"GODSPEED_TOKEN": "<YOUR_GODSPEED_TOKEN>",
"GODSPEED_EMPTY_LIST_ID": "<YOUR_GODSPEED_EMPTY_LIST_ID>"
}
}
}
}GODSPEED_EMPTY_LIST_ID is optional: the id of an empty list the server copies as a template when it creates a new list. Delete that line if you don't use one; you then give the empty list id each time you create a list.
Cursor — Windows
npm install -g godspeed-mcpThen create %USERPROFILE%\.cursor\mcp.json with:
{
"mcpServers": {
"godspeed-mcp": {
"command": "cmd",
"args": [
"/c",
"godspeed-mcp",
"--token=<YOUR_GODSPEED_TOKEN>",
"--empty-list-id=<YOUR_GODSPEED_EMPTY_LIST_ID>"
]
}
}
}<YOUR_GODSPEED_TOKEN> is your Godspeed API token. --empty-list-id is optional. Drop it if you do not use a template list.