openproject-mcp
Related Servers
Alternatives to openproject-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceWrite-capable MCP server for OpenProject API v3 with Community Edition support. Search, create, update, assign, prioritize, and comment on work packages.41MIT
- AlicenseAqualityDmaintenanceMCP server for OpenProject that enables AI agents to search and view work packages, add comments, upload attachments, log time, list projects, and search users via the REST API v3.10MIT
- AlicenseBqualityDmaintenanceA local STDIO server that exposes OpenProject API v3 as MCP tools, allowing MCP clients like Codex CLI and GitHub Copilot CLI to reference projects and work packages.6MIT
- AlicenseBqualityCmaintenanceAn MCP server for logging time entries locally and synchronizing them with OpenProject, enabling natural language time tracking and upload to OpenProject.1614 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude Desktop to your OpenProject instance, allowing you to manage projects, tasks, and time entries through natural language.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to interact with self-hosted or cloud OpenProject instances through API v3 for listing, searching, reading, creating, updating, commenting on, relating, and time-tracking work packages, with confirmation-controlled deletion.10MIT
TDQS
Scored across 18 tools
Most tools target clearly distinct resource/action pairs, and the descriptions remove most ambiguity. The only slight confusion is among op_list_time_entry_activities, op_list_time_entries, and op_list_activities, but their different subjects are clarified in the descriptions.
All tools follow a consistent op_<verb>_<noun> snake_case pattern with predictable verbs like list, get, create, update, and comment. op_log_time and op_add_document_attachment are minor stylistic variations but still fit the overall pattern.
At 18 tools, the server is slightly above the ideal 3-15 range but each tool covers a legitimate OpenProject action across projects, work packages, time tracking, and documents. The breadth is justified by the domain rather than being padded with redundant tools.
Core workflows are well covered: listing projects, CRUD-ish work package operations, commenting, time entry logging, reference data, and document read/update. Notable gaps like work-package deletion or time-entry update/delete exist, but they are secondary or documented API limitations, so agents can still complete main workflows.