Skip to main content
Glama
backloghq

backlog

by backloghq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to backlog

No user-submitted related servers found.

    Related Servers

    • Vibe Board VE

      HuntsDesk
      A
      license
      A
      quality
      B
      maintenance
      Persistent memory and task board for Claude Code. 14 tools spanning projects, tasks, sessions, and activity logs — backed by Firestore, runs on the free tier. Handoff notes survive context compaction; the next session reads the last handoff and picks up where you stopped.
      14
      MIT

    • ProPlan

      King-Proplan
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for project planning inside Claude. It tracks progress, knows your codebase, and resumes exactly where you left off every session.
      6 npm
      5
      -

    • MCP Project Manager

      skdkfk8758
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive project management and workflow tracking system that integrates with Claude Code via MCP, automatically capturing sessions, tools, agents, and project tasks into a centralized dashboard and database.
      7 npm
      MIT

    • Task Manager

      SimoCingo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to run a personal task manager in natural language: creating, updating, completing, deleting, listing, and searching tasks and projects, checking an overview, and performing weekly reviews. Tasks are stored in the user's own Cloudflare D1 database via a Worker exposed over MCP with OAuth 2.1 and password-protected access.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a distinct, clearly separated purpose with explicit cross-references in descriptions (e.g., 'use task_log instead', 'use task_doc_write instead'). No overlapping functionality—CRUD, lifecycle, archival, and document operations are cleanly partitioned.

    Naming Consistency5/5

    Strict snake_case convention with consistent 'task_' prefix. Sub-resources follow predictable patterns (task_doc_read/write/delete, task_archive_list/load). Verbs are clear and consistently placed (task_add, task_delete, task_modify).

    Tool Count4/5

    24 tools is above the typical ideal range but justified by the domain complexity. The set covers full task lifecycle, document attachments, archival management, annotations, and discovery without redundancy. Each tool earns its place for a comprehensive backlog system.

    Completeness4/5

    Excellent coverage of CRUD, status workflow (start/stop/done), soft-delete with purge, annotations, document attachments, and archival. Minor gap: archived tasks are view-only with no restore-to-active operation, though this appears to be an intentional cold-storage design.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources