A
licenseNot graded
qualityD
maintenanceEnables interacting with a Redmine instance via REST API, allowing issues, projects, time logging, and generic endpoint calls through an MCP agent.
28 npm
MIT
No user-submitted related servers found.
Scored across 4 tools
Each tool targets a distinct operation on the issue resource: fetching one, listing many, updating, and creating. There is no overlap or ambiguity between the four tools.
All tool names follow a consistent verb_noun snake_case pattern: get_issue, list_issues, update_issue, create_issue. The naming is predictable and easy to infer.
Four tools is well-scoped for a Redmine issue-focused MCP server. Each tool provides a necessary and distinct capability without unnecessary bloat.
The core issue lifecycle is covered: create, read single, read list, and update. The only notable gap is the absence of a delete_issue operation, though this can often be worked around via update_issue.