@dnjawm19/mcptest MCP server

Update the Design Guide markdown.

List tasks assigned to the current user or currently unassigned.

Read the User Journey document.

Retrieve the next priority task ordered by importance, urgency, and creation date. Workflow: 1. If the task is BACKLOG, move it to IN_PROGRESS via update_task_status. 2. For IN_PROGRESS tasks, finish outstanding sub-tasks and mark them DONE with update_subtask_status. 3. After meeting acceptance criteria, mark the task DONE and call get_next_task again.

Update the Information Architecture markdown.

List projects available to the current account.

Fetch detailed information for a specific task.

Read the Code Guideline document.

Add a single task with an auto-generated ID. Rules: - Only add tasks the user explicitly requested. - Confirm before adding proactive or debugging tasks. - For debugging tasks, set dependencyIds to the related implementation tasks.

Add sub-tasks to an existing task. Ensure the parent task exists, confirm user intent, provide clear titles and acceptance criteria, and set dependencies when needed.

Update task status (BACKLOG | IN_PROGRESS | DONE | ARCHIVED). Before setting DONE: - Confirm acceptance criteria or ask the user for confirmation. - Provide completionDetails markdown with a one-line summary, '## Description', and '## Modified Files' listing exactly five 'filename: note' entries. - Supply confidenceLevel (1-10, higher = better) and confidenceDetails covering strengths, risks, scope fit, and testing.

Update completion details for a DONE task after additional work. Return markdown with a combined summary, '## Description' including 'Additional work: ...', and '## Modified Files' covering every touched file. Also provide confidenceLevel (1-10) and confidenceDetails explaining quality changes, risks, and alignment with requirements.

Update a sub-task's details, status, or dependencies.

Synchronize DONE tasks with the existing codebase. Use only when the user explicitly requests it and you have confirmed the implementation. Pass taskIds for features already completed in the repository.

Deprecated: use update_task instead.

Update the TRD markdown for the project.

Download `.vooster/tasks/[taskId].txt` files plus `.vooster/tasks.json` for local reference.

Replace the PRD with new markdown provided via aiPrompt.

Update the Code Guideline markdown for the project.

Report missing project documents and instruct the caller to update them before retrying.

Create a vooster project and link it to the current codebase. Only call when the user explicitly says 'createProject'.

Update the User Journey markdown.

Rename the project (1-100 chars).

List project tasks. Provide offset and limit together when paginating (max 100).

Read the TRD for the project.

Read the Information Architecture document.

Update the ERD content (Mermaid or text).

Read the PRD for the project.

Read the Design Guide document.

Deprecated: call add_task separately for each task.

Update the status of a specific sub-task.

Update optional task fields such as summary, aiPrompt, importance, urgency, or complexity. Status and dependency changes are not handled here.