Labsco
MCP SERVER

Redmine

by tamu960925

Redmine issues, projects and users read and written over the REST API, with filtering on every list call.

Project & Task Management
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

One command plus a key — npx -y mcp-redmine, then supply credentials