telos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELOS_DIR | No | Directory where task files are stored | ~/.telos |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| task_createC | Create a new task for tracking work |
| task_updateB | Update an existing task's status, dependencies, or details |
| task_getA | Get full details of a task by ID |
| task_listA | List all tasks (summary view: id, subject, status, owner, blockedBy) |
| task_deleteA | Delete a task by ID (removes the folder) |
| task_moveC | Move a task to a different project (or to global tasks) |
| task_create_bulkC | Create multiple tasks at once |
| task_treeB | Get task hierarchy tree with all descendants |
| project_createC | Create a new project for organizing tasks |
| project_updateD | Update project |
| project_listC | List all projects with optional filtering |
| project_getB | Get project information by key |
| project_archiveA | Archive a project (moves to archive/year/) |
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 13 tools
Each tool targets a distinct action on either projects or tasks, with no overlapping purposes. For example, project_create and task_create are clearly differentiated by resource type.
All tool names follow a consistent verb_noun pattern: project_<verb> and task_<verb>, making it easy to predict functionality from the name.
With 13 tools, the count is appropriate for a project and task management domain. It covers core operations without being overwhelming, though slightly on the higher side.
The set covers CRUD for tasks fully (create, get, list, update, delete) and for projects (create, get, list, update, archive). Missing an explicit project delete, but archive serves as a soft delete. A project tree might be useful but is not essential.