Skip to main content
Glama
Developyn

Laver

by Developyn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Laver

No user-submitted related servers found.

    Related Servers

    • 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.
      27
      AGPL 3.0

    • Kanban MCP Server

      rikamalov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to work a self-hosted kanban board as first-class users, exposing eleven kanban_* tools over a stateless Streamable HTTP endpoint for listing projects, stages, members and custom fields, and for creating, updating, moving and deleting tasks. Authenticates with bearer-token scopes so read-only or write access can be granted per agent, with every mutation audited.
      4
      MIT

    • acta

      nubisco
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and humans to collaboratively manage kanban boards and Markdown documentation via MCP tools, with stable item keys, revision-safe editing, and full audit trails.
      MIT

    • Morion AI MCP

      miksushko
      A
      license
      Not graded
      quality
      B
      maintenance
      Local kanban board & harness for coding agents over MCP: agents claim and move tasks, read and write notes, and build Auto-code workflows, within per-folder permissions and an audit log.
      5 npm
      1
      Apache 2.0

    • Kanban MCP

      NatMota
      A
      license
      B
      quality
      B
      maintenance
      Provides a local-first MCP interface for managing SQLite-backed projects, boards, and tickets, including metrics, epics, documentation links, run-history, and staging-lease coordination with completion summaries for done items.
      32
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.4/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a distinct resource (ticket, board, wiki, automation, workspace) and a distinct action (list, create, get, update, move, etc.). Even similar tools like list_tickets and get_board are clearly separated by their descriptions. There is no ambiguity about which tool to call for a given operation.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, e.g., list_tickets, create_ticket, update_ticket, get_wiki_page, restore_wiki. The only minor deviation is 'search' and 'comment_on_ticket', but the pattern remains predictable. No mixing of case or conventions.

    Tool Count3/5

    With 30 tools, the surface is large, which could overwhelm agents. However, the server covers a broad domain (tickets, attachments, wiki, automations, boards) and each tool appears purposeful. It's on the heavy side but not extreme for the scope.

    Completeness3/5

    Ticket and attachment operations are fully covered, including archive/delete and comments. Wiki pages support create/append/versioning but intentionally not edit/delete. A notable gap is automation rules: they can be created and listed but not updated or deleted, which is a missing lifecycle.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources