Skip to main content
Glama

Dooray MCP Server

Dooray! 의 프로젝트, 업무, 위키, 드라이브, 캘린더를 AI assistant 에서 다루게 하는 MCP 서버.

설치

Node.js 18 이상이 필요합니다. MCP 등록 시 npx 로 실행되므로 별도 설치 없이 사용 가능합니다.

전역 설치가 필요하면:

npm install -g @jhl8041/dooray-mcp

Related MCP server: Dooray MCP Server

설정

1. API 토큰 발급

두레이 개인설정 > API > 개인 인증 토큰 메뉴에서 생성합니다. 가이드

2. 환경변수

변수

필수

설명

DOORAY_API_TOKEN

O

발급받은 API 토큰

DOORAY_WRITE_API_TOKEN

쓰기 요청(POST, PUT, PATCH, DELETE)에만 쓸 API 토큰. 업무, 댓글 등을 이 토큰의 계정으로 남기고, 조회는 DOORAY_API_TOKEN 으로 합니다. 쓰기가 실패해도 DOORAY_API_TOKEN 으로 다시 보내지 않습니다

DOORAY_API_BASE_URL

API 주소 (기본값 https://api.dooray.com)

LOG_LEVEL

ERROR, WARN, INFO, DEBUG (기본값 INFO). 로그는 stderr 로 출력됩니다

실행 위치에 .env 파일이 있으면 그 값도 적용됩니다.

MCP 등록

Claude Code

claude mcp add -s user dooray-mcp -e DOORAY_API_TOKEN=<발급받은 토큰> -- npx -y @jhl8041/dooray-mcp@latest

Claude Desktop

설정 파일 위치: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "dooray": {
      "command": "npx",
      "args": ["-y", "@jhl8041/dooray-mcp@latest"],
      "env": { "DOORAY_API_TOKEN": "<발급받은 토큰>" }
    }
  }
}

Tool 목록

공통

  • get-my-member-info - 사용자 정보 조회

  • get-member-list - 조직 전체 멤버 검색 (이름, 사용자 ID, 이메일, SSO ID)

  • get-member - 멤버 상세정보

캘린더

  • get-calendar-list - 캘린더 목록

  • get-calendar-event-list - 기간 일정 목록 (최대 1년)

  • get-calendar-event - 일정 상세정보 (본문, 참석자)

  • create-calendar-event - 일정 생성 (종일, 반복 일정 지원)

  • update-calendar-event - 일정 수정 (준 항목만 변경)

  • delete-calendar-event - 일정 삭제 (반복 일정 범위 지정)

프로젝트

  • get-project-list - 프로젝트 목록

  • get-project - 프로젝트 상세정보

  • get-project-workflow-list - 업무 상태 목록

  • get-task-list - 업무 검색/필터링

  • get-task - 업무 상세정보 (본문 제외 옵션 includeBody)

  • create-task - 업무 생성

  • update-task - 업무 수정 (담당자, 참조자, 태그 추가, 제거 옵션 포함. 담당자나 참조 한쪽만 넘기면 다른 쪽은 유지)

  • update-task-body - 업무 본문 일부 치환

  • create-task-comment - 댓글 작성

  • get-task-comment-list - 댓글 목록

  • get-task-comment - 댓글 단건 조회

  • update-task-comment - 댓글 수정 (이메일 댓글 수정 불가)

  • delete-task-comment - 댓글 삭제

  • get-milestone-list - 마일스톤 목록

  • get-tag-list - 태그 목록

  • get-tag - 태그 상세정보

  • create-tag - 태그 생성 (개별/그룹 태그)

  • update-tag-group - 태그 그룹 설정 수정

  • get-project-template-list - 템플릿 목록

  • get-project-template - 템플릿 상세정보

  • create-project-template - 템플릿 생성

  • update-project-template - 템플릿 수정

  • delete-project-template - 템플릿 삭제

  • get-project-member-list - 프로젝트 멤버 목록

  • get-project-member-group-list - 멤버 그룹 목록

첨부파일

  • upload-attachment - 파일 업로드

  • get-attachment-list - 첨부파일 목록

  • get-attachment-metadata - 첨부파일 메타데이터

  • download-attachment - 파일 다운로드 (savePath 옵션으로 로컬 저장 지원)

  • delete-attachment - 첨부파일 삭제

  • download-all-attachments - 첨부파일 일괄 다운로드 (디렉토리 저장)

드라이브

  • get-drive-list - 드라이브 목록 (개인/프로젝트)

  • get-drive-file-list - 파일/폴더 목록 조회

  • get-drive-file-meta - 파일 메타정보 조회 (file ID만으로)

  • create-drive-folder - 폴더 생성

  • rename-drive-file - 파일/폴더 이름 변경

  • move-drive-file - 파일/폴더 이동 (휴지통 이동 포함)

  • copy-drive-file - 파일 복사

  • delete-drive-file - 휴지통 파일 영구삭제

  • upload-drive-file - 파일 업로드

  • download-drive-file - 파일 다운로드 (savePath 옵션으로 로컬 저장 지원)

  • update-drive-file - 파일 새버전 업로드

위키

  • get-wiki-list - 위키 목록

  • get-wiki-page-list - 위키 페이지 목록

  • get-wiki-page-tree - 위키 페이지 트리 (깊이 지정)

  • get-wiki-page - 위키 페이지 상세정보

  • create-wiki-page - 위키 페이지 생성

  • update-wiki-page - 위키 페이지 수정

  • update-wiki-page-body - 위키 본문 일부 치환

  • move-wiki-page - 위키 페이지 이동 (부모, 순서, 다른 위키)

  • delete-wiki-page - 위키 페이지 삭제

  • get-wiki-page-comment-list - 위키 페이지 댓글 목록

  • get-wiki-page-comment - 위키 페이지 댓글 상세정보

  • create-wiki-page-comment - 위키 페이지 댓글 작성

  • update-wiki-page-comment - 위키 페이지 댓글 수정

  • delete-wiki-page-comment - 위키 페이지 댓글 삭제

위키 파일

  • upload-wiki-file - 위키에 파일 업로드 (페이지 생성 전 pre-upload용, attachFileId 반환)

  • upload-wiki-page-file - 기존 위키 페이지에 파일 업로드

  • download-wiki-page-file - 위키 페이지 첨부파일 다운로드 (fileId 사용, savePath 옵션으로 로컬 저장 지원)

  • download-wiki-attach-file - 위키 첨부파일 다운로드 (attachFileId 사용, savePath 옵션으로 로컬 저장 지원)

  • delete-wiki-page-file - 위키 페이지 첨부파일 삭제

Available Tools

70 tools
copy-drive-fileB

Copy a file in a Dooray drive to another location.

Required:

  • driveId: Source drive ID

  • fileId: File ID to copy

  • destinationDriveId: Target drive ID (can be same or different drive)

  • destinationFileId: Target folder ID

Example: { "driveId": "123", "fileId": "456", "destinationDriveId": "123", "destinationFileId": "789" }

Inputs: fileId (required), driveId (required), destinationFileId (required), destinationDriveId (required).

create-calendar-eventA

Create an event (일정 등록) in a Dooray calendar.

Required: calendarId, subject, startedAt, endedAt. Get calendarId from get-calendar-list (default=true is the user's own calendar).

Time Format:

  • Timed event: "2026-10-22T10:00:00+09:00"

  • Whole day event: set wholeDayFlag=true and use date format "2026-10-22+09:00". endedAt is the next day ("2026-10-23+09:00" for a one day event)

Attendees: {id, type} where type is "member" (organizationMemberId) or "email" (email address). Use get-my-member-info, get-project-member-list, get-member-list to find member IDs. Without attendees, the authenticated user is added as the attendee (the API rejects an event without one).

Examples:

  • Meeting: {"calendarId": "123", "subject": "주간 회의", "startedAt": "2026-10-22T10:00:00+09:00", "endedAt": "2026-10-22T11:00:00+09:00", "location": "4-5 회의실", "attendees": [{"id": "456", "type": "member"}]}

  • Whole day: {"calendarId": "123", "subject": "휴가", "startedAt": "2026-10-22+09:00", "endedAt": "2026-10-23+09:00", "wholeDayFlag": true}

  • Weekly: add "recurrenceRule": {"frequency": "weekly", "byday": "MO", "timezoneName": "Asia/Seoul"}

Returns: {id} of the created event.

Inputs: endedAt (required), subject (required), startedAt (required), calendarId (required), +9 more.

create-drive-folderA

Create a new folder in a Dooray drive.

Required:

  • driveId: The drive ID

  • folderId: Parent folder ID (where the new folder will be created)

  • name: Folder name

Example: { "driveId": "123", "folderId": "456", "name": "New Folder" }

Returns: ID of the created folder.

Inputs: name (required), driveId (required), folderId (required).

create-project-templateA

Create a new task template in a Dooray project.

Templates are pre-created task structures that help users quickly create tasks with predefined content.

Required Field:

  • templateName: The name of the template

Optional Fields:

  • users: Default assignees (to) and CC recipients

  • body: Default task body content (markdown or HTML)

  • guide: Instructions shown when creating tasks from this template

  • subject: Default task subject/title

  • dueDate: Default due date (ISO 8601 format)

  • dueDateFlag: Whether due date is enabled

  • milestoneId: Default milestone

  • tagIds: Default tags

  • priority: Default priority (highest, high, normal, low, lowest, none)

  • isDefault: Set as default template (auto-fills when creating new tasks)

Due Date Flags:

  • dueDateFlag: false → No schedule

  • dueDateFlag: true, dueDate: null → Schedule exists but date is TBD

  • dueDateFlag: true, dueDate: "2024-01-15T12:00:00+09:00" → Schedule with specific date

Examples:

  • Simple template: {"projectId": "123", "templateName": "Bug Report"}

  • With body: {"projectId": "123", "templateName": "Feature Request", "body": {"mimeType": "text/x-markdown", "content": "## Description\n\n## Expected Behavior\n\n## Steps to Reproduce"}}

  • With defaults: {"projectId": "123", "templateName": "Sprint Task", "priority": "normal", "tagIds": ["tag1"], "isDefault": true}

Returns the created template ID.

Inputs: projectId (required), templateName (required), body, guide, +8 more.

create-tagA

Create a new tag in a Dooray project.

Tag Types:

  1. Individual Tag: A standalone tag without a group

    • Example: {"name": "urgent", "color": "ff0000"}

  2. Group Tag: A tag belonging to a tag group (using "groupName:tagName" format)

    • Example: {"name": "Priority:High", "color": "ff0000"}

    • Example: {"name": "Priority:Medium", "color": "ffff00"}

    • Tags with the same group name prefix will be grouped together

Color Format:

  • 6-character hex color code without the # symbol

  • Examples: "ffffff" (white), "ff0000" (red), "c6eab3" (light green)

  • If not specified, a default color will be assigned

Response: Returns the created tag's ID:

{
  "id": "12345"
}

Tag Groups: After creating group tags, you can configure the group's behavior (mandatory, selectOne) using the update-tag-group tool.

Examples:

  • Individual tag: {"projectId": "123", "name": "Bug", "color": "ff0000"}

  • Group tag: {"projectId": "123", "name": "Type:Feature", "color": "00ff00"}

Inputs: name (required), projectId (required), color.

create-taskA

Create a new task (업무) in a Dooray project. Required: projectId, subject.

DRAFT vs REGULAR: ASK USER which type to create:

  • Draft (isDraft: true): Returns URL to continue editing in browser. Use for complex tasks or when user wants to review.

  • Regular (isDraft: false, default): Saves immediately. Use when all info is available.

INTERACTIVE WORKFLOW:

  1. Templates: Ask about get-project-template-list. If yes, use get-project-template for defaults.

  2. Content: Get subject and body. If no template and no body, ask user for details.

  3. Assignees/CC: Use get-my-member-info, get-project-member-list, or get-project-member-group-list. Format: {id, type: "member|group|email"}

  4. Tags: Call get-tag-list. CRITICAL: Check mandatory tag groups - must select or creation fails (500 error). selectOne=true requires exactly ONE tag from group.

Key Points:

Examples:

  • Draft: {"projectId": "123", "subject": "Bug fix", "isDraft": true}

  • Regular: {"projectId": "123", "subject": "Deploy", "assignees": [{"id": "user1", "type": "member"}], "tagIds": ["tag1"], "priority": "high"}

Returns: {id} (regular) or {id, url, message} (draft). For taskNumber, call get-task with includeBody false.

Inputs: subject (required), projectId (required), cc, body, +7 more.

create-task-commentA

Add a comment (댓글) to an existing Dooray task.

This tool creates a comment on a task, separate from editing the task body itself. Use this for:

  • Adding progress updates or status notes

  • Responding to questions or discussions

  • Logging information related to the task

  • Attaching files with context

When to Use:

  • create-task-comment: For adding discussion, updates, or notes (댓글)

  • update-task: For modifying the task description, title, or metadata

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId

  • Extract the second numeric ID as taskId

File Attachments:

Content Format:

  • Use "text/x-markdown" for markdown formatting (recommended)

  • Use "text/html" for rich HTML content

  • Body format: {"mimeType": "text/x-markdown", "content": "..."}

Examples:

  • Simple comment: { "projectId": "123456", "taskId": "789012", "body": {"mimeType": "text/x-markdown", "content": "Progress update: Completed initial implementation"} }

  • With markdown: { "projectId": "123456", "taskId": "789012", "body": { "mimeType": "text/x-markdown", "content": "## Test Results\n\n- ✅ All unit tests passing\n- ✅ Integration tests passed\n- ⏳ Performance testing in progress" } }

  • With file attachments: { "projectId": "123456", "taskId": "789012", "body": {"mimeType": "text/x-markdown", "content": "See attached screenshots"}, "attachFileIds": ["file123", "file456"] }

Returns: Created comment with ID.

Inputs: body (required), taskId (required), projectId (required), attachFileIds.

create-wiki-pageA

Create a new wiki page.

Required: wikiId, subject, content Optional: attachFileIds, referrers

IMPORTANT - parentPageId:

  • parentPageId is practically required for creating new pages

  • Without parentPageId, API returns 400 error ("입력한 내용에 오류가 있습니다")

  • To create a page, first use get-wiki-page-list to find the parent page (e.g., Home page)

  • Then provide that page's ID as parentPageId

Workflow:

  1. Call get-wiki-list to get wikiId

  2. Call get-wiki-page-list with wikiId to find parent page (usually "Home")

  3. Call create-wiki-page with parentPageId set to the Home page ID

Content is in markdown format. Returns: id, wikiId, parentPageId, version.

Inputs: wikiId (required), content (required), subject (required), referrers, +2 more.

create-wiki-page-commentB

Create a comment on a wiki page. Content is in markdown format. Returns: id.

Inputs: pageId (required), wikiId (required), content (required).

delete-attachmentA
Destructive

Delete a file attachment from a Dooray task.

Required Parameters:

  • projectId: The project ID

  • taskId: The task ID (post ID)

  • fileId: The file ID to delete (get from get-attachment-list)

Example: { "projectId": "123456", "taskId": "789012", "fileId": "abc123" }

Returns: Success message confirming deletion.

Note: This action is irreversible. The file will be permanently removed from the task.

Inputs: fileId (required), taskId (required), projectId (required).

delete-calendar-eventA
Destructive

Delete a Dooray calendar event (일정 삭제).

Recurring Events (deleteType):

  • this: Only this occurrence (default)

  • wholeFromThis: This and following occurrences

  • whole: All occurrences

For a recurring event, use the occurrence event ID from get-calendar-event-list.

Examples:

  • {"calendarId": "123", "eventId": "456"}

  • {"calendarId": "123", "eventId": "456", "deleteType": "whole"}

Returns: success message.

Inputs: eventId (required), calendarId (required), deleteType.

delete-drive-fileA
Destructive

Permanently delete a file from a Dooray drive trash.

Important: The file must already be in the trash folder. To move a file to trash first, use move-drive-file with destinationFileId="trash".

Required:

  • driveId: The drive ID

  • fileId: File ID to permanently delete

Example: { "driveId": "123", "fileId": "456" }

Inputs: fileId (required), driveId (required).

delete-project-templateA
Destructive

Delete an existing task template from a Dooray project.

CAUTION: This action cannot be undone. Make sure you want to permanently delete the template.

Required Fields:

  • projectId: Project ID where the template belongs

  • templateId: Template ID to delete

How to get template IDs: Use the get-project-template-list tool to list all templates and get their IDs.

Example:

  • Delete template: {"projectId": "123456", "templateId": "789012"}

Returns success status.

Inputs: projectId (required), templateId (required).

delete-task-commentA
Destructive

Delete a comment (댓글) on a Dooray task. This cannot be undone.

Confirm the target with get-task-comment before deleting.

Examples:

  • {"projectId": "123", "taskId": "456", "commentId": "789"}

Returns: success message.

Inputs: taskId (required), commentId (required), projectId (required).

delete-wiki-pageA
Destructive

Delete a wiki page (위키 페이지 삭제).

Confirm the target with get-wiki-page before deleting, and check child pages with get-wiki-page-tree.

Inputs: pageId (required), wikiId (required).

delete-wiki-page-commentC
Destructive

Delete a comment on a wiki page.

Inputs: pageId (required), wikiId (required), commentId (required).

delete-wiki-page-fileA
Destructive

Delete a file attached to a Dooray wiki page.

Required Parameters:

  • wikiId: The wiki ID

  • pageId: The wiki page ID

  • fileId: The file ID to delete (get from wiki page detail API: $.result.files.id or $.result.images.id)

Example: { "wikiId": "123456", "pageId": "789012", "fileId": "abc123" }

Returns: Success message confirming deletion.

Note: This action is irreversible. The file will be permanently removed from the wiki page.

Inputs: fileId (required), pageId (required), wikiId (required).

download-all-attachmentsA

Download every file attached to a Dooray task into a local directory (첨부 일괄 다운로드).

Files are saved with their original names. Existing files are not overwritten unless overwrite is true. If some files fail, the others are still downloaded and the result lists both succeeded and failed files.

Examples:

  • {"projectId": "123", "taskId": "456", "saveDir": "/tmp/task-456/"}

Returns: count, succeeded [{fileId, savedTo, size}], failed [{fileId, name, error}].

Inputs: taskId (required), saveDir (required), projectId (required), overwrite.

download-attachmentA

Download a file attachment from a Dooray task.

Required Parameters:

  • projectId: The project ID

  • taskId: The task ID (post ID)

  • fileId: The file ID (get from get-attachment-list)

Optional:

  • savePath: Local path to save the file. Can be a directory (filename auto-detected) or full file path. Recommended for large files.

Examples:

  • Save to file: { "projectId": "123", "taskId": "456", "fileId": "789", "savePath": "/tmp/downloads/" }

  • Base64 (small files): { "projectId": "123", "taskId": "456", "fileId": "789" }

Response Fields:

  • success: Whether download succeeded

  • fileId: The file ID

  • filename: Original filename

  • contentType: MIME type of the file

  • contentLength: File size in bytes

  • savedTo: (when savePath used) Local path where file was saved

  • base64Data: (when savePath omitted) Base64 encoded file content

Inputs: fileId (required), taskId (required), projectId (required), savePath.

download-drive-fileA

Download a file from a Dooray drive.

Required:

  • driveId: The drive ID

  • fileId: The file ID to download

Optional:

  • savePath: Local path to save the file. Can be a directory (filename auto-detected) or full file path. Recommended for large files.

Examples:

  • Save to file: { "driveId": "123", "fileId": "456", "savePath": "/tmp/downloads/" }

  • Save with name: { "driveId": "123", "fileId": "456", "savePath": "/tmp/myfile.pdf" }

  • Base64 (small files): { "driveId": "123", "fileId": "456" }

Tip: If you only have a file ID, use get-drive-file-meta first to get the driveId.

Inputs: fileId (required), driveId (required), savePath.

download-wiki-attach-fileA

Download a file from a Dooray wiki using attach file ID.

Required Parameters:

  • wikiId: The wiki ID

  • attachFileId: The attach file ID (get from wiki page detail API: $.result.files.attachFileId or $.result.images.attachFileId)

Optional:

  • savePath: Local path to save the file. Can be a directory (filename auto-detected) or full file path. Recommended for large files.

Examples:

  • Save to file: { "wikiId": "123", "attachFileId": "456", "savePath": "/tmp/downloads/" }

  • Base64 (small files): { "wikiId": "123", "attachFileId": "456" }

Note: The attachFileId is different from fileId. Use this endpoint when you have an attachFileId from the page detail API's $.result.files.attachFileId or $.result.images.attachFileId field.

Inputs: wikiId (required), attachFileId (required), savePath.

download-wiki-page-fileA

Download a file attached to a Dooray wiki page.

Required Parameters:

  • wikiId: The wiki ID

  • pageId: The wiki page ID

  • fileId: The file ID (get from wiki page detail API: $.result.files.id or $.result.images.id)

Optional:

  • savePath: Local path to save the file. Can be a directory (filename auto-detected) or full file path. Recommended for large files.

Examples:

  • Save to file: { "wikiId": "123", "pageId": "456", "fileId": "789", "savePath": "/tmp/downloads/" }

  • Base64 (small files): { "wikiId": "123", "pageId": "456", "fileId": "789" }

Response Fields:

  • success: Whether download succeeded

  • fileId: The file ID

  • filename: Original filename

  • contentType: MIME type of the file

  • contentLength: File size in bytes

  • savedTo: (when savePath used) Local path where file was saved

  • base64Data: (when savePath omitted) Base64 encoded file content

Inputs: fileId (required), pageId (required), wikiId (required), savePath.

get-attachment-listB
Read-onlyIdempotent

Get list of file attachments for a Dooray task.

Required Parameters:

  • projectId: The project ID

  • taskId: The task ID (post ID)

Note: This API returns only "general" type files attached to the task.

Example: { "projectId": "123456", "taskId": "789012" }

Returns: List of attachments with id, name, size, mimeType, createdAt, and creator info.

Response Fields:

  • totalCount: Total number of files

  • data[]: Array of file objects

    • id: File ID

    • name: File name

    • size: File size

    • mimeType: MIME type

    • createdAt: Creation timestamp (ISO-8601)

    • creator: Creator info (type, member.organizationMemberId)

Inputs: taskId (required), projectId (required).

get-attachment-metadataA
Read-onlyIdempotent

Get metadata of a specific file attachment in a Dooray task.

Required Parameters:

  • projectId: The project ID

  • taskId: The task ID (post ID)

  • fileId: The file ID (get from get-attachment-list)

Example: { "projectId": "123456", "taskId": "789012", "fileId": "abc123" }

Returns: File metadata including id, name, size, mimeType, createdAt, and creator info.

Response Fields:

  • id: File ID

  • name: File name

  • size: File size

  • mimeType: MIME type

  • createdAt: Creation timestamp (ISO-8601)

  • creator: Creator info (type, member.organizationMemberId)

Note: This returns metadata only, not the file content. Use download-attachment to get the actual file.

Inputs: fileId (required), taskId (required), projectId (required).

get-calendar-eventA
Read-onlyIdempotent

Get details of a Dooray calendar event (일정 상세).

Both calendarId and eventId are required. Take them from get-calendar-event-list (calendar.id and id).

Examples:

  • {"calendarId": "123", "eventId": "456"}

Returns: event with body, users (from = organizer, to = attendees, cc) and each attendee status (accepted, declined, tentative, not_confirmed), recurrenceRule and files.

Inputs: eventId (required), calendarId (required).

get-calendar-event-listA
Read-onlyIdempotent

Get Dooray calendar events (일정 목록) in a time range.

Required: timeMin (inclusive) and timeMax (exclusive). The range must be 1 year or less.

The list does not include event body or attendees. Use get-calendar-event for details. Subscription calendars are not included.

Filters:

  • calendars: Calendar IDs from get-calendar-list (default: all calendars)

  • postType: toMe (I am an attendee), toCcMe (attendee or CC), fromToCcMe (organizer, attendee or CC)

  • category: general (일반 일정), post (업무 마감일), milestone

Examples:

  • Today: {"timeMin": "2026-10-22T00:00:00+09:00", "timeMax": "2026-10-23T00:00:00+09:00"}

  • This month in one calendar: {"timeMin": "2026-10-01T00:00:00+09:00", "timeMax": "2026-11-01T00:00:00+09:00", "calendars": ["123"]}

Returns: events with id, calendar {id, name}, subject, startedAt, endedAt, wholeDayFlag, location, category, recurrenceType.

Inputs: timeMax (required), timeMin (required), category, postType, +1 more.

get-calendar-listA
Read-onlyIdempotent

Get the list of Dooray calendars (캘린더 목록) the user can access.

Subscription calendars are not included. The calendar marked default=true is the user's own default calendar.

Use the returned calendar id for create-calendar-event, or to filter get-calendar-event-list.

Examples:

  • {} (first 20 calendars)

  • {"size": 100}

Returns: totalCount and calendars with id, name, type (private, project), default, role.

Inputs: page, size.

get-drive-file-listA
Read-onlyIdempotent

Get list of files and folders in a Dooray drive.

Required: driveId Optional: parentId (use "root" for top-level), type filter, pagination

Examples:

  • Top-level: { "driveId": "123", "parentId": "root" }

  • Subfolder: { "driveId": "123", "parentId": "456" }

  • Only folders: { "driveId": "123", "parentId": "root", "type": "folder" }

  • With pagination: { "driveId": "123", "parentId": "root", "page": 0, "size": 20 }

Returns: file/folder ID, name, type, size, dates, creator info.

Inputs: driveId (required), page, size, type, +2 more.

get-drive-file-metaA
Read-onlyIdempotent

Get file metadata by file ID (without needing drive ID).

Required: fileId

Returns: file ID, driveId, name, version, type, subType, mimeType, size, creator, parent info.

Note: Use the returned driveId for download or other operations that require it.

Inputs: fileId (required).

get-drive-listA
Read-onlyIdempotent

Get list of accessible Dooray drives.

Drive Types:

  • private: Personal drive (default)

  • project: Project drives (use scope to filter private/public projects)

Examples:

  • Personal drive: { "type": "private" }

  • Project drives: { "type": "project", "scope": "private" }

  • Public project drives: { "type": "project", "scope": "public" }

Returns: drive ID, name, type, and associated project info.

Inputs: type, scope, state, projectId.

get-memberA
Read-onlyIdempotent

Get details of a Dooray organization member (멤버 상세).

Use the organizationMemberId found in task assignees, comment creators, calendar attendees, or get-member-list results.

Examples:

  • {"memberId": "1234567890123456789"}

Returns: id, name, userCode, externalEmailAddress, englishName, nickname, locale, timezoneName and more.

Inputs: memberId (required).

get-member-listA
Read-onlyIdempotent

Search members across the whole Dooray organization (조직 전체 멤버 검색).

Unlike get-project-member-list, this is not limited to one project. Use it to find the organizationMemberId of someone outside the project (e.g. to add them as CC by email or member ID).

Search Conditions (combine as needed):

  • name: Member name

  • userCode: User ID, like match

  • userCodeExact: User ID, exact match

  • externalEmailAddresses: Email addresses, exact match only (not a like search)

  • idProviderUserId: SSO user ID (e.g. employee number)

Examples:

  • By name: {"name": "홍길동"}

  • By email: {"externalEmailAddresses": ["user@example.com"]}

  • By user ID: {"userCodeExact": "gildong.hong"}

Returns: totalCount and members with id (organizationMemberId), name, userCode, externalEmailAddress. Use get-member for full details.

Inputs: name, page, size, userCode, +3 more.

get-milestone-listA
Read-onlyIdempotent

Get list of milestones for a project.

Milestones are used to organize and track tasks by release or sprint. This tool retrieves all milestones in a project.

Note: Returns compact response with essential fields only.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Examples:

  • Get all milestones: {"projectId": "123456"}

  • Get only open milestones: {"projectId": "123456", "status": "open"}

  • Get only closed milestones: {"projectId": "123456", "status": "closed"}

Returns an array of milestones with id, name, and status. Use milestone IDs when creating or updating tasks.

Inputs: projectId (required), status.

get-my-member-infoA
Read-onlyIdempotent

Get information about the authenticated user.

This tool retrieves your Dooray member profile using your API token. Most importantly, it returns your member ID which is needed for other operations like filtering tasks by assignee.

No parameters needed - it automatically uses your authentication token.

Examples:

  • Get my info: {} (empty parameters)

  • "What's my Dooray member ID?"

  • "Show my Dooray profile"

Returns your complete member profile including:

  • id: Your member ID (important for task queries)

  • name, email, organization

  • locale, timezone settings

  • display preferences

This is often the first tool to call to get your member ID for use in other tools like list-tasks.

Inputs: no named parameters.

get-projectA
Read-onlyIdempotent

Get detailed information about a specific Dooray project.

This tool retrieves complete details of a single project including its configuration, scope, organization, and category information.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID" or "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

IMPORTANT: When a specific project URL is provided, use this tool directly instead of calling get-project-list first.

Examples:

Returns project information including:

  • id, code, name: Basic project identifiers

  • description: Project description

  • scope: private or public

  • organizationId: Organization this project belongs to

  • projectCategoryId: Category ID (null if no category)

  • projectType: default, task, or issue

  • state: active or archived

Use this to get full details about a specific project when you have its project ID or URL.

Inputs: projectId (required).

get-project-listA
Read-onlyIdempotent

Get list of active projects that you belong to.

This tool retrieves only active projects where you are a member. Archived projects are excluded.

Note: Returns compact response with essential fields only. For complete project details, use get-project.

IMPORTANT: When the user provides a specific Dooray URL (e.g., "https://nhnent.dooray.com/task/PROJECT_ID"), do NOT use this tool. Instead, extract the PROJECT_ID from the URL and call get-project directly to get information about that specific project.

This tool is for browsing your active projects when no specific project URL or ID is provided.

Examples:

  • Get all your active projects: {} (empty parameters)

  • Get second page with 50 items: {"page": 1, "size": 50}

Returns a paginated list with project id and name (project code) for each project.

Inputs: page, size.

get-project-member-group-listA
Read-onlyIdempotent

Get list of member groups in a project.

Member groups are collections of members that can be assigned to tasks as a group. This tool retrieves all member groups configured in a project.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

Note: Returns compact response with essential fields only (id and code).

Examples:

  • Get all member groups: {"projectId": "123456"}

  • Get with pagination: {"projectId": "123456", "page": 0, "size": 50}

Returns a paginated response with totalCount and array of member groups containing:

  • id: Member group ID

  • code: Member group name/code

Use this tool to find member groups for assigning tasks to groups of members.

Inputs: projectId (required), page, size.

get-project-member-listA
Read-onlyIdempotent

Get list of members in a project with their details.

This tool fetches project members and enriches each member with detailed information including name and email address.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Role Filtering:

  • Optionally filter by roles: ["admin"], ["member"], or ["admin", "member"]

  • If not specified, returns all members regardless of role

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

Note: Returns compact response with essential fields only (id, name, externalEmailAddress).

Examples:

  • Get all members: {"projectId": "123456"}

  • Get only admins: {"projectId": "123456", "roles": ["admin"]}

  • Get with pagination: {"projectId": "123456", "page": 0, "size": 50}

Returns a paginated response with totalCount and array of members containing:

  • id: Member ID (organizationMemberId)

  • name: Member's display name

  • externalEmailAddress: Member's email address

Use this tool to find project members for assigning tasks or understanding team composition.

Inputs: projectId (required), page, size, roles.

get-project-templateA
Read-onlyIdempotent

Get detailed information about a specific project template.

This tool retrieves complete template details including body, guide, subject, users, tags, and milestone. The returned data is intended for creating new tasks from templates.

IMPORTANT - Full Details Returned: This tool returns ALL template fields (not filtered) because:

  • Template data will be used for creating new tasks

  • Need body, guide, subject, users, tags, milestone for task creation

  • This is a detail view, not a list view

Template Macros: Template macros like ${year}, ${month}, etc. are returned as-is (not interpolated). These can be processed when creating tasks if needed.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

How to get template IDs: Use the get-project-template-list tool to list all templates in a project and get their IDs.

Examples:

  • Get template details: {"projectId": "123456", "templateId": "789012"}

  • "Show me details of template 789012 in project 123456"

Returns complete template information including:

  • id: Template ID

  • templateName: Template name

  • project: Project info (id, code)

  • body: Template body with mimeType and content (markdown or HTML)

  • guide: Template guide/instructions with mimeType and content

  • subject: Default task subject

  • users: Default assignees (to) and CC

  • tags: Default tag IDs

  • milestone: Default milestone (id, name)

  • priority: Default priority level

  • dueDate, dueDateFlag: Default due date settings

  • isDefault: Whether this is the default template

Use this tool to get full template details before creating a new task from the template.

Inputs: projectId (required), templateId (required).

get-project-template-listA
Read-onlyIdempotent

Get list of project task templates.

Templates are pre-created task structures with predefined title and body content. This tool retrieves all available templates in a project.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Note: Returns compact response with essential fields only (id and templateName).

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

  • Set size parameter to control items per page (max: 100)

Examples:

  • Get all templates (first page): {"projectId": "123456"}

  • Get second page: {"projectId": "123456", "page": 1, "size": 20}

  • Get with custom page size: {"projectId": "123456", "page": 0, "size": 50}

Returns a paginated response with totalCount and an array of templates containing id and templateName.

Templates help users quickly create tasks with predefined structure and content, useful for common task types like bug reports, feature requests, or documentation tasks.

Inputs: projectId (required), page, size.

get-project-workflow-listA
Read-onlyIdempotent

Get list of workflow statuses (업무 상태) for a project.

Workflows represent the task statuses available in a project. There are four workflow classes:

  • backlog: 대기 (waiting/backlog)

  • registered: 등록/할 일 (registered/to-do)

  • working: 진행 중 (in progress)

  • closed: 완료 (completed/done)

Each project may have custom workflows within these classes. Use workflow IDs when creating or updating tasks (e.g., in create-task or update-task tools).

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the numeric ID after "/task/") and use it as the projectId parameter.

Examples:

  • Get all workflows: {"projectId": "1769381697328002548"}

Returns: Array of workflows with id, name, order, and class.

Inputs: projectId (required).

get-tagA
Read-onlyIdempotent

Get details of a specific tag in a Dooray project.

Response Format:

{
  "id": "12345",
  "name": "Priority:High",
  "color": "ff0000",
  "tagGroup": {
    "id": "group123",
    "name": "Priority",
    "mandatory": true,
    "selectOne": true
  }
}

Response Fields:

  • id: Tag ID

  • name: Tag name (includes group prefix if it's a group tag)

  • color: Hex color code without #

  • tagGroup: Tag group information (null for individual tags)

    • id: Group ID

    • name: Group name

    • mandatory: If true, at least one tag from this group is required when creating tasks

    • selectOne: If true, exactly one tag must be selected; if false, multiple tags can be selected

Examples:

  • Get tag: {"projectId": "123", "tagId": "456"}

Use Cases:

  • Check tag details before assigning to a task

  • Verify tag group settings (mandatory, selectOne)

  • Get tag color and group information

Inputs: tagId (required), projectId (required).

get-tag-listA
Read-onlyIdempotent

Get list of tags for a project, grouped by tag groups.

Tags are used to categorize and label tasks. This tool retrieves all available tags organized by their tag groups for better clarity.

Response Format: Returns tags grouped by their tagGroup:

{
  "tagGroups": [
    {
      "id": "group1",
      "name": "Type",
      "mandatory": true,
      "selectOne": true,
      "tags": [
        { "id": "tag1", "name": "Bug" },
        { "id": "tag2", "name": "Feature" }
      ]
    }
  ]
}

CRITICAL - Mandatory Tag Groups: When creating/updating tasks, you MUST include tags from all mandatory tag groups:

  • mandatory: true - At least one tag from this group is required

  • selectOne: true - Exactly ONE tag must be selected from this group

  • selectOne: false - One OR MORE tags must be selected from this group

Failing to provide required tags will result in a 500 error.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Pagination:

  • Default page size is 100 (maximum) to retrieve all tags

  • Use page parameter to get additional pages if totalCount > 100

Examples:

  • Get all tags: {"projectId": "123456"}

  • Get second page: {"projectId": "123456", "page": 1, "size": 100}

Use tag IDs when creating or updating tasks with create-task or update-task tools.

Inputs: projectId (required), page, size.

get-taskA
Read-onlyIdempotent

Get detailed information about a specific task.

This tool retrieves complete details of a task including its full body content, attachments, workflow status, assignees, and all metadata.

URL Pattern Recognition - Two formats supported:

  1. Project-scoped URL: "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID"

  2. Task-only URL: "https://nhnent.dooray.com/project/tasks/TASK_ID"

IMPORTANT:

  • taskId is REQUIRED, projectId is OPTIONAL

  • The taskId is the unique identifier (ID) from the URL, NOT the sequential task number shown in the UI

  • You can fetch task details with just the taskId without knowing the projectId

  • When a specific task URL is provided, use this tool directly instead of calling get-project-list first

  • To find taskId from task descriptions, use get-task-list to search and get task IDs

  • Bodies can exceed 50,000 characters. When you only need status, assignees, number or dates, set includeBody to false

Examples:

  • From URL pattern 1: {"taskId": "4206132384174602537", "projectId": "1769381697328002548"}

  • From URL pattern 2: {"taskId": "4206132384174602537"}

  • Just taskId: {"taskId": "789012345"}

  • With both IDs: {"taskId": "789012345", "projectId": "123456"}

  • Without body: {"taskId": "789012345", "includeBody": false}

Returns complete task information including:

  • Basic info: id, number, subject, taskNumber (PROJECT-CODE/NUMBER format)

  • Project: project object with id and code

  • Status: workflowClass (registered/working/closed), workflow (id and name), closed flag, priority

  • Dates: createdAt, updatedAt, dueDate, dueDateFlag

  • Content: body with mimeType (text/x-markdown or text/html) and content. With includeBody false: mimeType and contentLength

  • Hierarchy: parent task information (id, number, subject) if this is a subtask

  • People: users object with from (creator), to (assignees), cc (watchers)

  • Organization: milestone (id, name), tags array (id only, use get-tag for names)

  • Files: fileIdList (attachment IDs, use get-attachment-list for names and sizes)

Inputs: taskId (required), projectId, includeBody.

get-task-commentA
Read-onlyIdempotent

Get a single comment (댓글) on a Dooray task with its full body.

Use the comment ID from get-task-comment-list. Call this before update-task-comment to get the current body.

Examples:

  • {"projectId": "123", "taskId": "456", "commentId": "789"}

Returns: comment with id, type, subtype, createdAt, creator, body {mimeType, content}, files.

Inputs: taskId (required), commentId (required), projectId (required).

get-task-comment-listA
Read-onlyIdempotent

Get list of comments (댓글) on a specific Dooray task.

This tool fetches all comments that have been added to a task. Comments are discussions, updates, or notes added by team members.

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId (if present)

  • Extract the second numeric ID (or the ID after "/tasks/") as taskId

IMPORTANT: Both projectId and taskId are REQUIRED.

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

Sorting:

  • Default: createdAt (oldest comments first)

  • Use "-createdAt" to get newest comments first

Note: Returns filtered response with essential fields only (id, creator, body).

Examples:

  • Get all comments (first page): {"projectId": "123456", "taskId": "789012"}

  • Get newest comments first: {"projectId": "123456", "taskId": "789012", "order": "-createdAt"}

  • Get second page: {"projectId": "123456", "taskId": "789012", "page": 1, "size": 20}

Returns a paginated response with totalCount and array of comments containing:

  • id: Comment ID

  • creator: Who wrote the comment (member or emailUser)

    • For members: {"type": "member", "member": {"organizationMemberId": "..."}}

    • For email users: {"type": "emailUser", "emailUser": {"emailAddress": "...", "name": "..."}}

  • body: Comment content with mimeType and content

Use this tool to view discussion history, progress updates, or notes on a task.

Inputs: taskId (required), projectId (required), page, size, +1 more.

get-task-listA
Read-onlyIdempotent

Get list of tasks in a Dooray project with powerful filtering and sorting.

IMPORTANT: projectId is REQUIRED. This tool fetches tasks from a specific project.

Note: Returns compact response with essential fields only. For complete task details, use get-task.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID" or "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter. When a URL is provided, use get-project for project info instead of get-project-list.

Member ID Filters (use organizationMemberId from get-my-member-info):

  • toMemberIds: Tasks assigned to specific members

  • ccMemberIds: Tasks where members are in CC

  • fromMemberIds: Tasks created by specific members

Workflow Filters:

  • postWorkflowClasses: ["backlog", "registered", "working", "closed"]

  • postWorkflowIds: Project-specific workflow IDs

Date Filters (flexible patterns):

  • "today" - Today's tasks

  • "thisweek" - This week's tasks

  • "prev-7d" - Last 7 days

  • "next-7d" - Next 7 days

  • ISO8601 range: "2021-01-01T00:00:00+09:00~2021-01-10T00:00:00+09:00"

Examples:

  1. All tasks in project: {"projectId": "123456"}

  2. Tasks assigned to me: {"projectId": "123456", "toMemberIds": ["my-org-member-id"]}

  3. Tasks in "working" status: {"projectId": "123456", "postWorkflowClasses": ["working"]}

  4. Tasks due today: {"projectId": "123456", "dueAt": "today"}

  5. Recent tasks (sorted by update time): {"projectId": "123456", "updatedAt": "prev-7d", "order": "-postUpdatedAt"}

  6. Tasks with specific milestone and tags: {"projectId": "123456", "milestoneIds": ["milestone123"], "tagIds": ["tag456"]}

Sorting:

  • Default: Tasks are sorted by most recently updated first (-postUpdatedAt)

  • Custom: Use order parameter with: postDueAt, postUpdatedAt, createdAt

  • Prefix with - for descending (e.g., "-createdAt")

Title search: subjects matches part of the task title only. Body and comments are not searched, so 0 results does not mean no task mentions the keyword.

Returns totalCount and tasks with id, number, subject, workflowClass, priority, milestone, tags (id only), createdAt, updatedAt. Assignees, CC and dueDate are not included: use get-task.

Inputs: projectId (required), page, size, dueAt, +14 more.

get-wiki-listA
Read-onlyIdempotent

Get list of accessible wikis.

Wiki vs WikiPage:

  • Wiki is a container that groups related wiki pages together (similar to how Project groups Tasks)

  • Each wiki has a home page and can contain multiple wiki pages in a tree structure

  • Use get-wiki-page-list to get pages within a specific wiki

Returns: wiki ID, name, project, type, scope, and home page ID.

Inputs: page, size.

get-wiki-pageA
Read-onlyIdempotent

Get wiki page details including body content.

Two API endpoints supported:

  1. With pageId only: GET /wiki/v1/pages/{page-id}

  2. With wikiId + pageId: GET /wiki/v1/wikis/{wiki-id}/pages/{page-id}

Returns: id, wikiId, version, subject, body (mimeType, content), creator, referrers, files, images.

Inputs: pageId (required), wikiId.

get-wiki-page-commentA
Read-onlyIdempotent

Get a specific comment on a wiki page. Returns: id, page, createdAt, modifiedAt, creator, body.

Inputs: pageId (required), wikiId (required), commentId (required).

get-wiki-page-comment-listA
Read-onlyIdempotent

Get comments on a wiki page. Returns newest first. Each comment has: id, page, createdAt, modifiedAt, creator, body.

Inputs: pageId (required), wikiId (required), page, size.

get-wiki-page-listA
Read-onlyIdempotent

Get wiki pages at one depth level (siblings). Use parentPageId to get child pages, omit for root pages.

Inputs: wikiId (required), parentPageId.

get-wiki-page-treeA
Read-onlyIdempotent

Get the wiki page hierarchy as a tree (위키 페이지 트리).

get-wiki-page-list returns only one level. This tool walks down the levels and returns nested {id, subject, children}. Each level costs one API call per page, so keep depth small for large wikis. The walk stops at 500 pages (truncated=true).

Examples:

  • Top 3 levels: {"wikiId": "123"}

  • Under a page, 2 levels: {"wikiId": "123", "parentPageId": "456", "depth": 2}

Inputs: wikiId (required), depth, parentPageId.

move-drive-fileA
Destructive

Move a file or folder in a Dooray drive.

Required:

  • driveId: The drive ID

  • fileId: File or folder ID to move

  • destinationFileId: Target folder ID, or "trash" to move to trash

Examples:

  • Move to folder: { "driveId": "123", "fileId": "456", "destinationFileId": "789" }

  • Move to trash: { "driveId": "123", "fileId": "456", "destinationFileId": "trash" }

Note: To permanently delete, first move to trash, then use delete-drive-file.

Inputs: fileId (required), driveId (required), destinationFileId (required).

move-wiki-pageA
Destructive

Move a wiki page (위키 페이지 이동).

Moves the page under another parent page, into another wiki (targetWikiId), or changes its order among siblings (beforePageId). Child pages move together by default. Set withChildren=false to move only this page.

Examples:

  • Change parent: {"wikiId": "123", "pageId": "456", "targetParentPageId": "789"}

  • Move only this page: {"wikiId": "123", "pageId": "456", "targetParentPageId": "789", "withChildren": false}

  • Move to the top of siblings: {"wikiId": "123", "pageId": "456", "targetParentPageId": "789", "beforePageId": "0"}

Inputs: pageId (required), wikiId (required), targetParentPageId (required), beforePageId, +2 more.

rename-drive-fileC
Destructive

Rename a file or folder in a Dooray drive.

Required:

  • driveId: The drive ID

  • fileId: File or folder ID to rename

  • name: New name

Example: { "driveId": "123", "fileId": "456", "name": "new-name.txt" }

Inputs: name (required), fileId (required), driveId (required).

update-calendar-eventA
Destructive

Update a Dooray calendar event (일정 수정).

Only the fields you provide are changed. Unprovided fields keep their current values.

IMPORTANT:

  • attendees and cc REPLACE the current lists. Call get-calendar-event first and include existing attendees you want to keep

  • When changing time, provide both startedAt and endedAt

Examples:

  • Change time: {"calendarId": "123", "eventId": "456", "startedAt": "2026-10-22T14:00:00+09:00", "endedAt": "2026-10-22T15:00:00+09:00"}

  • Change location: {"calendarId": "123", "eventId": "456", "location": "7층 회의실"}

Returns: success message.

Inputs: eventId (required), calendarId (required), cc, body, +10 more.

update-drive-fileA
Destructive

Upload a new version of an existing file in a Dooray drive.

Required:

  • driveId: The drive ID

  • fileId: The file ID to update

  • filePath: Absolute path to the new version of the file

Example: { "driveId": "123", "fileId": "456", "filePath": "/Users/name/updated-document.pdf" }

Returns: File ID and new version number.

Note: This replaces the file content with a new version. The file must exist at the specified path.

Inputs: fileId (required), driveId (required), filePath (required).

update-project-templateA
Destructive

Update an existing task template in a Dooray project.

Required Fields:

  • projectId: Project ID where the template belongs

  • templateId: Template ID to update

  • templateName: Template name (required even for updates)

Optional Fields:

  • users: Default assignees (to) and CC recipients

  • body: Default task body content (markdown or HTML)

  • guide: Instructions shown when creating tasks from this template

  • subject: Default task subject/title

  • dueDate: Default due date (ISO 8601 format)

  • dueDateFlag: Whether due date is enabled

  • milestoneId: Default milestone

  • tagIds: Default tags

  • priority: Default priority (highest, high, normal, low, lowest, none)

  • isDefault: Set as default template (auto-fills when creating new tasks)

How to get template IDs: Use the get-project-template-list tool to list all templates and get their IDs.

Examples:

  • Update name: {"projectId": "123", "templateId": "456", "templateName": "Updated Bug Report"}

  • Update body: {"projectId": "123", "templateId": "456", "templateName": "Bug Report", "body": {"mimeType": "text/x-markdown", "content": "## New Format"}}

  • Set as default: {"projectId": "123", "templateId": "456", "templateName": "Main Template", "isDefault": true}

Returns success status.

Inputs: projectId (required), templateId (required), templateName (required), body, +9 more.

update-tag-groupA
Destructive

Update tag group settings in a Dooray project.

Tag Group Settings:

  • mandatory: When true, at least one tag from this group must be assigned when creating/updating tasks

  • selectOne: When true, exactly ONE tag from this group can be selected. When false, multiple tags can be selected

Common Configurations:

  1. Required single selection (e.g., Priority, Status): {"mandatory": true, "selectOne": true}

    • User MUST select exactly one tag

  2. Required multiple selection (e.g., Categories, Skills): {"mandatory": true, "selectOne": false}

    • User MUST select at least one tag, can select multiple

  3. Optional single selection: {"mandatory": false, "selectOne": true}

    • User can optionally select one tag

  4. Optional multiple selection (default): {"mandatory": false, "selectOne": false}

    • User can optionally select multiple tags

Finding Tag Group ID: Use get-tag-list to find tags and their tagGroup information:

{
  "tagGroup": {
    "id": "group123",  // Use this as tagGroupId
    "name": "Priority",
    "mandatory": false,
    "selectOne": false
  }
}

Examples:

  • Make group required with single selection: {"projectId": "123", "tagGroupId": "group456", "mandatory": true, "selectOne": true}

  • Allow multiple selections: {"projectId": "123", "tagGroupId": "group456", "selectOne": false}

Note: Only provide the settings you want to change. Omitted settings will not be modified.

Inputs: projectId (required), tagGroupId (required), mandatory, selectOne.

update-taskA
Destructive

Update an existing task in a Dooray project.

Only provide the fields you want to change. Fields you leave out keep their current values, so get-task is not needed first.

Fields:

  • Assignees, CC: assignees and cc each REPLACE that list. Passing only one of them keeps the other list. addAssignees, removeAssignees, addCc, removeCc change only the members you list. Do not combine add/remove options with assignees or cc

    • Member options: get-my-member-info, get-project-member-list, get-project-member-group-list. Format {"id": "...", "type": "member|group|email"} ("member": organizationMemberId, "group": group id, "email": email address)

  • Tags: tagIds REPLACES all tags. addTagIds, removeTagIds change only the tags you list. Do not combine them with tagIds

    • Check get-tag-list first: tags from every mandatory tag group (tagGroup.mandatory=true) must remain or the update fails with 500. tagGroup.selectOne=true allows exactly one tag from that group

  • Workflow: workflowId from get-project-workflow-list. Classes: backlog (대기), registered (등록/할 일), working (진행 중), closed (완료)

  • Parent (상위 업무): parentPostId. A task that already has sub-tasks cannot be set as a parent

  • Korean Terms: "to" = 담당자 (assignee), "cc" = 참조 (reference)

  • Priority: Use "none" to remove priority

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId

  • Extract the second numeric ID as taskId

Examples:

  • Change priority: {"projectId": "123", "taskId": "42", "priority": "high"}

  • Replace assignees, keep CC: {"projectId": "123", "taskId": "42", "assignees": [{"id": "user123", "type": "member"}]}

  • Change status: {"projectId": "123", "taskId": "42", "workflowId": "ID from get-project-workflow-list"}

  • Update tags: {"projectId": "123", "taskId": "42", "tagIds": ["tag1", "tag2"]}

  • Clear milestone: {"projectId": "123", "taskId": "42", "milestoneId": null}

  • Set parent task: {"projectId": "123", "taskId": "42", "parentPostId": "99"}

  • Add a CC, keep others: {"projectId": "123", "taskId": "42", "addCc": [{"id": "user456", "type": "member"}]}

  • Add and remove tags: {"projectId": "123", "taskId": "42", "addTagIds": ["tag3"], "removeTagIds": ["tag1"]}

Returns: Updated task. The body is returned as mimeType and contentLength. Use get-task to read the body.

Inputs: taskId (required), projectId (required), cc, body, +14 more.

update-task-bodyA
Destructive

Replace part of a task body (업무 본문 일부 치환).

Use this instead of update-task when only a few spots in a long body change. It reads the current body, replaces oldText with newText, and saves it with the same mimeType. The rest of the body (including inline images and file links) stays as it is.

Rules:

  • oldText must match the current body exactly (copy it from get-task)

  • Fails if oldText is not found

  • Fails if oldText appears more than once, unless replaceAll is true. Add surrounding text to make it unique

Examples:

  • {"projectId": "123", "taskId": "456", "oldText": "2. 배포", "newText": "2. 카나리 배포"}

  • {"projectId": "123", "taskId": "456", "oldText": "TODO", "newText": "완료", "replaceAll": true}

Returns: replacedCount and the body mimeType.

Inputs: taskId (required), newText (required), oldText (required), projectId (required), +1 more.

update-task-commentA
Destructive

Update an existing comment (댓글) on a Dooray task.

This tool modifies the content or attachments of an existing task comment.

IMPORTANT LIMITATION: Comments created from incoming emails CANNOT be modified. Only regular comments can be updated.

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId (if present)

  • Extract the second numeric ID (or the ID after "/tasks/") as taskId

  • Use get-task-comment-list to find the comment ID you want to update

REQUIRED: projectId, taskId, and commentId are all required.

Optional Parameters: You can provide either body, attachFileIds, or both. If you only want to update the text, just provide body. If you only want to update attachments, just provide attachFileIds.

File Attachments:

Workflow:

  1. Use get-task-comment-list to find the comment you want to update and get its ID

  2. Call update-task-comment with the comment ID and new content/attachments

  3. The comment will be modified immediately

Content Format:

  • Use "text/x-markdown" for markdown formatting (recommended)

  • Use "text/html" for rich HTML content

  • Body format: {"mimeType": "text/x-markdown", "content": "..."}

Examples:

  • Update comment text only: { "projectId": "123456", "taskId": "789012", "commentId": "4219415732999317024", "body": { "mimeType": "text/x-markdown", "content": "## Updated Comment\n\nThis comment has been revised" } }

  • Update with new attachments: { "projectId": "123456", "taskId": "789012", "commentId": "4219415732999317024", "body": { "mimeType": "text/x-markdown", "content": "See updated files" }, "attachFileIds": ["file123", "file456"] }

Returns: Success message upon completion.

Inputs: taskId (required), commentId (required), projectId (required), body, +1 more.

update-wiki-pageA
Destructive

Update wiki page title and/or content.

Required: wikiId, pageId, subject Optional: content, referrers

IMPORTANT - subject is required:

  • Even when only updating content, subject MUST be provided

  • Without subject, API returns 400 error ("Requested subject can not be null")

  • If you want to keep the existing title, first call get-wiki-page to get the current subject, then include it in the update

Workflow for content-only update:

  1. Call get-wiki-page with wikiId and pageId to get current page info

  2. Call update-wiki-page with the existing subject and new content

Set referrers to null to clear all referrers.

Inputs: pageId (required), wikiId (required), content, subject, +1 more.

update-wiki-page-bodyA
Destructive

Replace part of a wiki page body (위키 본문 일부 치환).

Use this instead of update-wiki-page when only a few spots in a long page change. The title and the rest of the body stay as they are.

Rules:

  • oldText must match the current body exactly (copy it from get-wiki-page)

  • Fails if oldText is not found

  • Fails if oldText appears more than once, unless replaceAll is true

Examples:

  • {"wikiId": "123", "pageId": "456", "oldText": "v1.2", "newText": "v1.3"}

  • {"wikiId": "123", "pageId": "456", "oldText": "TODO", "newText": "완료", "replaceAll": true}

Inputs: pageId (required), wikiId (required), newText (required), oldText (required), +1 more.

update-wiki-page-commentC
Destructive

Update a comment on a wiki page.

Inputs: pageId (required), wikiId (required), content (required), commentId (required).

upload-attachmentA

Upload a file attachment to a Dooray task.

Required Parameters:

  • projectId: The project ID

  • taskId: The task ID (post ID) to attach the file to

  • filePath: Absolute path to the file to upload (e.g., "/Users/name/document.pdf")

Example: { "projectId": "123456", "taskId": "789012", "filePath": "/Users/nhn/Downloads/report.pdf" }

Returns: File ID of the uploaded attachment.

Note: The file must exist at the specified path. Maximum file size depends on Dooray's server limits.

Inputs: taskId (required), filePath (required), projectId (required).

upload-drive-fileA

Upload a file to a Dooray drive folder.

Required:

  • driveId: The drive ID

  • parentId: Parent folder ID to upload the file into

  • filePath: Absolute path to the file to upload

Example: { "driveId": "123", "parentId": "456", "filePath": "/Users/name/document.pdf" }

Returns: File ID of the uploaded file.

Note: The file must exist at the specified path.

Inputs: driveId (required), filePath (required), parentId (required).

upload-wiki-fileA

Upload a file to a Dooray wiki (not page-specific).

This is useful for pre-uploading files before creating a wiki page. The returned attachFileId can be used in create-wiki-page's attachFileIds parameter.

Required Parameters:

  • wikiId: The wiki ID

  • filePath: Absolute path to the file to upload (e.g., "/Users/name/document.pdf")

Example: { "wikiId": "123456", "filePath": "/Users/nhn/Downloads/report.pdf" }

Workflow:

  1. Upload file with this tool -> get attachFileId

  2. Create wiki page with create-wiki-page using attachFileIds: [attachFileId]

Returns: File ID and attach file ID of the uploaded file.

Inputs: wikiId (required), filePath (required).

upload-wiki-page-fileA

Upload a file to an existing Dooray wiki page.

Required Parameters:

  • wikiId: The wiki ID

  • pageId: The wiki page ID to attach the file to

  • filePath: Absolute path to the file to upload (e.g., "/Users/name/document.pdf")

Example: { "wikiId": "123456", "pageId": "789012", "filePath": "/Users/nhn/Downloads/report.pdf" }

Returns: File ID and attach file ID of the uploaded file.

Note: The file must exist at the specified path. The type is set to "general" automatically.

Inputs: pageId (required), wikiId (required), filePath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 70 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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'.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables 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
      -
    • F
      license
      B
      quality
      D
      maintenance
      Enables 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
      -