mcp-redmine
Related Servers
Alternatives to mcp-redmine
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceProvides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.MIT
- 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-
- AlicenseBqualityBmaintenanceMCP server that provides access to the Redmine REST API, enabling issue tracking, project management, and more through natural language.2624 npmMIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.11 npmMIT
- AlicenseCqualityDmaintenanceModel Context Protocol (MCP) server for Redmine that provides comprehensive access to the Redmine REST API, enabling users to operate Redmine from MCP clients such as Claude Desktop.9020 npmMIT
TDQS
Scored across 18 tools
Most tools have distinct purposes, but redmine_get_users and redmine_find_user overlap in resolving user IDs, and redmine_my_dashboard partially duplicates redmine_search_issues for personal queries. These overlaps create mild selection ambiguity.
All tools share the redmine_ prefix and nearly all follow a verb_noun pattern (get_issue, create_issue, list_projects). The exception is redmine_my_dashboard, which uses a possessive instead of a verb, breaking the pattern slightly.
With 18 tools, the server falls in the borderline heavy range (16-25). The count is justified by the broad domain coverage (issues, users, time, wiki, projects), but it feels slightly oversized for a focused MCP.
The core issue workflow is well covered: create, retrieve, update, add notes, search, and log time are all present. However, missing delete operations for issues or notes, no attachment upload, and read-only wiki access represent minor but notable gaps.