taskboi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKBOI_API_KEY | Yes | Your Taskboi API key | |
| TASKBOI_API_BASE_URL | Yes | Base URL for the Taskboi API, e.g., https://api.example.invalid/functions/v1/mcp-api |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all projects in your Taskboi workspace |
| get_inboxA | Get the default Inbox project |
| get_projectA | Get details of a specific project |
| create_projectC | Create a new project |
| update_projectC | Update an existing project |
| delete_projectA | Delete a project (cannot delete Inbox) |
| list_tasksA | List all tasks, optionally filtered by project |
| get_taskB | Get details of a specific task |
| get_today_tasksA | Get all tasks due today (including overdue recurring tasks) |
| get_upcoming_tasksB | Get all upcoming tasks with due dates |
| get_subtasksB | Get all subtasks of a parent task |
| create_taskC | Create a new task |
| update_taskA | Update an existing task. Omitted fields are left unchanged; to remove the due date, pass clearDueDate: true. |
| complete_taskA | Mark a task as complete. For recurring tasks, this also creates the next occurrence. |
| uncomplete_taskB | Mark a completed task as incomplete |
| delete_taskC | Delete 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 16 tools
Each tool targets a distinct action on a specific resource type (projects vs tasks), with specialized query tools (today, upcoming, subtasks) clearly differentiated by their purpose. The only potential overlap, get_inbox vs get_project, is resolved by get_inbox being a convenience for the default project. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern in snake_case, using verbs like list, get, create, update, delete, complete, and uncomplete. Even the specialized queries get_today_tasks and get_subtasks adhere to the same pattern, making the set predictable and easy to navigate.
With 16 tools, the set is slightly above the typical 3-15 range but still well-scoped for a task management server covering both projects and tasks. Each tool earns its place, covering CRUD plus specialized list and task-state operations. The count feels appropriate, not bloated.
The tool surface provides complete CRUD coverage for both projects and tasks, along with essential task lifecycle operations like complete and uncomplete. Specialized queries for today, upcoming, and subtasks fill common workflow needs. There are no obvious dead ends or missing critical operations for the stated domain.