list-issuesLABSCO SUMMARY
Triage the tracker from the chat window.
Filtering by project, status and assignee in one call is what makes this usable for a standup: you can ask what is open against you and move it along without opening Redmine.
What it is
An MCP server for a Redmine instance, written in TypeScript. It covers the three objects most work runs through — issues, projects and users — with filters on the listings and full field coverage on create and update.
What you get
- Issues listed with filters for project, status and assignee, plus limit and offset
- One issue read in full by ID
- Issues created with tracker, status, priority, assignee and description
- Issues updated, including the done ratio
- Projects listed, and one read by numeric ID or string identifier
- Users listed, and one user read
Requirements
A Redmine instance and an API key from your account settings — the instance address and the key both go in the environment. Build with npm run build before npm start.
Setup effort
Build from source — git clone https://github.com/tamu960925/mcp-redmine.git
USE CASES
Seeing what is assigned to you
List issues filtered by assignee and status, paging with limit and offset.
Filing a bug you just found
Create the issue against a project with a subject, description, priority and assignee.
Moving a ticket along
Update status, priority, assignee or done ratio on an existing issue by ID.
Reading the full context of a ticket
Fetch one issue by ID rather than scanning a list for it.
Finding the right project to file against
List the projects, then read one by numeric ID or string identifier.
Working out who to assign something to
List the users and read one to confirm the account before assigning.
8 tools
Listed in project docs. Your client may show a different list.
create-issueget-issueupdate-issuelist-projectsget-projectlist-usersget-userBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- npm on PATH
- REDMINE_API_KEY in your environment
- REDMINE_BASE_URL in your environment
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
git clone https://github.com/tamu960925/mcp-redmine.git
cd mcp-redmine
npm install
npm run build
export REDMINE_BASE_URL="<YOUR_REDMINE_URL>"
export REDMINE_API_KEY="<YOUR_REDMINE_API_KEY>"
npm startThe project documents no client configuration. npm start runs node dist/index.js, so an entry for your client runs node with the full path to dist/index.js in your clone, and sets REDMINE_BASE_URL and REDMINE_API_KEY in its "env" section: an app opened from its icon or dock does not see variables exported in a terminal.