Agentic Backlog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKLOG_API_BASE_URL | Yes | Base URL of the backlog API | http://127.0.0.1:38117/api |
| BACKLOG_API_FAIL_FAST_MS | No | Fail-fast window in milliseconds | 15000 |
| BACKLOG_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds | 1800 |
| BACKLOG_API_FAILURE_THRESHOLD | No | Number of failures to trigger fail-fast | 1 |
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 |
|---|---|
| backlog.healthA | Checks backlog API health and connectivity before mutations. |
| backlog.versionA | Returns API version and protocol compatibility information. |
| backlog.identify_projectB | Detects git context and resolves/creates a project in the running backlog API (Docker app source of truth). |
| backlog.list_projectsC | Lists projects from the running backlog API. |
| backlog.get_projectB | Returns project metadata and board summary from the running backlog API. |
| backlog.get_kanban_urlC | Returns a browser URL for visual kanban from the running backlog API. |
| backlog.create_taskC | Creates a task through the running backlog API. |
| backlog.list_tasksC | Lists project tasks from the running backlog API. |
| backlog.get_taskA | Returns a single task by id from the running backlog API. |
| backlog.find_tasks_by_titleC | Finds tasks in a project by title keywords using backlog API task list. |
| backlog.update_taskC | Updates task fields through the running backlog API. |
| backlog.update_task_by_titleC | Finds a task by title query and updates it through the backlog API. |
| backlog.delete_taskC | Deletes a task through the running backlog API. |
| backlog.update_task_statusC | Moves a task between states through the running backlog API. |
| backlog.add_task_noteC | Adds a task note through the running backlog API. |
| backlog.plan_from_contextC | Delegates planning to running backlog API planner endpoint. |
| backlog.get_focusB | Returns what matters now for a project: top priority, blocked, stale, and in progress tasks. |
| backlog.claim_taskB | Claims a task with TTL for an agent/session to avoid multi-agent collisions. |
| backlog.release_taskC | Releases an active task claim for the given agent/session. |
| backlog.restore_taskC | Restores a soft-deleted task within restore window. |
| backlog.get_boardC | Returns board grouped snapshot from the running backlog API. |
| backlog.get_console_tableC | Returns a console-table style board snapshot from backlog API. |
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 22 tools
Many tools are distinct, but there are several overlapping boundaries: get_board and get_console_table both return board snapshots, update_task/update_task_by_title/update_task_status all mutate tasks, and get_focus/list_tasks overlap as list-like views. Descriptions help, but an agent could easily pick the wrong one for state changes or snapshot retrieval.
Names consistently use the backlog. prefix with snake_case verb_noun construction (list_tasks, create_task, update_task). Minor deviations are bare nouns health and version and the looser get_/list_ distinction, but the overall pattern is predictable and readable.
22 tools is on the heavy side and sits in the 16-25 borderline range. Many could be consolidated (board formats, update variants, health/version), though the broad project/task/planning/claim domain explains some of the volume.
The surface covers task CRUD well, including restore, status transitions, notes, claims, board snapshots, focus, and planning. Minor gaps exist such as no project update/delete and limited search beyond title keywords, but core agent workflows do not hit dead ends.