task-mcp-node
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | Opretter en ny task i tasks.json. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_tasks | Hjælper med at prioritere tasks ud fra status og priority. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_tasks | Returnerer alle tasks fra den lokale tasks.json-fil. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity. The tool's purpose is clearly stated.
The single tool uses a clear verb_noun pattern ('add_task'), consistent with best practices.
With only one tool for a task management server, the scope is extremely limited. Task management typically requires multiple operations.
The server provides only a create operation. Missing essential operations like list, read, update, and delete tasks, making it severely incomplete.