@vibescope/mcp-server 0.2.5 → 0.2.7

package/dist/tools.js

@@ -4,9 +4,9 @@
 export const tools = [
     {
         name: 'start_work_session',
-        description: `CALL THIS FIRST when beginning work on a project.
-Returns session info, persona, role, and next_task. Start the next_task IMMEDIATELY without asking the user.
-
+        description: `CALL THIS FIRST when beginning work on a project.
+Returns session info, persona, role, and next_task. Start the next_task IMMEDIATELY without asking the user.
+
 Use mode:'full' for complete context, mode:'lite' (default) for minimal tokens.`,
         inputSchema: {
             type: 'object',
@@ -48,8 +48,8 @@ Use mode:'full' for complete context, mode:'lite' (default) for minimal tokens.`
     },
     {
         name: 'confirm_agent_setup',
-        description: `Confirm that agent setup is complete for this project. Call this after creating your agent's configuration file (e.g., .claude/CLAUDE.md, .gemini/GEMINI.md).
-
+        description: `Confirm that agent setup is complete for this project. Call this after creating your agent's configuration file (e.g., .claude/CLAUDE.md, .gemini/GEMINI.md).
+
 This marks your agent type as fully onboarded to the project, so you won't receive setup instructions again.`,
         inputSchema: {
             type: 'object',
@@ -92,10 +92,10 @@ This marks your agent type as fully onboarded to the project, so you won't recei
     },
     {
         name: 'report_token_usage',
-        description: `Report actual Claude API token usage for accurate cost tracking.
-
-IMPORTANT: MCP can only estimate tokens from tool I/O (~1-5% of actual usage). Call this tool after each API response to report actual usage from the Claude API response headers.
-
+        description: `Report actual Claude API token usage for accurate cost tracking.
+
+IMPORTANT: MCP can only estimate tokens from tool I/O (~1-5% of actual usage). Call this tool after each API response to report actual usage from the Claude API response headers.
+
 The Claude API response includes 'usage.input_tokens' and 'usage.output_tokens' - pass those values here for accurate cost attribution.`,
         inputSchema: {
             type: 'object',
@@ -611,8 +611,8 @@ The Claude API response includes 'usage.input_tokens' and 'usage.output_tokens'
     },
     {
         name: 'get_next_task',
-        description: `Get highest priority pending task. Start it IMMEDIATELY by calling update_task(task_id, status: "in_progress").
-
+        description: `Get highest priority pending task. Start it IMMEDIATELY by calling update_task(task_id, status: "in_progress").
+
 Do NOT ask the user for permission. Follow the directive in the response.`,
         inputSchema: {
             type: 'object',
@@ -669,12 +669,12 @@ Do NOT ask the user for permission. Follow the directive in the response.`,
     },
     {
         name: 'update_task',
-        description: `Update task status, progress, or details. Include progress_note with progress_percentage.
-
-IMPORTANT: When setting status to "in_progress", you MUST provide git_branch AND worktree_path to enable cleanup tracking.
-Create worktree first: git worktree add ../PROJECT-task-TASKID -b feature/TASKID-description BASE_BRANCH
-Then call: update_task(task_id, status: "in_progress", git_branch: "feature/TASKID-description", worktree_path: "../PROJECT-task-TASKID")
-
+        description: `Update task status, progress, or details. Include progress_note with progress_percentage.
+
+IMPORTANT: When setting status to "in_progress", you MUST provide git_branch AND worktree_path to enable cleanup tracking.
+Create worktree first: git worktree add ../PROJECT-task-TASKID -b feature/TASKID-description BASE_BRANCH
+Then call: update_task(task_id, status: "in_progress", git_branch: "feature/TASKID-description", worktree_path: "../PROJECT-task-TASKID")
+
 For projects without git branching (trunk-based or none), use skip_worktree_requirement: true.`,
         inputSchema: {
             type: 'object',
@@ -736,18 +736,18 @@ For projects without git branching (trunk-based or none), use skip_worktree_requ
     },
     {
         name: 'complete_task',
-        description: `Mark task done. Returns next_task which you MUST start immediately without asking the user.
-
-CRITICAL: Before calling complete_task on branching workflows (github-flow, git-flow):
-1. Create your PR targeting the correct branch (develop for git-flow, main for github-flow)
-2. Call add_task_reference(task_id, pr_url) to link the PR to your task
-3. THEN call complete_task - validators CANNOT approve tasks without a PR reference
-
-CRITICAL: After calling this tool, you must:
-1. If next_task is returned → Start it immediately by calling update_task(task_id, status: "in_progress")
-2. If no next_task → Call get_next_task() or start a fallback_activity
-3. NEVER ask the user "What should I do next?" or "Should I continue?"
-
+        description: `Mark task done. Returns next_task which you MUST start immediately without asking the user.
+
+CRITICAL: Before calling complete_task on branching workflows (github-flow, git-flow):
+1. Create your PR targeting the correct branch (develop for git-flow, main for github-flow)
+2. Call add_task_reference(task_id, pr_url) to link the PR to your task
+3. THEN call complete_task - validators CANNOT approve tasks without a PR reference
+
+CRITICAL: After calling this tool, you must:
+1. If next_task is returned → Start it immediately by calling update_task(task_id, status: "in_progress")
+2. If no next_task → Call get_next_task() or start a fallback_activity
+3. NEVER ask the user "What should I do next?" or "Should I continue?"
+
 The auto_continue: true flag in the response means you are expected to continue working autonomously.`,
         inputSchema: {
             type: 'object',
@@ -1388,9 +1388,9 @@ The auto_continue: true flag in the response means you are expected to continue
     // =========================================================================
     {
         name: 'add_subtask',
-        description: `Add a subtask to break down a larger task into smaller workable pieces.
-Subtasks can be claimed and worked on independently by any agent.
-Subtasks inherit the project from their parent task.
+        description: `Add a subtask to break down a larger task into smaller workable pieces.
+Subtasks can be claimed and worked on independently by any agent.
+Subtasks inherit the project from their parent task.
 Max depth is 1 (subtasks cannot have their own subtasks).`,
         inputSchema: {
             type: 'object',
@@ -1424,7 +1424,7 @@ Max depth is 1 (subtasks cannot have their own subtasks).`,
     },
     {
         name: 'get_subtasks',
-        description: `Get subtasks for a parent task with pagination.
+        description: `Get subtasks for a parent task with pagination.
 Returns subtasks with aggregate completion stats.`,
         inputSchema: {
             type: 'object',
@@ -1452,17 +1452,17 @@ Returns subtasks with aggregate completion stats.`,
     },
     {
         name: 'get_stale_worktrees',
-        description: `Get worktrees that need cleanup.
-
-Returns tasks with worktree_path set where:
-- Task is completed or cancelled (worktree should have been cleaned up)
-- Task has been abandoned (no activity for 24+ hours while in_progress)
-
-IMPORTANT: Pass hostname (os.hostname()) to only see worktrees created on THIS machine.
-Worktrees created on other machines cannot be removed locally.
-
-For each stale worktree:
-1. Run: git worktree remove <worktree_path>
+        description: `Get worktrees that need cleanup.
+
+Returns tasks with worktree_path set where:
+- Task is completed or cancelled (worktree should have been cleaned up)
+- Task has been abandoned (no activity for 24+ hours while in_progress)
+
+IMPORTANT: Pass hostname (os.hostname()) to only see worktrees created on THIS machine.
+Worktrees created on other machines cannot be removed locally.
+
+For each stale worktree:
+1. Run: git worktree remove <worktree_path>
 2. Call: clear_worktree_path(task_id)`,
         inputSchema: {
             type: 'object',
@@ -1489,9 +1489,9 @@ For each stale worktree:
     },
     {
         name: 'clear_worktree_path',
-        description: `Clear the worktree_path from a task after cleanup.
-
-Call this AFTER removing the worktree with git worktree remove.
+        description: `Clear the worktree_path from a task after cleanup.
+
+Call this AFTER removing the worktree with git worktree remove.
 This marks the task as cleaned up so it won't appear in get_stale_worktrees.`,
         inputSchema: {
             type: 'object',
@@ -2151,7 +2151,7 @@ This marks the task as cleaned up so it won't appear in get_stale_worktrees.`,
     },
     {
         name: 'answer_question',
-        description: `Answer a question from the user. Use this when the user has asked a question via the dashboard.
+        description: `Answer a question from the user. Use this when the user has asked a question via the dashboard.
 The answer will be displayed to the user and the question marked as answered.`,
         inputSchema: {
             type: 'object',
@@ -2173,8 +2173,8 @@ The answer will be displayed to the user and the question marked as answered.`,
     // ============================================================================
     {
         name: 'add_milestone',
-        description: `Add a milestone to a task.
-Milestones help break down large tasks into smaller trackable steps.
+        description: `Add a milestone to a task.
+Milestones help break down large tasks into smaller trackable steps.
 Use this to show progress on complex tasks and help gauge completion.`,
         inputSchema: {
             type: 'object',
@@ -2279,7 +2279,7 @@ Use this to show progress on complex tasks and help gauge completion.`,
     // ============================================================================
     {
         name: 'create_body_of_work',
-        description: `Create a new body of work to group tasks into phases (pre/core/post).
+        description: `Create a new body of work to group tasks into phases (pre/core/post).
 Bodies of work allow organizing related tasks with optional auto-deployment on completion.`,
         inputSchema: {
             type: 'object',
@@ -2409,7 +2409,7 @@ Bodies of work allow organizing related tasks with optional auto-deployment on c
     },
     {
         name: 'add_task_to_body_of_work',
-        description: `Add a task to a body of work in a specific phase.
+        description: `Add a task to a body of work in a specific phase.
 Phases control execution order: pre tasks run first, then core, then post.`,
         inputSchema: {
             type: 'object',
@@ -2451,7 +2451,7 @@ Phases control execution order: pre tasks run first, then core, then post.`,
     },
     {
         name: 'activate_body_of_work',
-        description: `Activate a draft body of work to start execution.
+        description: `Activate a draft body of work to start execution.
 Requires at least one task. Once active, tasks can be worked on following phase order.`,
         inputSchema: {
             type: 'object',
@@ -2466,7 +2466,7 @@ Requires at least one task. Once active, tasks can be worked on following phase
     },
     {
         name: 'add_task_dependency',
-        description: `Add a dependency between tasks in a body of work.
+        description: `Add a dependency between tasks in a body of work.
 The dependent task cannot start until the dependency is completed. Prevents circular dependencies.`,
         inputSchema: {
             type: 'object',
@@ -2524,8 +2524,8 @@ The dependent task cannot start until the dependency is completed. Prevents circ
     },
     {
         name: 'get_next_body_of_work_task',
-        description: `Get the next available task from a body of work.
-Considers phase order (pre → core → post) and task dependencies.
+        description: `Get the next available task from a body of work.
+Considers phase order (pre → core → post) and task dependencies.
 Only returns tasks where all dependencies are completed.`,
         inputSchema: {
             type: 'object',
@@ -2983,7 +2983,7 @@ Only returns tasks where all dependencies are completed.`,
     // ============================================================================
     {
         name: 'create_sprint',
-        description: `Create a new sprint. Sprints are time-bounded bodies of work with velocity tracking.
+        description: `Create a new sprint. Sprints are time-bounded bodies of work with velocity tracking.
 Sprints start in 'planning' status where tasks can be added with story points.`,
         inputSchema: {
             type: 'object',
@@ -3072,8 +3072,8 @@ Sprints start in 'planning' status where tasks can be added with story points.`,
     },
     {
         name: 'get_sprint',
-        description: `Get a sprint with all its tasks organized by phase (pre/core/post).
-Includes progress percentage, velocity points, and committed points.
+        description: `Get a sprint with all its tasks organized by phase (pre/core/post).
+Includes progress percentage, velocity points, and committed points.
 Use summary_only: true to get task counts and next task instead of full task arrays (saves tokens).`,
         inputSchema: {
             type: 'object',
@@ -3092,7 +3092,7 @@ Use summary_only: true to get task counts and next task instead of full task arr
     },
     {
         name: 'get_sprints',
-        description: `List sprints for a project with velocity metrics.
+        description: `List sprints for a project with velocity metrics.
 Returns sprints sorted by sprint_number descending (most recent first).`,
         inputSchema: {
             type: 'object',
@@ -3130,7 +3130,7 @@ Returns sprints sorted by sprint_number descending (most recent first).`,
     },
     {
         name: 'start_sprint',
-        description: `Start a sprint. Transitions from 'planning' to 'active' status.
+        description: `Start a sprint. Transitions from 'planning' to 'active' status.
 Locks the committed_points at the current total story points.`,
         inputSchema: {
             type: 'object',
@@ -3145,7 +3145,7 @@ Locks the committed_points at the current total story points.`,
     },
     {
         name: 'complete_sprint',
-        description: `Complete a sprint. Handles retrospective phase and auto-deployment if configured.
+        description: `Complete a sprint. Handles retrospective phase and auto-deployment if configured.
 Status flow: active → in_review → retrospective → completed`,
         inputSchema: {
             type: 'object',
@@ -3168,7 +3168,7 @@ Status flow: active → in_review → retrospective → completed`,
     },
     {
         name: 'add_task_to_sprint',
-        description: `Add a task to a sprint with optional story points.
+        description: `Add a task to a sprint with optional story points.
 Tasks can be added during 'planning' status. Story points contribute to committed_points.`,
         inputSchema: {
             type: 'object',
@@ -3214,7 +3214,7 @@ Tasks can be added during 'planning' status. Story points contribute to committe
     },
     {
         name: 'get_sprint_backlog',
-        description: `Get tasks from backlog/pending that can be added to a sprint with pagination.
+        description: `Get tasks from backlog/pending that can be added to a sprint with pagination.
 Returns tasks not already assigned to any body of work or sprint.`,
         inputSchema: {
             type: 'object',
@@ -3241,7 +3241,7 @@ Returns tasks not already assigned to any body of work or sprint.`,
     },
     {
         name: 'get_sprint_velocity',
-        description: `Get velocity metrics for completed sprints.
+        description: `Get velocity metrics for completed sprints.
 Returns committed vs completed points and average velocity.`,
         inputSchema: {
             type: 'object',

package/dist/utils.js

@@ -141,17 +141,17 @@ export const FALLBACK_ACTIVITIES = [
         activity: 'worktree_cleanup',
         title: 'Clean up stale worktrees',
         description: 'Find and remove git worktrees from completed or abandoned tasks.',
-        prompt: `Clean up stale git worktrees to reclaim disk space and prevent confusion:
-
-1. Call get_stale_worktrees(project_id) to find worktrees needing cleanup
-2. For each stale worktree returned:
-   a. Check if the worktree directory exists: ls -la <worktree_path>
-   b. If it exists, remove it: git worktree remove <worktree_path>
-   c. If removal fails (untracked files), use: git worktree remove --force <worktree_path>
-   d. Call clear_worktree_path(task_id) to mark it as cleaned up
-3. Run 'git worktree list' to verify cleanup
-4. Log any issues encountered with add_blocker if worktrees cannot be removed
-
+        prompt: `Clean up stale git worktrees to reclaim disk space and prevent confusion:
+
+1. Call get_stale_worktrees(project_id) to find worktrees needing cleanup
+2. For each stale worktree returned:
+   a. Check if the worktree directory exists: ls -la <worktree_path>
+   b. If it exists, remove it: git worktree remove <worktree_path>
+   c. If removal fails (untracked files), use: git worktree remove --force <worktree_path>
+   d. Call clear_worktree_path(task_id) to mark it as cleaned up
+3. Run 'git worktree list' to verify cleanup
+4. Log any issues encountered with add_blocker if worktrees cannot be removed
+
 This prevents disk bloat from accumulated worktrees and keeps the workspace clean.`,
     },
 ];