Content
View differences
Updated by Niels Lindenthal 3 months ago
**As a:** ##
Problem:
* Project managers who want to query, summarize, or report on projects naturally using AI tools.
* Product owners who want to automate repetitive project reporting.
* Project members who need quick summaries, comparisons, or contextual insights from project data.
* Admins who want to safely connect OpenProject data with AI assistants.
**I want:**
* One of the first project management platform with native MCP support, enabling direct AI assistant access to real project data.
* It to be fully integrated with OpenProject’s existing authentication and permission system.
* An admin customization layer to align AI vocabulary with organizational terminology (e.g., “features,” “tickets,” or “projectOne”).
* A simple and easy to operate architecture (HTTP-only, no streaming) and easy deployment in my own infrastructure.
**Problem:**
* Users want to interact with OpenProject using natural language with external AI assistants to generate project status reports, find work packages, or analyze progress.
* Currently, they must extract data manually, build API scripts, or rely on nonstandard integrations.
* There’s no consistent, secure, standard protocol to let LLMs work with OpenProject data.
**Pain:** Pain:
* Manually copy project data for analysis
* Use API tokens in custom scripts which is a technical barrier and not maintainable.
* AI models can’t access project data directly
Problem:
* Project managers who want to query, summarize, or report on projects naturally using AI tools.
* Product owners who want to automate repetitive project reporting.
* Project members who need quick summaries, comparisons, or contextual insights from project data.
* Admins who want to safely connect OpenProject data with AI assistants.
**I want:**
* One of the first project management platform with native MCP support, enabling direct AI assistant access to real project data.
* It to be fully integrated with OpenProject’s existing authentication and permission system.
* An admin customization layer to align AI vocabulary with organizational terminology (e.g., “features,” “tickets,” or “projectOne”).
* A simple and easy to operate architecture (HTTP-only, no streaming) and easy deployment in my own infrastructure.
**Problem:**
* Users want to interact with OpenProject using natural language with external AI assistants to generate project status reports, find work packages, or analyze progress.
* Currently, they must extract data manually, build API scripts, or rely on nonstandard integrations.
* There’s no consistent, secure, standard protocol to let LLMs work with OpenProject data.
**Pain:**
* Manually copy project data for analysis
* Use API tokens in custom scripts which is a technical barrier and not maintainable.
* AI models can’t access project data directly