godspeed-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODSPEED_TOKEN | Yes | Your Godspeed API token | |
| GODSPEED_EMPTY_LIST_ID | No | ID of an empty list to use as a template for creating new task lists |
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 |
|---|---|
| listTasksD | – |
| getTaskD | – |
| createTaskD | – |
| updateTaskD | – |
| deleteTaskD | – |
| completeTaskD | – |
| uncompleteTaskD | – |
| getTaskListsD | – |
| duplicateListD | – |
| bulkCreateTaskD | – |
| createTaskListD | – |
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 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools target specific actions on tasks or task lists (e.g., createTask vs. updateTask, getTask vs. listTasks, completeTask vs. uncompleteTask), making it easy for an agent to select the correct one.
Tool names follow a consistent verb_noun pattern throughout, using camelCase uniformly. All names are descriptive and predictable (e.g., createTask, deleteTask, getTaskLists), with no deviations in style or convention.
With 11 tools, the count is well-scoped for a task management domain. Each tool earns its place by covering essential CRUD and lifecycle operations for tasks and task lists, avoiding bloat or thin coverage.
The tool set provides complete CRUD/lifecycle coverage for the task management domain. It includes creation, retrieval, updating, deletion, listing, and state management (complete/uncomplete) for both tasks and task lists, with no obvious gaps or dead ends.