openproject-mcp
Related Servers
Alternatives to openproject-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to access and manage OpenProject projects, work packages, attachments, time tracking, wiki, and users via the OpenProject API v3.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable assistants to read files, work packages, and wiki pages from an openDesk instance using the account's existing permissions.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely connect to OpenProject workspaces and browse, query, and reason about projects, work packages, saved queries, and related metadata via the OpenProject REST API v3.24 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with self-hosted OpenProject instances through the MCP protocol, supporting CRUD operations for projects and tasks (work packages) with pagination and filtering capabilities.8-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with OpenProject's API v3 for comprehensive project management operations including work packages, projects, time tracking, users, and all other OpenProject features through natural language.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage OpenProject projects, work packages, activities, and wiki pages through the Model Context Protocol.-
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: current user, projects, work-package search, single work package, comments, statuses, and types. There is no meaningful overlap between search_work_packages and get_work_package because one is full-text search and the other is retrieval by ID.
All tools follow a consistent verb_noun snake_case pattern: get_current_user, list_projects, search_work_packages, get_work_package, and so on. The one longer name, get_work_package_comments, still fits the established convention.
Seven tools is a well-scoped size for a read-oriented OpenProject integration. Each tool has a clear purpose and none are redundant, so the count feels intentional rather than padded or thin.
The surface is entirely read-only: it can search, view, and list work packages, projects, comments, statuses, and types, but it cannot create, update, transition, or comment on work packages. For a project-management domain this is a significant functional gap that prevents agents from completing common workflows.