Redmine AI Helper plugin
A Redmine plugin with AI chat, issue summaries and an MCP server: an external agent works with Redmine issues via an API key.
- 107 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent creates and changes issues with user rights and issue content goes to the chosen AI model.
Install
- Works in
Manual install
git clone https://github.com/haru/redmine_ai_helper.gitThe first README step, run inside `{REDMINE_ROOT}/plugins/`; then `bundle install` and plugin migrations.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent creates and changes issues with user rights and issue content goes to the chosen AI model.
This is third-party code. Review the repository files before installing.
What it does
Redmine AI Helper adds an AI assistant to Redmine 6. Inside Redmine it runs chat, writes issue summaries, comment drafts and subtasks, finds similar issues and duplicates, suggests assignees, fixes typos, completes descriptions and wiki text and builds a project health report. For agents the plugin has two MCP directions. The first connects external MCP servers (Slack, GitHub and others) to the chat through `config/ai_helper/config.json`. The second exposes Redmine itself as an MCP server at `/ai_helper/mcp` (Streamable HTTP, sessionless). Requests carry the `X-Redmine-API-Key` header and rights are limited to that user role. Tool groups include issue work: `read_issues`, `search_issues`, `create_new_issue`, `update_issue`.
Who it is for. Redmine administrators who want to give Claude Desktop or other agents access to issues within a user rights.
Good fit when
- An agent finds similar and duplicate issues on request.
- A long issue needs a summary and a list of subtasks.
- A manager reviews the project health report and its history.
- An issue summary is sent to a messenger through a connected MCP server.
Not a fit when
- Redmine older than 6.0 or Ruby older than 3.2.
- Only external MCP access to issues is needed, without chat and the rest of the plugin.
- Issue data cannot be sent to the chosen models.
Example request
Find issues in the project similar to this one and suggest which to close as duplicates.Limitations
Redmine 6.0 or newer and Ruby 3.2 or newer are required; Ruby 3.1 is no longer supported. The plugin goes into the `plugins` folder, then `bundle install` and migrations run. The MCP endpoint is enabled in plugin settings; without that, requests are refused. Issue content goes to the chosen model through plugin settings. SSE transport is not supported. The server does not implement change subscriptions. External MCP servers are described in a config, and Slack and GitHub keys sit in a file on the Redmine server.
How to disable. Disable the MCP Server option in plugin settings and remove `plugins/redmine_ai_helper` after rolling back migrations. Revoke user API keys in Redmine.
FAQ
How do I enable the MCP endpoint?
Open AI Helper settings under Administration and enable "MCP Server", restarting Redmine if needed.
How does the agent authenticate?
With the `X-Redmine-API-Key` header holding the user key. Without a valid key the answer is 401.
Can Slack or GitHub be connected to the chat?
Yes, through `config/ai_helper/config.json`: `stdio` and `http` transports work, plain `http://` is allowed only for localhost.
Does the agent go beyond user rights?
No. The chat, chat gateway and MCP server read and write no more than the requesting user role permits.
How do I install it?
Clone the repository into `plugins/`, run `bundle install` and `bundle exec rake redmine:plugins:migrate RAILS_ENV=production`, then restart Redmine.
Discussion
No questions or reviews yet.
Related
Pluginsredmine-cli runs Redmine issues and time tracking from a terminal and exposes them to agents as a skill or MCP server
MCP Redmine restricts files to approved directories, and administrators can limit read-only work to GET requests.
Redmine MCP Server: issues and time tracking
Redmine MCP Server
An MCP server for Redmine: issues, projects, wikis, time tracking and files, a read-only mode and per-user OAuth2 sign-in
Jira MCP in Go: an agent searches issues by JQL, runs sprints, comments and worklogs and sees an issue's branches and pull requests on Cloud and Server
A plugin that works Jira from the agent terminal: JQL search, issues, sprints, worklogs and wiki markup validation
Miro's official plugins, skills and MCP: the agent reads boards, draws diagrams, keeps tables and codes from designs
README in short
The README lists plugin features, installation, basic and advanced setup, permissions, the data access policy and MCP configuration.