RedmineMCP MCP Server

If you want an AI assistant working directly with RedmineMCP, the redminemcp mcp server is the bridge. An integration between Claude AI (or any MCP client - Like Windsurf) and Redmine using the Model Context Protocol (MCP).

What RedmineMCP does

An integration between Claude AI (or any MCP client - Like Windsurf) and Redmine using the Model Context Protocol (MCP).

You can use the existing tooling like Jira MCP servers to accomplish this. We disagree with Jira's structure and design as Redmine allows entire Projects to be shifted or rehomed without issue. If you want an 100% OpenSource solution, keep reading.

Key capabilities

• Project Management — List and view Redmine projects with detailed information
• Issue Tracking — Create, update, list and view issues with full parameter support
• Parent-Child Relationships — Create and manage subtasks with hierarchical structure
• Issue Relations — Create, view, and manage issue relationships (relates, blocks, etc.)
• User Information — Access current user details and permissions
• Robust Error Handling — Detailed error reporting and parameter validation
• Mock Mode — Development and testing without requiring a Redmine instance

Installing the redminemcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 7 environment variables: REDMINE_URL, REDMINE_API_KEY, LOG_LEVEL, GITLAB_URL, GITLAB_TOKEN, GITLAB_PROJECT_ID, SYNC_GITHUB_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. RedmineMCP sits in that group. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by zacharyelston, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the redminemcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.