Planka MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | HTTP port used when MCP_TRANSPORT=sse | 3001 |
| MCP_TRANSPORT | No | MCP transport mode: stdio or sse | stdio |
| PLANKA_API_KEY | No | Planka API key sent as X-Api-Key | |
| PLANKA_BASE_URL | Yes | Your Planka instance URL | http://localhost:3000 |
| PLANKA_PASSWORD | No | Planka password | |
| PLANKA_USERNAME | No | Planka username or email | |
| ENABLE_ALL_TOOLS | No | Enable all 27 tools | false |
| ENABLE_ADMIN_TOOLS | No | Enable admin tools | false |
| ENABLE_OPTIONAL_TOOLS | No | Enable optional tools | false |
| PLANKA_HTTP_MAX_RETRIES | No | Max retry attempts for transient HTTP/network failures per request | 2 |
| PLANKA_HTTP_RETRY_BASE_DELAY_MS | No | Base retry delay in milliseconds (exponential backoff) | 250 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authB | Authentication operations for login flows, token management, and terms acceptance. |
| bootstrapB | Get Planka application bootstrap data including current user, projects, boards, and notifications. |
| projectsB | Manage Planka projects. Projects are top-level containers for boards. |
| boardsC | Manage Planka boards. Boards contain lists and cards for organizing work. |
| listsB | Manage Planka lists. Lists are columns on a board that contain cards. |
| cardsC | Manage Planka cards. Cards are individual work items on a board. |
| commentsC | Manage comments on Planka cards. |
| tasksB | Manage task lists and tasks on Planka cards. Tasks are checklist items within a card. |
| labelsB | Manage labels on Planka boards and cards. Labels help categorize and filter cards. |
| cardMembersC | Manage user assignments on Planka cards. |
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 10 tools
Each tool targets a distinct Planka resource or function: projects, boards, lists, cards, comments, tasks, labels, cardMembers, plus bootstrap and auth. There is no overlap in primary purpose, and even the potentially confusing lists vs. tasks are clearly differentiated by their descriptions (columns vs. checklist items).
Tool names are mostly single lowercase nouns representing resources (projects, boards, lists, cards), which is a consistent pattern. However, 'cardMembers' uses camelCase breaking the all-lowercase convention, and 'bootstrap' and 'auth' are not resource CRUD names, creating minor semantic deviation.
With 10 tools covering core Planka entities and operations, the count is well-scoped for the domain. It is neither too thin nor overly heavy, fitting comfortably within the typical 3-15 tool range for a focused CRUD server.
The tool set covers the primary resource lifecycle for projects, boards, lists, cards, comments, tasks, labels, and members, which is sufficient for most workflow needs. Minor gaps exist (e.g., no explicit search, activity log, or attachment support), but these are not critical for baseline operations.