Redmine MCP Server
Related Servers
Alternatives to Redmine MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI clients (Cursor, Claude Desktop) to manage Redmine issues, projects, time tracking, and wiki pages through natural language.9 npm1-
- AlicenseBqualityBmaintenanceMCP server to operate self-hosted Redmine from Claude Code, enabling project and issue management, search, and metadata retrieval via natural language.24MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to manage Redmine issues, projects, time tracking, wiki, and files via the MCP protocol.337 npm5Apache 2.0
- AlicenseBqualityDmaintenanceA 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 gradedqualityAmaintenanceEnables AI assistants to interact with Redmine project management systems through MCP tools, providing access to issues, projects, time tracking, wiki, and more.378 PyPI79MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with Redmine project management systems, providing comprehensive access to issues, projects, time tracking, users, and wiki pages through natural language commands.3345 npmApache 2.0
TDQS
Scored across 11 tools
All tools have clearly distinct purposes: add_comment is for issue comments, create_issue for creation, download_attachment for downloading, get_issue for details, get_my_today for personalized summary, get_wiki for wiki content, list_enumerations for IDs, list_issues for listing, list_projects for projects, list_wiki_pages for wiki listing, and update_wiki for wiki modification. No two tools overlap in functionality.
Tool names follow a consistent snake_case verb_noun pattern (e.g., create_issue, list_projects). The only minor deviation is 'get_my_today' which uses a possessive 'my_today', but it remains readable and fits the pattern of other 'get_' tools.
With 11 tools covering issues, wiki, projects, attachments, and enumerations, the number is well-scoped. Each tool earns its place without redundancy, appropriate for a Redmine MCP server.
Core operations for issues (create, read, add comment) and wiki (get, list, upsert) are present, but missing update and delete for issues, and delete for wiki. This leaves notable gaps in lifecycle coverage, though the surface handles common workflows.