Content
View differences
Updated by Niels Lindenthal 3 months ago
* Implement a Model Context Protocol (MCP) server within OpenProject, using the official Ruby MCP SDK.
* Use HTTP transport only (no WebSocket or streaming) for simpler infrastructure and easier scaling.
* Reuse OpenProject’s existing OAuth2 authentication (with PKCE) for secure access — compatible with both browser-based and desktop MCP clients.
* Provide two search tools out of the box:
* `searchProject`: filters projects by standard attributes (name, identifier, status).
* `searchWorkPackage`: filters work packages by standard attributes (subject, type, status, project, version, user).
* Expose resources derived from OpenProject APIv3:
* `projects`
* `work_packages`
* `versions`
* `users`
* Add an MCP admin page under `Administration` -> `AI Integration`:
* Allows renaming or localizing tool/resource names and descriptions.
* Enables or disables specific tools/resources for compliance or privacy.
* Use HTTP transport only (no WebSocket or streaming) for simpler infrastructure and easier scaling.
* Reuse OpenProject’s existing OAuth2 authentication (with PKCE) for secure access — compatible with both browser-based and desktop MCP clients.
* Provide two search tools out of the box:
* `searchProject`: filters projects by standard attributes (name, identifier, status).
* `searchWorkPackage`: filters work packages by standard attributes (subject, type, status, project, version, user).
* Expose resources derived from OpenProject APIv3:
* `projects`
* `work_packages`
* `versions`
* `users`
* Add an MCP admin page under `Administration` -> `AI Integration`:
* Allows renaming or localizing tool/resource names and descriptions.
* Enables or disables specific tools/resources for compliance or privacy.