Dooray MCP Server
Related Servers
Alternatives to Dooray MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables integration with Dooray API for comprehensive project management including task operations, comment management, tag organization, search functionality, and user management. Supports task creation, modification, status updates, assignee management, and collaborative features through natural language interactions.7-
- FlicenseNot gradedqualityCmaintenanceEnables Claude Code to query, create, and modify Dooray tasks via natural language.-
- FlicenseBqualityDmaintenanceEnables interaction with Dooray's task and calendar management system, allowing users to filter and list tasks, retrieve details, and manage task comments. It provides a set of tools for seamless integration with MCP-compatible clients like Claude Desktop and Cursor.6-
- AlicenseNot gradedqualityDmaintenanceEnables Jira integration for comprehensive issue management, board operations, time tracking, and project management through natural language.MIT
- AlicenseBqualityCmaintenanceEnables LLM clients to manage tasks and projects, search content, handle comments, custom fields, recurring tasks, statuses, schedules, and workspaces through natural conversation.10Apache 2.0
- AlicenseAqualityCmaintenanceEnables interaction with Megaplan project management platform, allowing users to manage tasks, deals, projects, and comments through natural language.835 npm2MIT
TDQS
Scored across 70 tools
Most tools target distinct resource+action pairs, but several clusters blur together: upload-wiki-file vs upload-wiki-page-file, download-wiki-page-file vs download-wiki-attach-file (fileId vs attachFileId), and update-task vs update-task-body / update-wiki-page vs update-wiki-page-body. Detailed descriptions do a lot of work to differentiate them, but an agent still has to read carefully to pick correctly.
Almost all tools follow verb_noun kebab-case (create-task, get-wiki-page, delete-calendar-event, move-drive-file), which is predictable. Minor deviations exist: task attachment tools omit the 'task' qualifier (upload-attachment vs upload-wiki-page-file), and metadata is spelled 'get-drive-file-meta' versus 'get-attachment-metadata'.
70 tools is far above a comfortable surface even for a broad product (tasks, wiki, drive, calendar, members, templates, tags, attachments). Many are highly granular variants (six task-attachment tools, separate -body update tools, dual wiki file-upload tools) that could be consolidated or made optional parameters.
Coverage is genuinely broad: tasks have create/read/update/list, comments CRUD, attachments, tags, templates, milestones and workflows; wiki, drive and calendar each have near-full lifecycles. The main gap is the absence of a delete-task tool (and no tag delete/update beyond group settings), which leaves a dead end for the core entity.