Agentic Backlog MCP Server
Related Servers
Alternatives to Agentic Backlog MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve project briefings, reserve and track tasks, and record checkpoints, passages, messages, and durable context so another AI can resume work using local SQLite-backed project memory.10,848 npmMIT
- AlicenseBqualityBmaintenanceEnables coding agents to discover projects, inspect existing work, atomically claim tasks, record progress, and complete verified work through a task-tracking HTTP API, with version checks, claim coordination, and idempotent retries.271MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage tasks on a local-first board via MCP, exposing task creation, updates, and queries through a thin adapter over the REST service.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.-
- AlicenseNot gradedqualityCmaintenanceA self-hosted backlog tracker with priority scoring and an MCP server, enabling AI agents to autonomously pull, work on, and update tasks via JSON-RPC tools.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.-
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.