dooray-mcp-js
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOORAY_TOKEN | Yes | Dooray personal API token. Can also be passed as --token. | |
| DOORAY_MCP_MODE | No | Tool exposure mode: full or read-only. Can also be passed as --mode. | full |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dooray_messengerB | send message to dooray messenger |
| dooray_calendar_calendarsC | find dooray calendars |
| dooray_calendar_eventsC | find dooray events of calendars |
| dooray_calendar_post_eventC | register dooray events on a calendar |
| dooray_account_membersA | find dooray account members by name or userCode |
| dooray_account_memberC | find dooray account members by id |
| dooray_projectB | find Dooray projects or get a project by id |
| dooray_postsC | find dooray posts in projects |
| dooray_post_logsC | find comments and activity logs of a Dooray post |
| dooray_post_logB | find a specific comment or activity log of a Dooray post |
| dooray_post_log_createB | add a comment to a Dooray post |
| dooray_post_log_updateC | update a comment or activity log of a Dooray post |
| dooray_post_filesA | find attachments of a Dooray post |
| dooray_post_file_downloadA | download raw content of a Dooray post attachment through authenticated redirects to a local temporary directory |
| osB | get os time date |
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 15 tools
Most tools have clear resource-action boundaries (e.g., account member lookup vs. calendar events), but a few pairs like dooray_post_logs and dooray_post_log could confuse agents without careful reading. The plural/singular distinction helps, and the 'os' tool is clearly separate.
The naming is mostly consistent with a dooray_<domain>_<resource> pattern for queries and dooray_<domain>_<resource>_<verb> for actions. However, 'dooray_messenger' (a send action without a verb) and the standalone 'os' tool break the pattern, along with redundant 'dooray_calendar_calendars'.
15 tools is within a reasonable range for a multi-domain integration (account, messenger, calendar, posts, logs, files). The inclusion of an unrelated 'os' tool slightly detracts from the overall scope, but the count is not excessive.
Critical CRUD operations are missing across resources: no way to create or update posts, no update/delete for calendar events, no read for messenger, and no upload for files. While some actions exist (create calendar event, add comment, download file), the surface is incomplete for full lifecycle management, leading to dead ends.