v2.5.0: File uploads on issues, per-user API keys

Highlights

You can now attach files directly when creating or updating issues. Both create_redmine_issue and update_redmine_issue accept an uploads parameter that resolves files from base64 content, a URL, or a path on the server's disk, and attachments can land on a journal note when combined with notes. On-disk sources are gated by a new REDMINE_MCP_UPLOAD_FILE_ROOTS allowlist.

For Redmine instances too old for OAuth, the new legacy-per-user auth mode gives each request its own identity via an X-Redmine-API-Key header. It is opt-in and fail-closed, keys are redacted from logs, and an optional identity audit is available.

Tracker workflows also get easier: a new list_project_trackers tool discovers project-scoped trackers, and issues now expose a tracker field. RedmineUP Checklists users gain a create_checklist_item tool.

Changes

Added

• uploads parameter on create_redmine_issue and update_redmine_issue to attach files to issues, or to a journal note when combined with notes
• Files resolvable from content_base64, source_url, or a new on-disk file_path source
• file_path source in upload_file for files already on the server
• REDMINE_MCP_UPLOAD_FILE_ROOTS setting to allowlist file_path upload directories, defaulting to ATTACHMENTS_DIR
• legacy-per-user auth mode: per-request Redmine API key via X-Redmine-API-Key header, opt-in and fail-closed (REDMINE_PER_USER_TRUST_PROXY required), keys redacted from logs, optional identity audit via REDMINE_PER_USER_AUDIT_IDENTITY
• tracker field in issue output and in the fields selector for issue listing and search tools
• list_project_trackers tool for project-scoped tracker discovery
• create_checklist_item tool for RedmineUP Checklists, plus is_section in checklist output

Installation

pip install redmine-mcp-server==2.5.0

Links

• PyPI Package
• MCP Registry
• Full Changelog