No user-submitted related servers found.
Scored across 90 tools
Most tools follow clean resource+action pairs, but several boundaries are unclear: getCurrentUser and getMyAccount overlap, addRelatedIssue/removeRelatedIssue largely duplicate create/delete issue relation, and getVersions has a list-style name but is actually a Show version action. These overlaps will cause agents to misselect tools.
The overall get/create/update/delete + resource naming scheme is consistent and readable, but list/show conventions are inconsistent: list tools usually use plural nouns (getIssues, getGroups) yet some use List suffixes (getNewsList, getNewsListByProject) and one use singular/plural mismatch goes the wrong way (getVersions is actually a show). Despite these deviations, the naming is still largely predictable.
With 90 tools—many being full CRUD sets across roughly two dozen resources—the surface far exceeds what an agent needs to manage Blender surfaces. This is well beyond the 50-tool extreme mismatched threshold and will overwhelm tool selection.
The server covers most major Redmine domains at near-full lifecycle: issues, projects, users, groups, roles, memberships, time entries, wiki, news, versions, attachments, files, categories, relations, and custom fields. Some gaps exist, such as no document resource management, and uploads are token-based rather than directly attachable in one step, but these are relatively minor workarounds.