Tasks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host address for server mode | 0.0.0.0 |
| PORT | No | Port number for server mode | 8000 |
| TRANSPORT | No | Transport protocol for the server (stdio or streamable-http) | stdio |
| DATABASE_PATH | No | Path to the SQLite database file | ~/.tasks.sqlite3 |
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 |
|---|---|
| tasks_list_toolC | Get a list of tasks. Args: task_limit (int): The maximum number of tasks to return. Default is 10. Returns: list[Task]: A list of tasks. |
| get_task_toolB | Get a task by ID. Args: task_id (int): The ID of the task to retrieve. Returns: Task: The task object if found, otherwise None. |
| add_task_toolB | Add a new task. Args: title (str): The title of the task. description (str): The description of the task. optional value. Returns: Task: The newly created task object. |
| update_task_toolC | Update an existing task. Args: task (Task): The task object containing updated information. Returns: Task: The updated task object. |
| delete_task_toolB | Delete a task by ID. Args: task_id (int): The ID of the task to delete. Returns: None |
| filter_tasks_toolC | Filter tasks by status and title. Args: status (TaskStatus): The status to filter tasks. Optional value. title (str): The title to filter tasks. Optional value. description (str): The description to filter tasks. Optional value. created_at (str): The creation date to filter tasks. Optional value. Returns: list[Task]: A list of tasks matching the specified status and title. |
| get_tasks_statusC | Get the status tasks values. Returns: dict: The status tasks values. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tasks:list | Prompt to list tasks. |
| tasks:get | Prompt to get a task by ID. |
| tasks:add | Prompt to add a new task. |
| tasks:update | Prompt to update an existing task. |
| tasks:delete | Prompt to delete a task by ID. |
| tasks:filter | Prompt to filter tasks by status and title. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes (add, delete, get, update, list, filter, get status), but 'tasks_list_tool' and 'filter_tasks_tool' could cause confusion as both retrieve lists of tasks. The descriptions clarify that one is a simple list with a limit, while the other allows filtering by multiple criteria, but the overlap in functionality might lead to misselection in some contexts.
The naming is mixed with no clear pattern: 'add_task_tool', 'delete_task_tool', 'filter_tasks_tool', 'get_tasks_status', 'get_task_tool', 'tasks_list_tool', 'update_task_tool'. Some use verb_noun_tool (e.g., add_task_tool), others use noun_verb_tool (e.g., tasks_list_tool), and 'get_tasks_status' lacks the '_tool' suffix. This inconsistency reduces predictability but remains readable.
With 7 tools, this is well-scoped for a task management server. Each tool serves a clear purpose in handling tasks, such as CRUD operations, listing, filtering, and retrieving status values. The count is neither too sparse nor bloated, fitting typical use cases effectively.
The tool set provides complete coverage for task management: create (add_task_tool), read (get_task_tool, tasks_list_tool, filter_tasks_tool), update (update_task_tool), delete (delete_task_tool), and additional utility (get_tasks_status). There are no obvious gaps; agents can perform all essential lifecycle operations without dead ends.