A
licenseNot graded
qualityA
maintenanceMCP server for the Plaky project management API. Provides 32 generated and 7 curated tools for spaces, boards, items, comments, and more, with safe defaults and dry-run mutations.
MIT
plaky-mcp
by pavlealeksic
Related Servers
Alternatives to plaky-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables interaction with ClickUp workspaces, spaces, folders, lists, tasks, and comments via MCP tools.1Apache 2.0
- FlicenseCqualityAmaintenanceEnables AI assistants to manage Planka projects, boards, lists, cards, tasks, labels, comments, stopwatches, and memberships through MCP tools.56-
- AlicenseNot gradedqualityAmaintenanceEnables natural-language interaction with Favro through MCP, exposing 85 typed tools for searching, resolving names to IDs, and safely mutating data with dry-run support.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Clickup's project management tools through the MCP protocol, allowing task and project operations via natural language.1MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to control a Planka 2.x board via 15 MCP tools, with writes re-read and verified so reported success matches the board, plus an optional workflow that turns the board into durable agent memory.1532 npm2MIT
TDQS
A3.7/5.0
Scored across 26 tools
Disambiguation5/5
Each tool targets a distinct resource-action combination (e.g., create_item vs. create_item_comment, update_item_field vs. update_item_fields). There is no ambiguity between tools; even similar ones like list_items and list_subitems are clearly differentiated by resource.
Naming Consistency5/5
All tools follow the pattern 'plaky_<verb>_<noun>' in snake_case. Verbs are consistent (create, delete, get, list, update, etc.) and nouns correspond to the resource. No mixing of conventions.
Tool Count4/5
26 tools is on the higher side but still appropriate for a comprehensive project management MCP server covering items, comments, files, boards, spaces, users, and teams. Each tool serves a distinct purpose; the count is justified by the domain's breadth.
Completeness4/5
The tool surface covers core CRUD operations for items, comments, and files, plus listing for boards, spaces, users, teams, and subitems. Missing operations like creating/updating boards or spaces are minor gaps for a tool focused on item-level management.
Maintenance
ActivityInactive
ResponsivenessNo issues