# Feature AI-216 - MCP tool get_work_package_schema for creating work packages

Project: Stream AI
Status: needs review
URL: https://community.openproject.org/work_packages/AI-216

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.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 | Community (COM) |

## Details

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

## People

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

## Estimates and progress

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

## Description

**As a** user working with an AI assistant connected to the OpenProject MCP server  
**I want to** let the assistant read the schema of a work package for a given project and type  
**so that** the work packages it creates use the right custom fields, allowed statuses and the type's description template

**Acceptance criteria**

*   For a project and a type, an assistant can find out which fields a new work package has, which of them are required, which values are allowed and which defaults apply.
    
*   When an assistant creates a work package, it uses the description template of the type as the starting point for the description.
    
*   An assistant fills required custom fields and picks allowed values (for example status, priority, versions, list custom fields) without running into a failed create first.
    
*   The assistant is offered the fields a user sees when creating a work package of that type in OpenProject. Fields hidden in the form configuration of the type are not offered.
    
*   The answer stays small enough to work with in an assistant's context, also for types with many custom fields.
    
*   The tool description says what the schema is for, so assistants pick the tool on their own when they create work packages.
    
*   The new MCP tool is called `get_work_package_schema`
    

**Technical notes**

*   Based on the APIv3 work package create form, with project and type as the only input. The response is reduced with MCP output filters.
    
*   Update `docs/system-admin-guide/integrations/mcp-server/README.md`.
    

**Permissions and visibility considerations**

*   Only available when the `mcp_server` is active and the tool is enabled.
    
*   Same rules as the APIv3 create form: the user needs to see the project and to be allowed to add work packages in it.
    

**Out of scope**

*   Validating a work package payload
    
*   A schema for editing existing work packages. Useful as a follow-up.