Taskavel’s MCP server exposes two ready-made prompts to compatible AI clients: Plan my day and Triage new bugs. They are MCP prompts, not buttons inside Taskavel. After you connect Taskavel, your client may list them as available prompts or workflows; if it does not, type the example request from Plan my day or Triage new bugs directly into the conversation. The result is the same: the client uses Taskavel’s generated tool reference to inspect the permitted projects and tasks before it proposes or makes a change.
Find the right tool without guessing
Open the MCP tools overview when you need a specific operation. It is generated from the Taskavel server, so it remains aligned with the shipped tools and their schemas. The overview groups the tools; each tool page identifies whether it is read, write, or destructive and gives a prompt and call example.
Start with discovery tools when the input is not yet exact. ListProjects resolves accessible projects; ListBoardColumns and ListMilestones reveal valid destinations; task details and searches establish the current state. For broad planning, use FilterTasks, GetBoardSnapshot, and RecentActivity instead of trying to infer status from a title alone.
Read tool descriptions closely for their data shape. Task descriptions use rich-text HTML, not Markdown, when a create or update tool accepts a description. Comments identified as #123 are comment IDs, not task IDs: use the reply tool only when responding to that comment.
Plan my day
Ask the client to use the Plan my day prompt or phrase the request directly: “Plan my Taskavel work for today. Show deadlines, my active tasks, and any running timer before recommending an order.” The workflow can inspect your tasks and deadlines before it proposes what to do next.
Review the proposed order before asking the client to start or stop tracking time. A good plan names the relevant projects and tasks and distinguishes a recommendation from an action already taken. If a suggested task is unfamiliar, ask for its details rather than accepting the priority blindly.
Triage new bugs
Use the Triage new bugs prompt when recent incoming work needs sorting. A useful request is: “Triage new bug reports in the Mobile project. Show the board snapshot and recent activity, identify missing information, and ask before moving anything.” This tells the client to collect context before changing columns or milestones.
For several moves, prefer the bulk-move capability rather than individual repeated moves. If a requested column does not match the board, the server can return available columns; choose from those options instead of having the client invent one. List milestones before creating a new milestone, and suggest a new one only when the requested milestone does not exist.
Write prompts that are safe to execute
Give the client a clear scope and an approval boundary. For example: “In Website, find tasks assigned to me that are due this week. Do not change anything; summarize blockers.” After review, follow with: “Move only task #42 to Review.” Keep member management, archive actions, and deletion as separate requests.
Permanent deletion requires an already archived task and explicit confirmation. When in doubt, ask for an archive and a report, not a purge. See permissions and project scope for the effective access limits.