LabscoMCP early access ↗
zacharyelstonMCP SERVER

Redmine MCP

Redmine issue tracking from the chat — projects and issues, subtasks and parent relationships, issue relations and comments, with a mock mode for working offline.

by zacharyelston ↗Project & Task ManagementCommunity

LABSCO SUMMARY

Hierarchy and relations, which is where most trackers stop.

Plenty of integrations can create an issue. Fewer can restructure work — reparent a ticket, split a task into subtasks, record that one issue blocks another — and that is the part where Redmine differs from the alternatives. The mock mode is the other thing worth noticing: being able to exercise the whole tool surface with no instance behind it makes this safe to try before you point it at a live tracker. Set expectations on completeness — the README says plainly that this is not finished, and the tool list is the accurate picture of what exists today.

What it is

A TypeScript MCP server for Redmine, the open-source project management system. It covers reads and writes on projects and issues, and pays particular attention to the structural parts — parent-child hierarchies and typed relations between issues — that make Redmine worth using in the first place.

What you get

  • Projects: list the ones you can reach and open one in detail — redmine_projects_list, redmine_projects_get
  • Issues with filtering, full detail, creation and update — redmine_issues_list, redmine_issues_get, redmine_issues_create, redmine_issues_update
  • Hierarchy as its own set of operations rather than a field you have to know about: create a subtask under a parent, set or change an existing issue's parent, promote an issue back to top level, and list a parent's children — redmine_issue_create_subtask, redmine_issue_set_parent, redmine_issue_remove_parent, redmine_issue_get_children
  • Typed relations between issues — read them, create one, delete one — plus comments on an issue — redmine_issue_relations_get, redmine_issue_relation_create, redmine_issue_relation_delete, redmine_issue_comment_add
  • The current user's details and permissions, so an assistant knows what it is allowed to do — redmine_users_current
  • A mock mode with a complete data provider that simulates every operation with predictable responses, for development, offline work and demonstrations without touching a Redmine instance
  • A Docker-based Redmine development environment in the repository, with a Postgres database, sample projects and issues, for testing against something real but disposable

Requirements

A reachable Redmine instance and an API key with the permissions you need. Three values go into your client config: REDMINE_URL, REDMINE_API_KEY and LOG_LEVEL. Node.js — the implementation lives in the TypeScript sub-project and the client entry points at its built output. The package is redmcp-typescript (1.0.0 in package.json). One practical gotcha the README flags: Redmine requires a priority when creating an issue, so that field has to be supplied.

Setup effort

Build from source — git clone https://github.com/zacharyelston/RedmineMCP.git