Redmine MCP Server
Related Servers
Alternatives to Redmine MCP Server
No user-submitted related servers found.
Related Servers
- 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 gradedqualityDmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.-
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables Claude Code to directly interact with Redmine project management systems, supporting issue management, project operations, and search features.229MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for interacting with Redmine using its REST API, enabling the management of tickets, projects, and user data through integration with LLMs.78MIT
- AlicenseBqualityCmaintenanceMCP server to operate self-hosted Redmine from Claude Code, enabling project and issue management, search, and metadata retrieval via natural language.24MIT
- AlicenseNot gradedqualityDmaintenanceProvides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.MIT
TDQS
Scored across 90 tools
Most tools target distinct Redmine resources and actions, but the large surface contains several overlapping or confusing pairs: addRelatedIssue vs createIssueRelation, getNewsList vs getNewsListByProject, getVersions vs getVersionsByProject, and singular/plural pairs like getMembership/getMemberships. Descriptions help somewhat, but an agent can still misselect among these similar tools.
The set is predominantly camelCase with verb_noun naming such as getIssue, createIssue, updateProject, and deleteUser. There are minor deviations like the bare search tool and inconsistent use of List in getNewsList/getVersions, but the overall convention is readable and predictable.
With 90 tools, the surface is far beyond a well-scoped MCP tool set and exceeds the 50+ threshold for extreme mismatch. Even for a broad system like Redmine, this many tools makes discovery, selection, and maintenance unnecessarily difficult.
Core Redmine workflows are well covered: projects, issues, users, groups, memberships, time entries, versions, wiki pages, news, attachments, watchers, relations, and issue categories. There are still notable gaps such as document CRUD, boards/forums/messages, repository operations, and admin CRUD for roles/custom fields/queries, but agents can work around most of these for common tasks.