redmine

The Redmine MCP Server provides comprehensive access to Redmine's REST API via the Model Context Protocol. It enables MCP clients (such as Claude Desktop and similar tools) to perform nearly all REST operations against a Redmine instance, including issues, projects, users, time entries, wiki pages, files, attachments, queries, custom fields, and more. By default the server can operate in a read-only mode for safe data reference, and you can toggle write capabilities by setting the REDMINE_MCP_READ_ONLY environment variable. To start using it, configure your MCP client to point at the server (commonly via npx or Docker) with the required Redmine URL and API key, and an optional read-only flag. The server is designed to work across various clients and IDE integrations, including Claude Desktop, Claude Code, and Visual Studio Code, providing a consistent bridge to Redmine’s REST API.

Prerequisites:

• Node.js and npm (for npx usage) or Docker (for containerized deployment)
• A Redmine instance with an API key enabled (see prerequisites in the README)

Installation options:

1. Quick start with npx (no local installation required):

• Ensure Node.js and npm are installed
• Run the MCP server via npx with the required environment variables set in your MCP client configuration:

json { "mcpServers": { "redmine": { "command": "npx", "args": ["-y", "@onozaty/redmine-mcp-server"], "env": { "REDMINE_URL": "https://your-redmine.example.com", "REDMINE_API_KEY": "your-api-key-here", "REDMINE_MCP_READ_ONLY": "true" } } } }

2. Docker (alternative, containerized):

• Ensure Docker is installed
• Run the container with required environment variables:

bash docker run --rm -i
-e REDMINE_URL=https://your-redmine.example.com
-e REDMINE_API_KEY=your-api-key-here
-e REDMINE_MCP_READ_ONLY=true
ghcr.io/onozaty/redmine-mcp-server:latest

3. Local installation (if supported by the package):

• Install dependencies and run the server locally as per package documentation (refer to the npm package README for exact commands).

Environment variables:

• REDMINE_URL (required): Base URL of the Redmine instance
• REDMINE_API_KEY (required): API key generated in Redmine
• REDMINE_MCP_READ_ONLY (optional): 'true' enables read-only mode, any other value enables full access

Common issues and tips:

• Ensure the API key has necessary permissions in Redmine (administrative access is typical during setup)
• If REDMINE_URL uses a self-signed certificate, confirm TLS trust in the client environment
• For Docker deployments, use a stable image tag or the latest as needed and consider using a private registry in enterprise environments
• When using Claude or VSCode integrations, ensure the environment variables are correctly passed to the MCP server configuration

Configuration options:

• You can switch between read-only and read-write modes by changing REDMINE_MCP_READ_ONLY and restarting the MCP server.
• The server currently exposes the full REST API surface; you can selectively limit capabilities at the client side by avoiding write operations when in read-only mode.