Related Servers

Each tool targets a distinct resource-action pair (e.g., issues, wiki pages, time entries, users, attachments, projects). Overlap is minimal—the only compound tool, redmine_create_or_update_wiki_page, clearly handles both create and update. The catch-all redmine_custom_request is explicitly generic and optional, so it does not create ambiguity.

All tools follow a consistent redmine_<verb>_<resource> pattern in snake_case. Verbs are uniformly list, get, create, update, delete, with one exception (redmine_create_or_update_wiki_page) that uses a compound verb but remains readable and consistent in style. The single non-verb-noun tool, redmine_custom_request, is a deliberate generic fallback and does not break the established convention.

At 33 tools, the surface is oversized for a typical MCP server, exceeding the 25-tool threshold that indicates 'too many.' While Redmine is a feature-rich system, many tools could be consolidated (e.g., time entry activities and statuses/priorities/trackers could be grouped), and the breadth makes the server harder to navigate.

The tool set covers the major Redmine domains: issues (CRUD plus statuses, priorities, trackers), projects (list/get only), wiki pages (CRUD), time entries (full CRUD plus activities), users (read-only), attachments (get/update/delete), and files (upload/create/list). Notable gaps are the absence of project create/update/delete and user management, but the presence of redmine_custom_request mitigates these limitations for advanced use.