TinyTasks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The environment mode, typically set to 'production'. | |
| WEB_MODE | No | Set to 'true' to run the server in web/API mode instead of the default local MCP mode. |
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 |
|---|---|
| get_api_statusB | Obtiene el estado actual de la API de TinyTasks |
| get_tasks_statsB | Obtiene estadísticas de las tareas: total, completadas, pendientes |
| list_tasksC | Lista todas las tareas con filtro opcional por estado |
| get_taskC | Obtiene los detalles de una tarea específica |
| create_taskC | Crea una nueva tarea |
| update_taskC | Actualiza una tarea existente |
| toggle_taskC | Alterna el estado de completación de una tarea |
| delete_taskC | Elimina permanentemente una tarea |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: create, delete, get, list, update, toggle, and API status/statistics tools all target specific actions on tasks or system status. An agent can easily differentiate between them based on their descriptions.
All tools follow a consistent verb_noun naming pattern (e.g., create_task, delete_task, get_task) with clear, descriptive verbs. There are no deviations in style or convention across the set.
With 8 tools, this server is well-scoped for task management, covering core CRUD operations (create, get, update, delete), listing, toggling completion, and supplementary functions like stats and API status. Each tool earns its place without bloat.
The toolset provides complete coverage for task management: full CRUD (create, get, update, delete), lifecycle handling (toggle for completion), listing with filters, statistics, and system status. There are no obvious gaps that would hinder an agent's workflow.