create_issueLABSCO SUMMARY
It does one thing, at the moment the thing is worth doing.
The issues that never get filed are the ones you notice mid-task, when opening the tracker means losing your place. Keeping creation inside the editor is the whole point; reading and updating still happen in Redmine.
What it is
A small Node server for Redmine, built for the Cline VS Code extension but usable from any MCP client. It creates issues over Redmine's REST API, and publishes projects as a resource — redmine://projects/{project_id} — that a client can read for a project's details.
What you get
- New issues created in a Redmine project over the REST API
- A project's details, readable as a resource rather than a tool call
- Whatever your Redmine account can reach, since it authenticates as you with your own API key
Requirements
Node.js 18 or newer, a Redmine instance with the REST API enabled, and two values in a .env file: your Redmine host and an API key. The key comes from My Account, API access key in Redmine.
Setup effort
Build from source — git clone https://github.com/papunoko/Redmine-MCP.git
USE CASES
01
Filing a bug the moment you find it
Create the issue from the editor with the description already written by the assistant that just read the code.
02
Turning a decision from a conversation into a tracked task
Put it into the right project as an issue rather than leaving it in chat history.
03
Capturing the follow-ups from a code review
Create one issue per point while you are still in the diff, instead of reconstructing the list later.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Node.js 18 or newer
- REDMINE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/papunoko/Redmine-MCP.git
cd Redmine-MCP
npm installCreate a .env file in the Redmine-MCP folder that sets REDMINE_HOST (your Redmine hostname) and REDMINE_API_KEY (from My Account, API access key, in Redmine).
MCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"redmine-server": {
"command": "node",
"args": [
"C:\\Users\\<YOUR_USERNAME>\\<YOUR_PATH_TO_REDMINE_MCP>\\server.js"
],
"disabled": false,
"autoApprove": []
}
}
}C:\\Users\\<YOUR_USERNAME>\\<YOUR_PATH_TO_REDMINE_MCP>\\server.js is the full path to server.js in your clone. On Windows keep each backslash doubled; on macOS or Linux write an ordinary /… path.
The configuration on this page does not set REDMINE_API_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
