# Feature AA-73 - Add update_work_package MCP tool

Project: Stream Agents & Assistants
Status: closed
URL: https://community.openproject.org/work_packages/AA-73

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.8.0 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Artificial Intelligence / MCP Server (MCP) |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Jan Sandbrink |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

**As** a user of LLMs,  
**I want to** have a tool to update work packages,  
**so that** I can use my agent to update work packages from my inputs.

**Acceptance criteria**

*   A tool to update a new work package is available
    
*   During update all business rules we'd usually enforce are enforced
    
    *   e.g. required fields
        
*   A correct `lock_version` must be provided for a successful update
    

**Technical notes**

*   We should probably stay compatible with the schema we usually accept for WP update via API
    

**Permissions and visibility considerations**

*   Regular permissions checks for the user performing the request are applied