Dooray MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOORAY_API_KEY | Yes | Your Dooray API key | |
| DOORAY_PROJECT_ID | Yes | Your default Dooray project ID |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dooray_list_tasksC | List tasks from Dooray project with optional filtering |
| dooray_get_taskC | Get detailed information about a specific task |
| dooray_list_commentsC | List comments on a specific task |
| dooray_add_commentC | Add a new comment to a task |
| dooray_update_commentC | Update an existing comment |
| dooray_delete_commentC | Delete a comment from a task |
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 6 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: three tools for comments (add, delete, update), two for tasks (get, list), and one for listing comments. No overlap or ambiguity exists between these functions.
All tools follow a consistent 'dooray_verb_noun' pattern with snake_case, using clear verbs like add, delete, get, list, and update. This uniformity makes the tool set predictable and easy to understand.
With 6 tools, this server is well-scoped for managing tasks and comments in Dooray. Each tool serves a distinct and necessary function, avoiding bloat while covering core operations effectively.
The server provides complete CRUD coverage for comments (add, delete, update, list) and good task management (get, list), but lacks task creation, update, or deletion tools. This minor gap may require workarounds for full task lifecycle management.