dooray-mcp-link
Related Servers
Alternatives to dooray-mcp-link
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides read-only access to Dooray collaboration services through REST, CalDAV, and LDAP, enabling queries for projects, tasks, calendar events, and directory information via 18 MCP tools.-
- FlicenseBqualityBmaintenanceEnables MCP-compatible AI clients to securely read a user's Microsoft 365 data across Outlook, Calendar, Teams, meetings, OneNote, SharePoint, OneDrive, Loop, and Search, and to send Outlook email only after explicit user confirmation.103-
- AlicenseAqualityCmaintenanceEnables read-only access to Finary portfolio data, including profiles, organizations, institution connections, portfolios, and transactions, through MCP.5MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to securely access Jisr's documented HR Open API read-only operations, including employees, attendance, leave, payroll, finance, and discovery tools, with role-based field policies and dual protocol support.11MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables MCP clients to access Amazon Selling Partner and Advertising APIs for orders, inventory, pricing, ads, reports, and related read paths.MIT
- AlicenseBqualityBmaintenanceDooray MCP server for interacting with Dooray services such as messenger, calendar, project, and posts. Supports operations like reading, creating, and updating posts, comments, and files.1516 npmMIT
TDQS
Scored across 15 tools
The tools are mostly separable by resource: calendars, events, members, projects, posts, files, logs, messenger, and one OS utility. A few pairs like dooray_post_log vs dooray_post_logs and dooray_post_files vs dooray_post_file_download require careful reading, but the descriptions clarify the list/get and list/download boundaries.
Naming is consistently lowercase snake_case with a dooray_ prefix, but verb placement is inconsistent: dooray_calendar_post_event places the action before the object, while dooray_post_log_create and dooray_post_file_download place it after. Bare noun tools like dooray_project and dooray_posts, plus the pattern-breaking 'os', further weaken consistency.
Fifteen tools is at the upper edge of a well-scoped set and each Dooray resource area has at least one operation. The server does span many concerns—project, calendar, messenger, account, files, and OS—and the os tool feels tacked on, but the count is still reasonable for the described integration.
The set covers discovery and reading for projects, posts, comments, calendars, members, and files, plus comment/event creation and comment updates. Notable lifecycle gaps exist: there is no create/update/delete for task posts, no update/delete for calendar events, and no messenger read capability.