Skip to main content
Glama
0Thomas1

Kanban MCP Server

by 0Thomas1

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create-taskC

create a new todo task

move-taskB

move a task to a different status

set-prioityC

set a task to a different priority

add-tagC

add tags to a tasks

Prompts

Interactive templates invoked by user choice

NameDescription
tasks-analyticsget analytics for users tasks

Resources

Contextual data attached and managed by the client

NameDescription
tasksGet all tasks from the database

TDQS

B3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add-tag modifies metadata, create-task creates new items, move-task changes workflow status, and set-prioity adjusts priority levels. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency3/5

The naming is mixed: add-tag and move-task use verb-noun patterns, while create-task and set-prioity use verb-noun but with inconsistent spelling (e.g., 'prioity' vs. 'priority'). This reduces predictability, though the tools remain readable.

Tool Count4/5

With 4 tools, the count is appropriate for a kanban server, covering core operations like task creation, status movement, tagging, and priority setting. It is slightly lean but reasonable for the domain, lacking only minor features like task deletion or listing.

Completeness3/5

The toolset covers basic CRUD-like operations but has notable gaps: there is no tool to delete tasks, list tasks, or retrieve task details. This could lead to agent failures when full lifecycle management is needed, though core workflows are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues