# Feature AA-82 - Expose work package relations via MCP

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

## 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** expose information about work package relations via MCP,  
**so that** those relations can be taken into account, for example during scheduling via MCP.

**Acceptance criteria**

*   Expose work package relations via MCP tools or resources
    
*   The information exposed is enough to understand how the rescheduling of one work package could affect the scheduling of another work package (e.g. in precedes/follows relations)
    

**Background**

During some practical tests, it was noticed that updating a work package's start or due date is easily possible, but it can have unintended consequences other work package's dates. Exposing relations should either prevent this or at least ease the trouble shooting that follows.