A Model Context Protocol (MCP) server for integrating with Redmine project management systems. This server provides AI applications with the ability to interact with Redmine instances for project management, issue tracking, and time logging.
get_issues- Retrieve issues with optional filtering by project, status, assigneeget_projects- List available Redmine projectsget_project_memberships- Get users and groups assigned to a project with their rolescreate_issue- Create new issues in Redmine projectsget_time_entries- Retrieve time entries with filtering optionslog_time- Log time spent on issues or projects
- redmine://projects - List of all accessible projects
- redmine://issues/recent - Recently updated issues
- redmine://time_entries/recent - Recently logged time entries
- issue_summary - Generate comprehensive project issue summaries
- time_report - Create detailed time tracking reports
- Node.js 22+
- Access to a Redmine instance with API key
- Redmine REST API enabled
Set the following environment variables:
export REDMINE_URL="https://your-redmine-instance.com"
export REDMINE_API_KEY="your_api_key_here"- Clone or download this repository
- Install dependencies:
npm install
- Build the server:
npm run build
Clone this repository and create the file .vscode/mcp.json with following
contents:
{
"servers": {
"redmine-mcp-server": {
"type": "stdio",
"command": "node",
"args": ["build/src/index.js"],
"env": {
"REDMINE_URL": "your URL here",
"REDMINE_API_KEY": "your API key here"
}
}
}
}API documentation is automatically generated from JSDoc comments and deployed to GitHub Pages:
To generate documentation locally:
npm run docsThe generated documentation will be available in the docs/ directory.
npm run buildnpm run lint
npm run formatThis project uses Vitest as its testing framework, providing fast test execution, watch mode, and comprehensive coverage reports.
# Run all tests
npm test
# Run tests once and exit
npm run test:run
# Run only e2e tests
npm run test:e2e
# Run tests with UI
npm run test:ui
# Run tests with coverage
npm run test:coverageCode coverage is automatically collected and reported in the CI pipeline using Vitest's built-in coverage support with the V8 provider. Coverage reports are:
- Generated for every test run in CI
- Uploaded as workflow artifacts (available for 30 days)
- Displayed in the GitHub Actions workflow summary
- Stored in the
coverage/directory locally
To generate coverage locally:
npm run test:coverageCoverage reports include:
- HTML report: Open
coverage/index.htmlin your browser for detailed line-by-line coverage - JSON summary:
coverage/coverage-summary.jsoncontains overall metrics - Text output: Coverage percentages displayed in the terminal
The coverage configuration excludes test files, configuration files, and build artifacts to focus on source code coverage.
test/e2e/- End-to-end tests using Docker and Playwright
Tests use Vitest's describe, it, and expect API:
import { describe, it, expect } from "vitest";
describe("My Feature", () => {
it("should work correctly", () => {
expect(1 + 1).toBe(2);
});
});npx @modelcontextprotocol/inspector node build/src/index.js