F
licenseNot graded
qualityD
maintenanceEnables 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
-
openproject-mcp
by OliverRhyme
Related Servers
Alternatives to openproject-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for interacting with Redmine, including issues, projects, wiki pages, time entries, and more.15 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI agents to interact with OpenProject API v3 for project management, including creating and managing work packages, projects, comments, time entries, boards, and user dashboards.41 npmMIT
- AlicenseBqualityCmaintenanceEnables AI assistants to manage OpenProject work packages, projects, and time tracking. It provides comprehensive tools for creating, updating, and querying tasks and project metadata through the OpenProject API.1141 npm1MIT
- FlicenseNot gradedqualityCmaintenanceExposes OpenProject project management tools to Claude Code via MCP, enabling listing, reading, and updating work packages, projects, and statuses with safety features like dry-run and protected transitions.-
- AlicenseAqualityBmaintenanceWrite-capable MCP server for OpenProject API v3 with Community Edition support. Search, create, update, assign, prioritize, and comment on work packages.41MIT
TDQS
A3.5/5.0
Scored across 37 tools
Disambiguation5/5
Each tool targets a distinct resource and action (e.g., op_create_project, op_delete_work_package, op_list_boards). Even similar operations like add/remove watchers are clearly differentiated. The escape hatch (op_api_passthrough) is explicitly noted as distinct.
Naming Consistency5/5
All tools follow the consistent pattern op_verb_noun (snake_case), with clear verbs like create, delete, get, list, update, etc. No mixing of conventions or ambiguous prefixes.
Tool Count4/5
37 tools is above the typical ideal range, but each tool serves a specific and necessary operation for OpenProject's domain (projects, work packages, attachments, users, notifications, etc.). The count reflects the complexity of the platform rather than poor scoping.
Completeness4/5
The tool surface covers most core workflows: CRUD for projects and work packages, attachments, relations, notifications, and user management. Minor gaps exist (e.g., no update for relations or users), but these are likely intentional due to permissions or scope.
Maintenance
ActivityInactive
ResponsivenessNo issues