Agentic Backlog MCP Server
# Agentic Backlog MCP Server
Local-first MCP server for AI backlog management.
This package runs over `stdio` (Node.js) and forwards MCP tool calls to a running backlog API.
## Exposed tools
- `backlog.identify_project`
- `backlog.health`
- `backlog.version`
- `backlog.list_projects`
- `backlog.get_project`
- `backlog.get_kanban_url`
- `backlog.create_task`
- `backlog.list_tasks`
- `backlog.get_task`
- `backlog.find_tasks_by_title`
- `backlog.update_task`
- `backlog.update_task_by_title`
- `backlog.delete_task`
- `backlog.update_task_status`
- `backlog.add_task_note`
- `backlog.plan_from_context`
- `backlog.get_focus`
- `backlog.claim_task`
- `backlog.release_task`
- `backlog.restore_task`
- `backlog.get_board`
- `backlog.get_console_table`
## Requirements
- Node.js 18+
## Environment
```bash
BACKLOG_API_BASE_URL=http://127.0.0.1:38117/api
BACKLOG_REQUEST_TIMEOUT_MS=1800
BACKLOG_API_FAIL_FAST_MS=15000
BACKLOG_API_FAILURE_THRESHOLD=1
```
## Run locally
```bash
npm install
npm run build
npm start
```
For development:
```bash
npm run dev
```
## MCP config example
`.mcp.json` file:
```json
{
"mcp": {
"agentic-backlog": {
"command": "npx",
"args": ["-y", "@hakenshi/agentic-backlog-mcp-server"],
"env": {
"BACKLOG_API_BASE_URL": "http://127.0.0.1:38117/api"
}
}
}
}
```
## Notes
- This server uses `stdio` transport only.
- Do not use `console.log` in MCP stdio mode (stdout breaks JSON-RPC). Logs must go to `stderr`.
- `backlog.delete_task` requires explicit `confirm: "DELETE"`.
- `backlog.plan_from_context` is preview-only by default. Set `apply: true` to persist changes.
- API resilience is fail-fast: when repeated timeout/5xx errors happen, the server opens a short circuit window and returns immediate 503 errors so agent runs do not stall.
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.