Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KAITEN_TOKENYesThe Kaiten API token used for all requests.
KAITEN_ORIGINYesYour company origin, such as https://company.kaiten.ru. Supply the origin only, without an API path or query string.
KAITEN_TIMEOUT_MSNoTimeout for each tool operation, in milliseconds. Defaults to 30000; accepts integers from 1 to 2147483647.30000

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
kaiten_list_spacesB

List accessible Kaiten spaces. Use their IDs to discover boards.

kaiten_get_spaceB

Get a space and its available board references.

kaiten_list_boardsB

List boards in a space. Pagination is applied locally.

kaiten_get_boardB

Get board details, columns, lanes and custom property configuration.

kaiten_list_columnsB

List columns on a board in Kaiten order. Pagination is applied locally.

kaiten_list_lanesB

List lanes on a board. Pagination is applied locally.

kaiten_get_current_userA

Identify the user associated with the configured Kaiten token.

kaiten_list_usersB

Find company users by query to obtain user IDs for ownership and membership.

kaiten_list_card_typesC

List existing card types.

kaiten_list_tagsC

Find tags by name, optionally within a space.

kaiten_search_cardsA

Search cards with filters. Returns summaries and a cursor; reuse the same filters with next_cursor. Fetch details with kaiten_get_card.

kaiten_get_cardA

Get a card with its full description, members, tags, properties and checklist references. Read comments and checklist items with their dedicated tools.

kaiten_create_cardC

Create a card on a board. Description uses Markdown. Optional properties use Kaiten id_ keys.

kaiten_update_cardA

Update the supplied card fields. Omitted fields remain unchanged; null clears supported fields. Description uses Markdown.

kaiten_move_cardA

Move a card to an explicit board, column and lane. Obtain valid target IDs using the navigation tools.

kaiten_archive_cardA

Archive a card. The card can be restored with kaiten_restore_card.

kaiten_restore_cardB

Restore an archived card to its live condition.

kaiten_delete_cardA

Delete a card using the Kaiten delete endpoint. This is a destructive operation; use archive_card for archiving.

kaiten_list_commentsA

Read card comments. Full comment text is preserved; pagination is applied locally.

kaiten_add_commentC

Add a text comment to a card.

kaiten_update_commentB

Replace the text of an existing comment.

kaiten_delete_commentC

Delete an existing card comment.

kaiten_list_card_membersB

List card memberships. Use the returned id as member_id and user_id to identify the user.

kaiten_add_card_memberB

Add an existing user to a card using user_id.

kaiten_update_card_member_roleB

Make a card member responsible with type 2. Use the membership id returned by list_card_members. Returns card_id, user_id and type.

kaiten_remove_card_memberC

Remove a membership from a card using its member_id.

kaiten_list_card_tagsB

List tags attached to a card. Pagination is applied locally.

kaiten_add_card_tagB

Attach a tag by name. Kaiten may create the tag if it does not exist.

kaiten_remove_card_tagC

Detach a tag from a card using tag_id.

kaiten_list_checklistsA

List checklist references on a card. Fetch item details with kaiten_get_checklist.

kaiten_get_checklistB

Read a card checklist and all its items.

kaiten_create_checklistB

Create an empty named checklist on a card.

kaiten_update_checklistC

Change a checklist name or order.

kaiten_delete_checklistC

Delete a checklist from a card.

kaiten_add_checklist_itemC

Add a checklist item with optional completion, order, due date and responsible user.

kaiten_update_checklist_itemB

Change checklist item fields. checked marks completion; null clears text, due_date or responsible_id.

kaiten_delete_checklist_itemC

Delete an item from a card checklist.

kaiten_list_custom_propertiesB

Find existing custom property definitions. Inspect type, multi_select and data before assigning values.

kaiten_get_custom_propertyB

Read a custom property definition and type-specific settings.

kaiten_list_select_valuesC

Find existing select options. Card values use an array of numeric option IDs, including single-select properties.

kaiten_list_catalog_valuesC

Find existing catalog values. Assign a catalog value ID as a string in card properties.

kaiten_list_custom_directoriesB

Find existing custom directories with field definitions.

kaiten_list_custom_directory_recordsC

Find records in an existing custom directory. Assign record UUIDs as an array in card properties.

kaiten_set_card_propertiesA

Set existing card properties using id_ keys. Omitted properties remain unchanged; null clears a value. Use native Kaiten formats: scalar text/number, select ID arrays, catalog string ID, directory UUID arrays, or a date object with date/time/tzOffset. Definitions and options are read-only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 44 tools

Disambiguation4/5

Most tools target distinct resources and actions, and descriptions help. However, card modification has overlapping pathways: kaiten_update_card, kaiten_move_card, and kaiten_set_card_properties could be confused when changing placement or custom fields, and the several custom-field metadata list tools require domain knowledge to choose correctly.

Naming Consistency5/5

All tools use the kaiten_ prefix followed by consistent snake_case verb_noun names (list_, get_, create_, update_, delete_, add_, remove_, set_). The pattern is predictable and easy to scan.

Tool Count2/5

44 tools is well above the typical 3-15 range and heavy for an agent to hold in context. While the broad Kaiten domain explains the count, several granular groups (e.g., checklist items, card members, custom-field metadata) could be consolidated.

Completeness4/5

The server covers CRUD for cards, comments, checklists, members, tags, and custom property values, plus navigation of spaces, boards, columns, and lanes. It lacks attachments, card links/blockers, and time tracking, which are minor-to-notable gaps for a project management system.

Maintenance

ActivityMaintained
ResponsivenessNo issues