Task Board MCP Server
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
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tasksA | Find tasks whose title or tags contain the query. Use this before creating a task to avoid duplicates. Returns a note describing what was searched, including when nothing matched. |
| create_taskA | Add a task to the board. Search first — this does not detect duplicates. |
| set_statusA | Move a task to one of: todo, doing, done. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| standup | Summarise the board the way you would report it in a standup. |
| triage | Propose what to work on next, with reasoning. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| board | Every task with its status and tags. Read this for current state. |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: searching, creating, and updating status. No overlap or ambiguity exists between them.
All tool names follow a consistent verb_noun pattern with lower snake_case: search_tasks, create_task, set_status. This makes the API predictable and easy to navigate.
With only three tools, the server is tightly scoped to its purpose as a minimal task board. Each tool earns its place and there is no bloat.
The core lifecycle of creating, searching, and updating task status is covered. Missing delete and full task editing are minor gaps, but the essential workflow is functional.