planfix-mcp
Related Servers
Alternatives to planfix-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityBmaintenanceMCP server for Planfix REST API that generates tools from an OpenAPI spec, exposing operations like task_list and comment_add with Russian descriptions, filtering, and response validation.37-
- AlicenseCqualityDmaintenanceMCP server for Plane integration, enabling AI agents to interact with Plane APIs and services for project management tasks.100MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Watermelon.ai that exposes all 13 public API endpoints as tools, enabling AI assistants to manage contacts, conversations, messages, custom fields, and webhooks.MIT
- AlicenseCqualityBmaintenanceMCP server for Voximplant API enabling calls, SMS, recordings, scenarios, and rules management with 11 tools and 2 skills.2357 npm3MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with self-hosted Planka boards through the Planka REST API. It allows users to list, search, create, and update projects, boards, and cards using natural language.3-
- AlicenseAqualityFmaintenanceMCP server enabling AI agents to manage PLANKA kanban boards with full CRUD support for cards, tasks, labels, comments, and lists.15129 npm11MIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action: tasks have list/get/create/update, contacts have list/get/create/update, and separate tools for comments, files, users, directories, custom fields, and datatags. No two tools overlap in purpose, and the singular/plural naming clearly differentiates collection vs single-item operations.
All tool names follow a verb_noun snake_case pattern, which is consistent and readable. However, collections use a mix of 'list_' (list_custom_fields, list_datatags, list_users, list_directories) and 'get_' (get_tasks, get_contacts, get_projects), creating a minor inconsistency in the verb prefix for the same type of operation.
With 20 tools, the set is on the heavier side but well-scoped for a comprehensive Planfix integration covering tasks, contacts, projects, comments, files, users, and metadata. Each tool has a clear place, and the count is justified by the breadth of the domain, though it borders on the 'heavy' range.
The toolset provides solid coverage for tasks (create, read, update) and contacts (create, read, update), plus essential supporting operations for comments and files. Major gaps include no delete operations for tasks or contacts, read-only access to projects (no create/update), and no update/delete for comments, which are workable but incomplete lifecycle gaps.