F
licenseA
qualityC
maintenanceMCP server for Redmine integration, enabling AI assistants to manage issues, upload files, automate workflows, and handle wiki pages.
18
-
redmine-mcp-server
by igorolv
Related Servers
Alternatives to redmine-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to manage Redmine issues, projects, time tracking, wiki, and files via the MCP protocol.3353 npm5Apache 2.0
- AlicenseBqualityBmaintenanceMCP server to operate self-hosted Redmine from Claude Code, enabling project and issue management, search, and metadata retrieval via natural language.24MIT
- FlicenseAqualityDmaintenanceMCP server for Redmine that lets coding agents read and write Redmine: search issues, view histories, comment, log time, browse wiki, and download attachments. Enforces explicit user permission for any write operations.181-
- 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.9014 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients (Cursor, Claude Desktop) to manage Redmine issues, projects, time tracking, and wiki pages through natural language.8 npm1-
TDQS
A4.1/5.0
Scored across 39 tools
Disambiguation5/5
Each tool targets a distinct resource and action, and descriptions explicitly cross-reference alternatives (e.g., listIssues vs searchIssues vs getMyIssues, getIssue vs getIssueHistory). The surface is large but boundaries are clearly documented, leaving little true ambiguity.
Naming Consistency5/5
Consistent camelCase verb_noun pattern throughout (listIssues, getIssue, createWikiPage, searchAll). Minor 'My' variants (getMyIssues, getMyTimeEntries) remain predictable and readable.
Tool Count2/5
39 tools is excessive for a single MCP server; many list* metadata tools and specialized read tools could be consolidated or dynamically discovered, increasing selection burden.
Completeness3/5
Issue tracking and analytics are well covered, but notable gaps exist: no delete operations for issues, wiki pages, or time entries; no update/delete for time entries; no create/update for projects or versions.
Maintenance
ActivityActive
ResponsivenessNo issues