ReleaseNew Feature

Update PBIs, tasks, and epics—including their body text—via MCP

Update released

If you work with Lasimban through MCP, you can now finish the content of your PBIs, tasks, and epics—body text included—in your own context and apply it all at once. The update tools are now complete, with a single tool per target for partial updates.

🧩 Updates used to stop halfway

Until now, MCP had several gaps around updating. You couldn’t update epics at all, you couldn’t change the body text (description) of PBIs and tasks, and for tasks you could only change the status.

As a result, even when you shaped the content in your own context, you couldn’t apply it completely—you had to switch over to the web app to finish things off, breaking the flow.

🛠️ One tool per target, including body text, for partial updates

With this update, you can now make partial updates to PBIs, tasks, and epics—body text included—through MCP.

  • A new task update tool lets you update not just the status but the body text as well
  • A new epic update tool lets you update epics, which couldn’t be changed before
  • The PBI update tool now adds body text updates

Each target—PBI, task, or epic—has a single tool for updates. Fields you don’t specify stay unchanged, so you can confidently send only what you want to change.

🔁 Status-only tools retired, and how to migrate

Alongside this update, the status-only tools update_pbi_status and update_task_status have been retired.

To change status from now on, use the status field of update_pbi and update_task. Because these update tools handle every field, status included, you can revise the body text and change the status in a single call.

The behavior when you set a status to “done” remains the same as before. You don’t need to rework your existing workflow to migrate—just swap the status-only tool for the update tool, and you’ll get the same result as before.

🎯 Finish in your own context, apply all at once

Now that the update tools are complete, AI agents and developers can polish content to the very end in their own context and apply only the fields they need, all at once.

From adjusting the body text to updating the status, everything stays within MCP without switching over to the web app. Your work moves along with the flow of your thinking, instead of being broken up midway.

📮 Contact us

If you have any questions or feedback, please don’t hesitate to reach out.