Skip to main content
Glama

Related Servers

Alternatives to kanboard-mcp

  • A
    license
    A
    quality
    A
    maintenance
    A remote Model Context Protocol server acting as middleware to the Sentry API, allowing AI assistants like Claude to access Sentry data and functionality through natural language interfaces.
    7
    35 npm
    908
    MIT

Related Servers

  • 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
  • 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.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides MCP tools to manage a local-first Kanban board, including projects, issues, dependencies, and labels. Enables AI clients to interact with the board via a stdio MCP server connected to a NestJS API.
    3 npm
    MIT
  • 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
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.
    -

TDQS

A4.2/5.0

Scored across 39 tools

Disambiguation5/5

Each tool has a clearly distinct purpose, with descriptions explicitly differentiating similar operations (e.g., close_task vs delete_task, create_task vs create_tasks_batch). Overlapping tools are well distinguished by documentation.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., create_project, list_tasks, update_column). The naming is predictable and uniform across all entities.

Tool Count3/5

With 39 tools, the server covers a comprehensive Kanboard domain but feels heavy. While each tool is justified for full lifecycle management, the count exceeds typical MCP server scope (3-15 tools), making it borderline overwhelming.

Completeness4/5

The tool surface is very comprehensive, covering CRUD for projects, tasks, subtasks, comments, columns, swimlanes, users, and files, plus batch and movement operations. Minor gaps exist, such as missing list_comments or get_subtask by id, but the core workflows are well supported.

Maintenance

ActivityInactive
ResponsivenessNo issues