redmine_projects_listLABSCO 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
USE CASES
Breaking a big ticket into work
Create subtasks under the parent from the conversation where the plan was made, then list the children to check the split.
Recording that one thing blocks another
Create the relation between the two issues instead of writing it in a comment nobody will query later.
Filing an issue without leaving what you are doing
Create it with the project, tracker and priority set, and add the context as a comment in the same pass.
Reorganising work that has drifted
Move an issue under a different parent, or promote it back to top level, rather than closing and recreating it.
Trying it out before connecting a live tracker
Run in mock mode, or bring up the bundled Docker Redmine with its sample data, and exercise the tools against something disposable.
15 tools
Listed in project docs. Your client may show a different list.
redmine_projects_getredmine_issues_listredmine_issues_getredmine_issues_createredmine_issues_updateredmine_issue_create_subtaskredmine_issue_set_parentredmine_issue_remove_parentredmine_issue_get_childrenredmine_issue_relations_getredmine_issue_relation_createredmine_issue_relation_deleteredmine_issue_comment_addredmine_users_currentBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Requires
REDMINE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/zacharyelston/RedmineMCP.git
cd RedmineMCP/redmcp-typescript
npm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"redmine": {
"command": "node",
"args": [
"<YOUR_PATH_TO_REDMCP_TYPESCRIPT>/build/index.js"
],
"env": {
"REDMINE_URL": "<YOUR_REDMINE_URL>",
"REDMINE_API_KEY": "<YOUR_REDMINE_API_KEY>",
"LOG_LEVEL": "info"
}
}
}
}