A
licenseA
qualityD
maintenanceConnect Claude to your Redmine instance to search, browse, create and update issues, manage time entries, and upload/download attachments.
5
1
Mozilla Public 2.0
redmine-mcp
Related Servers
Alternatives to redmine-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceConnects Claude Desktop to Redmine for seamless project and issue management, including searching, creating, updating, and tracking tasks using Redmine's API.52,831 PyPI251Mozilla Public 2.0
- AlicenseAqualityDmaintenanceEnables natural language interaction with Redmine via Claude Code or other MCP clients, supporting project, issue, and wiki management.111MIT
- AlicenseDqualityBmaintenanceEnables AI assistants to interact with Redmine via its REST API, covering issues, projects, users, time entries, wiki, files, attachments, and more, with read-only mode and tool filtering.9016 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients (Cursor, Claude Desktop) to manage Redmine issues, projects, time tracking, and wiki pages through natural language.13 npm1-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, update, and query Redmine issues and projects directly from conversations.210 npm1MIT
TDQS
C2.8/5.0
Scored across 15 tools
Disambiguation3/5
The 13 specific tools (get_issue, list_projects, list_versions, etc.) have clearly distinct purposes, but the generic redmine_get and redmine_list overlap with almost all of them, creating real ambiguity about which to use. search vs. search_issues also blurs (full-text vs. filtered), further muddying selection.
Naming Consistency3/5
Most tools follow a clean verb_noun snake_case pattern (list_projects, get_issue, search_issues). However, redmine_get and redmine_list switch to a namespace-prefixed convention, and the bare 'search' breaks the verb_noun rhythm, making the set mixed.
Tool Count5/5
15 tools is well within the healthy range and each of the specific tools maps to a real Redmine resource. The two generic catch-alls add coverage without bloating the surface excessively.
Completeness4/5
The server is explicitly read-only and covers a broad surface (users, projects, issues, time entries, versions, wiki, attachments, search) plus generic get/list fallbacks. The main gap is the absence of write operations (create/update issues, wiki edits, time logging), though the generic tools partially compensate for reads.
Maintenance
ActivityMaintained
ResponsivenessNo issues