F
licenseC
qualityB
maintenanceAn MCP server that connects AI assistants to Redmine, enabling issue and project management via natural language.
17
-
Redmineflux MCP Server
by ZTMP0010
Related Servers
Alternatives to Redmineflux MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server that provides access to the Redmine REST API, enabling issue tracking, project management, and more through natural language.268 npmMIT
- FlicenseAqualityDmaintenanceMCP server for Redmine integration, enabling AI assistants to manage issues, upload files, automate workflows, and handle wiki pages.18-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.11 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.MIT
- 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
TDQS
A3.9/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct resource and action, from project and issue CRUD to time logging and metadata lookups. Even the analytical tools (project_stats, project_summary, my_workload, critical_issues) have clearly defined, non-overlapping purposes that are well-explained in their descriptions.
Naming Consistency4/5
Most core tools follow a consistent verb_noun pattern (list_projects, get_issue, create_issue), but a few use noun phrases like project_stats and my_workload, and system tools (onboard, feedback) break the pattern. The shared redmineflux_core_/redmineflux_system_ prefix helps maintain a sense of order.
Tool Count3/5
At 21 tools, the server leans heavy, with several metadata lookup tools (list_statuses, list_trackers, list_priorities, list_time_entry_activities, list_versions) that could potentially be combined. Despite the count, each tool has a clear purpose and the set is scoped to Redmine project management.
Completeness4/5
The tool surface covers the core issue lifecycle (list, get, create, update) and time tracking, plus project views and useful aggregate summaries. Notable gaps include lack of project creation/update/delete and time entry update/delete, but these are not critical for common Redmine workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues