Planka MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANKA_BASE_URL | No | URL base del servidor Planka | http://localhost:3000 |
| PLANKA_AGENT_EMAIL | Yes | Email para autenticación | |
| PLANKA_AGENT_PASSWORD | Yes | Contraseña para autenticación | |
| PLANKA_ALLOW_INSECURE | No | Permitir conexiones HTTPS sin validar certificado SSL (útil para certificados autofirmados o internos) | false |
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
| Name | Description |
|---|---|
| mcp_kanban_project_board_managerD | Manage projects and boards with various operations |
| mcp_kanban_list_managerC | Manage kanban lists with various operations |
| mcp_kanban_card_managerD | Manage kanban cards with various operations |
| mcp_kanban_stopwatchC | Manage card stopwatches for time tracking |
| mcp_kanban_label_managerD | Manage kanban labels with various operations |
| mcp_kanban_task_managerC | Manage kanban tasks with various operations |
| mcp_kanban_comment_managerC | Manage card comments with various operations |
| mcp_kanban_membership_managerC | Manage board memberships with various operations |
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 8 tools
Every tool has a clearly distinct purpose targeting different resources in the kanban domain: cards, comments, labels, lists, memberships, projects/boards, stopwatches, and tasks. There is no overlap or ambiguity between these resource types, making tool selection straightforward for an agent.
All tool names follow a perfectly consistent pattern: 'mcp_kanban_' prefix followed by a specific resource type and '_manager' suffix (except 'mcp_kanban_stopwatch' which still fits the overall convention). This predictability makes the tool set easy to navigate and understand.
With 8 tools, this server is well-scoped for managing a kanban system. Each tool covers a distinct aspect (cards, tasks, projects, etc.), and the count is neither too sparse nor overwhelming, providing comprehensive coverage without redundancy.
The tool set offers complete CRUD/lifecycle coverage for the kanban domain, including core resources (cards, tasks, projects), supporting elements (comments, labels, lists), and administrative features (memberships, time tracking). There are no obvious gaps that would hinder agent workflows.