Projects and members
List projects, review activity and versions, inspect modules, and manage project membership when the user has permission.
How it works
Give AI clients a controlled way to work with Redmine
Model Context Protocol is an open standard that lets AI clients use tools provided by external systems through a common interface. Redmine MCP provides that interface directly from within Redmine, without requiring a separate integration service.
- 60+
- built-in tools
- GPL v2+
- open-source license
- 6.0–7.0
- supported Redmine versions
What clients can do through Redmine MCP
The server exposes purpose-built MCP tools rather than unrestricted database access. Available tools depend on the current user's permissions, project access, and enabled extensions.
Issues and comments
Find, create and update issues, add notes and attachments, work with relations, subtasks, watchers and categories.
Search and saved queries
Search issues and Wiki pages, filter issue lists and run saved Redmine queries without rebuilding the filters in the client.
Time tracking
Read, create and update time entries, inspect activity types and import several entries in one operation.
Wiki and forums
Read, create and update project Wiki pages; browse forum boards, topics and message threads.
Files and attachments
List project files, upload files and attachments, inspect attachment metadata, and download supported attachments within documented limits.
Getting started
Install the plugin and connect a client
Installation follows the standard Redmine plugin workflow. An administrator enables MCP and assigns access; each user connects with their own Redmine API key.
- 1. Install Redmine MCPClone the git repository into the Redmine plugins directory
cd /path/to/redmine/plugins git clone https://github.com/rkteam/redmine_mcp.git - 2. Install dependenciesFrom the Redmine root directory, install dependencies and restart Redmine
cd /path/to/redmine bundle install - 3. Enable MCP and the REST APIEnable MCP in the plugin settings and enable the REST web service in Redmine's API settings.
- 4. Assign accessEnable the global “Use MCP” permission for the required roles. Administrators have MCP access automatically.
- 5. Configure the clientSet the MCP server URL to https://your-redmine.example.com/mcp and authenticate with the user's Redmine API key. The key is available under My account → API access key.
Cursor configuration example
.cursor/mcp.json{
"mcpServers": {
"redmine": {
"url": "https://your-redmine.example.com/mcp",
"headers": {
"X-Redmine-API-Key": "your_api_key"
}
}
}
}The exact MCP configuration format can vary by client version. Keep API keys out of source control.
Redmine stays in control of access
The plugin does not bypass Redmine's permission model. MCP access does not replace Redmine permissions and visibility rules; it adds an additional access check.
Permissions and visibility
Tools respect the authenticated user's existing Redmine permissions and visibility rules.
Read-only mode
Administrators can block create, update, and delete operations while keeping read-only tools available.
Safer write operations
Selected write operations include safeguards against conflicting updates and accidental duplicate resource creation.
Compatibility
Redmine 6.0–7.0 · REST API required
Built to be extended
Extend MCP from other Redmine plugins
Other Redmine plugins can register their own tools, resources, prompts, and capabilities through the Redmine MCP extension API, without modifying Redmine MCP itself. Administrators choose which detected extensions are enabled.
Redmine MCP FAQ
Redmine MCP currently supports Redmine 6.0–7.0. See the compatibility documentation for protocol and SDK versions.
Any MCP client that supports Streamable HTTP and custom HTTP headers can connect. The documentation includes a configuration example for Cursor.
Each user authenticates with their Redmine API key in the
X-Redmine-API-Keyheader. The REST API must be enabled in Redmine.Yes. The plugin checks the global “Use MCP” permission in addition to the authenticated user's existing Redmine permissions and visibility rules.
Yes. Read-only mode blocks create, update, and delete operations while keeping read tools available.
No. The MCP client only needs network access to Redmine's /mcp endpoint. The connection can be public or private, depending on where the client runs.
Yes. Other Redmine plugins can register their own tools, resources, prompts, and capabilities through the Redmine MCP extension API. Administrators choose which detected extensions are enabled. See the extension guide.
Review the source and install Redmine MCP
The repository contains installation steps, client configuration, the full tool reference and troubleshooting guidance.
Our Telegram Bot