Related Servers

Most tools target a distinct resource+action, and descriptions explicitly cross-reference alternatives (search_work_packages vs list_work_packages vs run_query; list_versions vs list_sprints; get_project_metadata vs get_work_package_schema). A few pairs remain easy to confuse at a glance—sprints versus versions, saved queries versus ad-hoc filters, and project phase definitions versus project phases—but the descriptions resolve them.

All 59 tools use snake_case verb_noun names (get_work_package, update_project, list_time_entries, delete_attachment, mark_notifications), with predictable list/get/create/update/delete patterns across domains. Minor outliers like run_query, save_query, log_time and toggle_comment_reaction still follow the verb_noun convention.

At 59 exposed tools this is a very heavy surface for an agent to navigate, spanning work packages, comments, watchers, relations, reminders, reactions, attachments, file links, projects, phases, queries, notifications, time entries, versions, sprints, principals, roles, memberships and metadata. The breadth is justified by OpenProject's domain, but 59 tools exceeds a comfortable selection budget and risks misselection.

Core lifecycle coverage is strong: work packages, projects, time entries, versions and comments each have full CRUD, with supporting metadata, schema, permission, job-status and notification tools. Gaps such as no edit/delete for saved queries, read-only file links and sprints, and admin-gated membership writes are explicitly documented but still leave a few dead ends.