redmine-mcp
Related Servers
Alternatives to redmine-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for Redmine that enables interaction with issues, wiki pages, and time entries through natural language.ISC
- 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.89211MIT
- 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-
- FlicenseCqualityBmaintenanceAn MCP server that connects AI assistants to Redmine, enabling issue and project management via natural language.17-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.11MIT
- AlicenseNot gradedqualityCmaintenanceProvides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.MIT
TDQS
Scored across 26 tools
Each tool targets a distinct Redmine resource (issues, projects, users, etc.) with clearly separated actions. The only potential ambiguity is the generic redmine_api_request, but it is explicitly documented as an escape hatch for unsupported endpoints, so agents can distinguish it from the resource-specific tools.
All tools follow the pattern 'redmine_<resource>', using plural nouns for resources (e.g., redmine_issues, redmine_projects). Minor deviations exist: redmine_upload_file, redmine_paginated_request, and redmine_api_request include action words, but the prefix 'redmine_' is consistently applied, making the set predictable.
26 tools is on the upper end but appropriate for the comprehensive Redmine API surface it covers. The count reflects the many resource types (issues, projects, users, wiki, attachments, etc.), and no tool feels unnecessary. A slightly smaller set could be acceptable, but this is well-scoped.
The tool surface covers CRUD for most major resources and includes search, file upload, and enumeration reads. Minor gaps exist (e.g., custom_fields only list, news read-only) but are compensated by the redmine_api_request escape hatch, which agents can use for any missing endpoint.