Skip to main content
Glama

Related Servers

Alternatives to aiboard

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage a file-backed ticketing system directly within a local repository using a structured state machine and directory hierarchy. It enforces strict markdown schemas and provides specialized tools for claiming tasks, appending work logs, and validating ticket metadata.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create, query, update, claim, hand off, and complete tasks on a local SQLite-backed, project-namespaced kanban board through stdio MCP tools, including filtering for ready/blocked/stale work and exchanging task attachments. It also lets agents list projects and manage statuses, ownership, and evidence without any server or accounts.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables a planning Claude chat and Claude Code to exchange work through local Markdown files, letting the chat create tasks that code agents pick up, complete, and report back on. Project-scoped task and report tools track each item's status from open through reported, eliminating manual copy-paste between the two clients.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A Jira-lite MCP server that enables planning-first workflows for AI-assisted development. It manages tickets as markdown files with YAML frontmatter, guiding agents through epics, stories, tasks, and architecture decision records.
      17
      40 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables one developer and their AI agents to manage issues, projects, milestones, labels, sub-issues, priorities, estimates, blockers, attachments, search, and soft delete/restore over MCP, with every write attributed.
      1 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions (comments vs worklog, tasks vs sprints, ranking vs status changes). The main overlap is among start_task, assign_task, and change_task_status, but the descriptions explicitly clarify when to use start_task over the other two.

    Naming Consistency3/5

    The dominant pattern is verb_noun (create_task, get_sprint, block_task), but there are noticeable deviations like sprint_add_tasks, sprint_remove_tasks, and board_summary. These remain readable but break the otherwise predictable convention.

    Tool Count3/5

    At 20 tools the surface is on the heavy side for a task-board server, though most tools correspond to distinct operations. It borders on over-scoped, especially with separate sprint membership and status tools.

    Completeness4/5

    Task lifecycle is well covered: create, list, get, edit, status, assignment, blocking, ranking, comments, and worklogs, plus sprint creation and membership management. Minor gaps remain around deleting tasks or sprints and editing sprint metadata, but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues