mcp-server-redmine
Related Servers
Alternatives to mcp-server-redmine
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceProvides read-only MCP tools over stdio for interacting with a Redmine instance, enabling users to list and retrieve projects, issues, queries, wiki pages, and other Redmine resources via the REST API.35-
- FlicenseNot gradedqualityCmaintenanceExposes Redmine's REST API as MCP tools, enabling AI assistants to read, create, update, and comment on issues, manage projects, and handle attachments through both HTTP and stdio transports.9 npm-
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for interacting with Redmine, including issues, projects, wiki pages, time entries, and more.4 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Redmine projects, issues, users, time entries, memberships, groups, versions, custom fields, and queries via 53 API endpoints, with OAuth authentication.1MIT
- 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.897 npm1MIT
- AlicenseAqualityAmaintenanceA local Model Context Protocol server (stdio) for Redmine that allows you to work with Redmine issues, projects, and time entries directly from your editor.1272 npmMIT
TDQS
Scored across 33 tools
Most tools are cleanly separated by resource and action, but redmine_get_current_user and redmine_get_my_account overlap in purpose, and redmine_upload_attachment vs redmine_upload_file could be misread despite helpful descriptions. Otherwise, issue/project/time/wiki tools are clearly distinct.
The dominant redmine_<verb>_<noun> pattern is easy to follow, but the issue-relation tools (list_issue_relations, get_issue_relation, create_issue_relation, delete_issue_relation) break the redmine_ prefix convention, and redmine_search doesn't fit the verb_noun shape.
33 tools is well beyond the ideal 3-15 range and falls into the 25+ overgrown category. While Redmine is a broad system, many tools are simple read operations (list/get) that could be consolidated, making the set feel heavy.
Core Redmine workflows are well covered: issues, projects, time entries, and wiki pages have full CRUD, and issue relations are complete. However, there are notable gaps such as no project deletion, no file deletion, read-only users/roles, and news limited to listing, which prevents full lifecycle coverage.