Related Servers

Most tools have clearly distinct resource/action targets, and the descriptions explicitly separate commonly confused pairs such as list_attachments vs list_file_links and list_work_packages vs search_work_packages. The large set still has several adjacent read paths (list/search/run_query/get for work packages, versions vs sprints, metadata vs schema) that an agent must track carefully, but the boundaries are generally documented.

Names consistently use snake_case with a verb_noun pattern across CRUD, bulk, comment, watcher, relation, notification, and meta tools. Compound resources such as work_package, time_entry, and project_phase are applied predictably, with no camelCase or mixed-verb chaos.

At 59 tools, the surface is far beyond the typical 3-15 range and is heavy for an agent to navigate, even though OpenProject is a broad domain. The tools are mostly meaningful and non-redundant, but the set would benefit from stronger grouping or consolidation.

Core workflows are well covered: project CRUD/copy, work-package CRUD/bulk/comments/watchers/relations, attachments, time entries, versions, sprints, notifications, reminders, queries, phases, and permissions. Remaining gaps are mostly intentional or gated (wiki/meetings/documents/budgets hidden behind enable_tool_group, saved-view edit/delete deferred to UI, membership writes admin-gated).