ya-planka-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANKA_EMAIL | No | Email address for Planka login (used with PLANKA_PASSWORD) | |
| PLANKA_API_KEY | No | Admin-generated API key from Planka's user administration screen | |
| PLANKA_BASE_URL | Yes | Base URL of your Planka instance (e.g. https://planka.example.com, no trailing slash) | |
| PLANKA_PASSWORD | No | Password for Planka login (used with PLANKA_EMAIL) | |
| PLANKA_API_TOKEN | No | JWT access token from the legacy /api/access-tokens exchange |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| planka_get_workspaceA | Get complete workspace structure (projects, boards, lists, labels, users). Pass project_name or board_name to scope the response — resolving a single board? board_name returns a fraction of the full dump. |
| planka_get_meA | Get authenticated user identity (id, username, role). |
| planka_get_labelsA | Get all labels on a board (fast targeted refresh without full workspace re-fetch). |
| planka_create_boardC | Create a new board with canonical lists and lifecycle labels. |
| planka_create_listC | Create a list on a board. |
| planka_update_listB | Rename and/or reorder a board list. |
| planka_create_labelA | Create a label on a board (idempotent by name). |
| planka_update_labelB | Update a label's name or color. |
| planka_delete_labelB | Delete a label from a board. |
| planka_list_cardsC | List cards with filtering and pagination options. |
| planka_find_and_get_cardC | Find and get card details by search query. |
| planka_get_cardA | Get detailed information about a specific card. |
| planka_create_cardC | Create a new card in a specified list. |
| planka_update_cardC | Update an existing card's properties. |
| planka_add_taskC | Add a task to a card. |
| planka_create_task_listC | Create a named task list on a card. |
| planka_update_taskC | Update a task's completion status. |
| planka_add_card_labelB | Add a label to a card. |
| planka_remove_card_labelB | Remove a label from a card. |
| planka_add_card_memberB | Add a member to a card. |
| planka_remove_card_memberB | Remove a member from a card. |
| planka_delete_cardC | Delete a card from Planka. |
| planka_move_cardsB | Bulk-move cards to a target list for kanban ceremonies. |
| planka_next_cardC | Get the top card of a list (default TODO) with full execution context. |
| planka_card_ready_checkC | Mechanically validate a card against the card-schema readiness rules. |
| planka_board_statusA | One-call board status report: per-list counts, in-progress ages, blocked cards with latest Blocked: comment, unsatisfied gates, done-window points. |
| planka_delete_taskC | Delete a task from a card. |
| planka_add_commentB | Add a comment to a card. |
| planka_get_commentsC | List comments on a card. |
| planka_create_custom_field_groupB | Create a board-wide or card-specific custom field group. |
| planka_get_custom_field_groupA | Read a custom field group with its fields and values. |
| planka_update_custom_field_groupC | Update a custom field group's name and/or position. |
| planka_delete_custom_field_groupB | Delete a custom field group. |
| planka_create_custom_fieldC | Create a custom field inside a custom field group. |
| planka_update_custom_fieldD | Update a custom field. |
| planka_delete_custom_fieldC | Delete a custom field. |
| planka_set_custom_field_valueC | Set a custom field value on a card. |
| planka_delete_custom_field_valueB | Delete a custom field value from a card. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
Most tools have clearly distinct purposes, such as creating, updating, deleting, or retrieving specific entities. However, slight overlap exists between 'planka_find_and_get_card' and 'planka_get_card', and 'planka_get_labels' may be redundant with workspace data, but descriptions clarify intent.
The vast majority follow a consistent 'planka_verb_noun' pattern (e.g., planka_create_card, planka_delete_label). A few outliers like 'planka_board_status' and 'planka_card_ready_check' break the pattern, and 'planka_next_card' uses an adjective as verb, but overall naming is predictable.
38 tools is on the higher end but appropriate for a full-featured project management server covering boards, lists, cards, labels, custom fields, tasks, comments, and members. Each tool serves a specific action, and while a few could be merged, the count is reasonable for the domain.
The tool set covers most core operations (CRUD for cards, labels, custom fields, tasks, comments), but lacks board update/delete, list delete, and comment delete. The presence of specialized tools like 'planka_board_status' and 'planka_card_ready_check' indicates attention to workflows, yet gaps remain.