Skip to main content
Glama
VoidNullable

Lific

by VoidNullable
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to Lific

No user-submitted related servers found.

    Related Servers

    • sprinter

      danimoya
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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

    • Saga MCP

      spranab
      A
      license
      B
      quality
      A
      maintenance
      A Jira-like project tracker MCP server for AI agents. SQLite-backed, per-project scoped, with full hierarchy and activity logging — so LLMs never lose track. No more scattered markdown files. saga-mcp gives your AI assistant a structured database to track projects, epics, tasks, subtasks, notes, and decisions across sessions.
      41
      170 npm
      37
      MIT

    • primer-mcp

      ivanlai
      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
      MIT

    • KittyClaw

      Ekioo
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted kanban board that dispatches AI agent fleets against tickets. The embedded Streamable HTTP /mcp endpoint exposes 7 tools to list projects, read boards and tickets, and create, move and comment tickets from any MCP client.
      26
      AGPL 3.0

    • AgentIssueTracker

      Rhynier
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for tracking issues across multiple AI agent sessions, enabling agents to file, claim, complete, review, and close issues with a web UI for monitoring.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation3/5

    Tools like edit_issue and update_issue have overlapping purposes but are differentiated by method (exact string replacement vs general field update). delete_comment overlaps with the generic delete tool, which can also delete comments, causing potential ambiguity. Overall, most tools are distinct, but these redundancies lower clarity.

    Naming Consistency3/5

    The naming follows a verb_noun pattern for most tools, but there are exceptions like 'delete', 'export', and 'search' without a noun. Additionally, the use of 'edit' vs 'update' for similar operations (edit_issue, update_issue) introduces inconsistency, as does 'add_comment' instead of 'create_comment'.

    Tool Count3/5

    With 27 tools, the count is slightly above the typical range for a well-scoped server. The domain spans issues, pages, plans, comments, resources, and auxiliary features, but redundant tools (delete vs delete_comment, edit vs update for each entity) inflate the count unnecessarily. It's manageable but could be streamlined.

    Completeness5/5

    The tool set covers CRUD operations for issues, pages, plans, and comments, plus resource management, linking, bulk updates, activity logs, board views, export, and search. No major gaps are apparent for the stated domain, and all core workflows appear supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources