MCP Backlog Server
Related Servers
Alternatives to MCP Backlog Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-native task management using plain markdown files to create, update, query, and organize Epics, Stories, Tasks, and Milestones without requiring a database.-
- AlicenseNot gradedqualityBmaintenanceEnables managing work entries, statuses, cycles, and free-form notes between meetings, with tools for creating, updating, deleting, and presenting meeting markdown summaries.26 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to file and track issues, plan epics with steps, comment as they work, and hand decisions back to the user through a local Markdown- and YAML-backed issue tracker.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to manage a filesystem-based issue tracker through typed MCP tools such as list_tasks, create_task, change_task_status, log_work, and get_sprint, instead of shelling out to a CLI. Tasks and sprints are plain folders of Markdown files, so agents can create, claim, comment on, and move work by topic without any database or server state.20MIT
- AlicenseNot gradedqualityDmaintenanceAutomatically generates structured agile backlogs including epics, features, and user stories from natural language descriptions within AI-powered IDEs. It streamlines project management by creating AI-optimized markdown files and directory structures to guide step-by-step implementation.21 npm3MIT
- AlicenseBqualityBmaintenanceEnables managing a minimal task backlog with operations to create, list, update, and retrieve tasks with different statuses (open, in progress, blocked, done, cancelled). Tasks are stored in a local JSON file with atomic writes.2847 npm5MIT
TDQS
Scored across 7 tools
Tools are mostly distinct, but 'done' and 'ticket-done' could confuse an agent as both mark items complete; similarly 'read' vs 'ticket-read' and 'write' vs 'ticket-write' are pairs with overlapping purposes, though descriptions clarify the backlog vs ticket context.
Naming is inconsistent: plain verbs (done, prune, read, write) and noun-verb with hyphen (ticket-done, ticket-read, ticket-write) mix styles. The verb placement also varies (verb-first vs noun-first).
Seven tools is a reasonable number for managing backlog items and tickets, covering necessary operations without excess or deficiency.
The tool set covers core CRUD-like operations for both backlog items and tickets, including creation, reading, updating, completing, and pruning. Minor gaps include lack of explicit delete for backlog items or tickets (beyond pruning), but these are not severe.