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
- FlicenseNot gradedqualityDmaintenanceAn MCP server providing 63 tools to interact with Redmine instances, covering issues, projects, time entries, and wiki pages. It utilizes streamable HTTP transport and supports per-client authentication for secure management of Redmine resources.6 npm-
- AlicenseBqualityBmaintenanceMCP server that provides access to the Redmine REST API, enabling issue tracking, project management, and more through natural language.268 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Redmine that enables interaction with issues, wiki pages, and time entries through natural language.ISC
- AlicenseNot gradedqualityAmaintenanceA stateless MCP server for Redmine that allows users to interact with issues, time entries, wiki, projects, and more via their own API keys.4MIT
- 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-
TDQS
Scored across 73 tools
Every tool targets a distinct resource and action; even the two file-uploading tools (attach_file_to_issue, upload_project_file) are clearly separated by destination, and create_or_update_wiki_page is explicit about its dual nature. No two tools appear to do the same thing.
All tools follow a verb_noun (or verb_adjective_noun) snake_case convention; the few composite verbs like chain_issues and bulk_update_issues still fit the pattern. No camelCase or mixed styles.
With 73 tools, this is a large surface, but it mirrors the breadth of Redmine's API across projects, issues, wiki, news, users, groups, time entries, and more. Every tool addresses a specific endpoint or workflow, so the count is justified even if it feels heavy for an agent.
The coverage is comprehensive across the main Redmine resources, including lifecycle operations for issues, projects, versions, categories, users, groups, wiki pages, news, and time entries. Minor gaps remain — the Documents module only exposes categories, not document files, and there is no way to manage project modules or issue workflows.