aiboard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --root | No | Override board discovery; specifies the board root path. | |
| --author | No | Sets the default author for worklog entries recorded by the MCP server. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| board_summaryA | Board name, task counts per status, and every sprint with its progress. |
| list_tasksA | List tasks in queue order: the top of the queue first, so take work from the start of the list. Metadata only; use get_task for the brief and worklog. Each task carries blocked_by, blocked (true while a blocker is open) and blockers. |
| get_taskA | Full task: metadata, brief (Markdown), worklog entries and comments (discussion with humans; check it for answers and review notes). |
| create_taskB | Create a task. Returns the new task; its id is allocated automatically. |
| change_task_statusA | Move a task to another status (moves its folder, appends a worklog entry). Refuses to start a task that is blocked by open tasks unless force=true. |
| block_taskB | Record that a task is blocked by other tasks (Jira: 'is blocked by'). |
| unblock_taskC | Remove blockers from a task. |
| rank_taskA | Reorder the queue (Jira: Rank). Give exactly one of top, bottom, before or after. Lists and board columns sort by rank, and agents take work from the top. |
| start_taskA | Claim a backlog task and move it to in-progress in ONE atomic step (Jira: Start progress). Fails if the task is not in backlog, is assigned to someone else, or is blocked. Use this instead of assign_task + change_task_status when several agents share a board. |
| assign_taskA | Set or clear the assignee of a task. Refuses to take a task from someone else unless force=true. |
| log_workA | Append an entry to the task's worklog (Markdown). Use it for progress, decisions, blockers. |
| comment_taskA | Add to the task's discussion, separate from the worklog: ask a human a question, leave a review note, or answer one. Humans see comments on the web board. |
| edit_taskA | Change task metadata. Only the fields given are changed; sprint='' detaches. |
| list_sprintsC | List sprints with progress. |
| get_sprintC | Sprint details, progress, and its tasks. |
| create_sprintC | Create a sprint. |
| change_sprint_statusC | Move a sprint to another status. |
| sprint_add_tasksC | Attach tasks to a sprint. |
| sprint_remove_tasksC | Detach tasks from a sprint. |
| check_boardA | Validate consistency between tasks and sprints; fix=true repairs stale sprint checklists. |
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 20 tools
Most tools target clearly distinct resources or actions (comments vs worklog, tasks vs sprints, ranking vs status changes). The main overlap is among start_task, assign_task, and change_task_status, but the descriptions explicitly clarify when to use start_task over the other two.
The dominant pattern is verb_noun (create_task, get_sprint, block_task), but there are noticeable deviations like sprint_add_tasks, sprint_remove_tasks, and board_summary. These remain readable but break the otherwise predictable convention.
At 20 tools the surface is on the heavy side for a task-board server, though most tools correspond to distinct operations. It borders on over-scoped, especially with separate sprint membership and status tools.
Task lifecycle is well covered: create, list, get, edit, status, assignment, blocking, ranking, comments, and worklogs, plus sprint creation and membership management. Minor gaps remain around deleting tasks or sprints and editing sprint metadata, but core workflows are supported.