Skip to main content
Glama
lrivallain

kanban.board

by lrivallain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_boardsA

List the GitHub Projects v2 boards the user tracks.

Covers the configured repository's account when there is one, plus every
project source added on the board. Returns each board's ``id`` (needed by
``get_board``), ``number``, ``title`` and ``url``.
get_boardA

Read one board: its Status columns and every issue/PR card on it.

``project_id`` is the opaque node id from ``list_boards`` (e.g. ``PVT_…``).
Each card carries its ``number``, ``title``, ``state``, ``repo``, ``labels``
and the ``status_name`` column it sits in.
board_summaryA

Summarise a board as counts per column, plus its total card count.

Cheaper for the model to reason over than the full card list when the question is "where does the work stand?".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct role: discovering boards, reading a full board, and producing a column summary. Descriptions clarify when to use board_summary vs get_board, so there is no ambiguity.

Naming Consistency4/5

list_boards and get_board follow a clear verb_noun pattern, but board_summary uses a noun phrase instead. The names remain readable and consistent in domain terminology, but this small deviation makes the set mostly consistent rather than fully uniform.

Tool Count5/5

With three tools, the server is tightly scoped to reading and summarizing Kanban boards. Each tool has a clear purpose, and the count feels appropriate rather than excessive or thin.

Completeness4/5

The tools cover board discovery, full board retrieval, and aggregate summaries, which is complete for a read-only Kanban workflow. The absence of write operations (create/update/move) is a notable gap if broader board management is expected, but for the stated tracking purpose the surface is sufficient.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources