F
licenseC
qualityB
maintenanceAn MCP server that connects AI assistants to Redmine, enabling issue and project management via natural language.
17
-
mcp-redmine-server
by YuSahrov
Related Servers
Alternatives to mcp-redmine-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to manage Redmine issues, projects, time tracking, wiki, and files via the MCP protocol.338 npm5Apache 2.0
- FlicenseAqualityDmaintenanceAn MCP server that connects AI agents to Redmine project data, enabling natural language access to issues, projects, time entries, and more via the REST API.21-
- AlicenseBqualityDmaintenanceMCP server for Redmine project management, enabling tools for managing projects, issues, users, time entries, groups, memberships, versions, wiki, news, attachments, search, and Agile sprints via the Redmine REST API.8921 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Redmine for task management, time logging, status updates, and progress tracking via the MCP protocol.9MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Redmine project management systems through MCP tools, providing access to issues, projects, time tracking, wiki, and more.77MIT
TDQS
A3.6/5.0
Scored across 18 tools
Disambiguation4/5
Each tool generally maps to one resource/action, with only a few overlapping pairs like get_issue_tree vs get_issue and get_project_issues vs get_issues_by_status. The descriptions sufficiently clarify these boundaries, so an agent can usually select the right tool.
Naming Consistency5/5
All tools use a consistent redmine_ prefix and snake_case with verb-first names such as get, create, add, start, complete, and upload. Even the wiki PUT operation is named predictably, and there is no mixing of naming conventions.
Tool Count4/5
18 tools is at the upper end of a typical MCP server, but each tool serves a distinct purpose across issues, wiki, projects, attachments, and workflow. It feels slightly heavy but not bloated for the breadth of Redmine features covered.
Completeness3/5
Issue coverage lacks a generic update_issue or delete_issue; status changes are only available through add_comment or the start_fix/complete_fix workflow. Wiki and project access are well covered, but the core issue lifecycle is incomplete.
Maintenance
ActivityInactive
ResponsivenessNo issues