Redmine MCP Server
Provides tools to interact with a Redmine instance, including managing projects, issues, users, time entries, groups, memberships, versions, issue categories, issue relations, wiki pages, news, attachments, files, search, enumerations, catalogs, roles, journals, and Agile Sprints (via the RedmineUP Agile plugin).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Redmine MCP Server list my open issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Redmine MCP Server
MCP (Model Context Protocol) server for Redmine, built with TypeScript.
Requirements
Node.js 18+
A Redmine instance with REST API enabled
Redmine API Key
Related MCP server: Redmineflux MCP Server
Installation
npm install
npm run buildConfiguration
Environment variables:
Variable | Description | Required |
| Redmine base URL (e.g. | Yes |
| Redmine API Key | Yes |
Usage with VS Code / Claude Desktop
Add to your MCP configuration file:
{
"mcpServers": {
"redmine": {
"command": "npx",
"args": ["-y", "redmine-server-mcp@latest"]
"env": {
"REDMINE_URL": "https://redmine.example.com",
"REDMINE_API_KEY": "your-api-key"
}
}
}
}Available Tools
Projects (7)
list_projects— List projectsget_project— Project detailscreate_project— Create projectupdate_project— Update projectarchive_project— Archive projectunarchive_project— Unarchive projectdelete_project— Delete project
Issues (7)
list_issues— List issues with filtersget_issue— Issue detailscreate_issue— Create issueupdate_issue— Update issuedelete_issue— Delete issueadd_watcher— Add watcherremove_watcher— Remove watcher
Users (8)
list_users— List usersget_user— User detailscreate_user— Create userupdate_user— Update userdelete_user— Delete userget_current_user— Current userget_my_account— My accountupdate_my_account— Update my account
Time Entries (5)
list_time_entries— List time entriesget_time_entry— Detailscreate_time_entry— Createupdate_time_entry— Updatedelete_time_entry— Delete
Groups (7)
list_groups,get_group,create_group,update_group,delete_groupadd_user_to_group,remove_user_from_group
Memberships (5)
list_project_memberships,get_membership,create_project_membership,update_membership,delete_membership
Versions (5)
list_project_versions,get_version,create_version,update_version,delete_version
Issue Categories (5)
list_issue_categories,get_issue_category,create_issue_category,update_issue_category,delete_issue_category
Issue Relations (4)
list_issue_relations,get_issue_relation,create_issue_relation,delete_issue_relation
Wiki (5)
list_wiki_pages,get_wiki_page,get_wiki_page_version,create_or_update_wiki_page,delete_wiki_page
News (5)
list_all_news,list_project_news,get_news,create_news,update_news
Attachments & Files (6)
get_attachment,update_attachment,delete_attachment,upload_filelist_project_files,create_project_file
Search (2)
search,search_in_project
Enumerations (3)
list_issue_priorities,list_time_entry_activities,list_document_categories
Catalogs (4)
list_trackers,list_issue_statuses,list_custom_fields,list_queries
Roles (2)
list_roles,get_role
Journals (1)
update_journal
Agile Sprints — RedmineUP Agile plugin (7)
Requires the RedmineUP Agile plugin installed in your Redmine instance.
list_agile_sprints— List sprints of a projectget_agile_sprint— Sprint detailscreate_agile_sprint— Create sprintupdate_agile_sprint— Update sprintdelete_agile_sprint— Delete sprintget_issue_agile_data— Get sprint, story points and position of an issueassign_issue_to_sprint— Assign (or remove) an issue to a sprint
Development
npm run dev # Run in development mode
npm test # Run tests
npm run build # Production buildArchitecture
The project follows Clean Architecture:
src/
├── domain/ # Types, interfaces, errors
├── application/ # Services (interfaces) and use cases
└── infrastructure/ # Controllers (HTTP), MCP server, utilsLicense
MIT
Available Tools
89 toolsadd_user_to_groupB
Adds a user to a group.
Inputs: group_id (required), user_id (required).
add_watcherB
Adds a user as watcher/observer to an issue.
Inputs: issue_id (required), user_id (required).
archive_projectA
Archives a project, making it read-only.
Inputs: id (required).
assign_issue_to_sprintA
Assigns an issue to a sprint (or removes it by passing null). Requires the RedmineUP Agile plugin.
Inputs: issue_id (required), agile_sprint_id (required).
create_agile_sprintB
Creates a new sprint in a project. Requires the RedmineUP Agile plugin.
Inputs: project_id (required), name (required), start_date, end_date, +2 more.
create_groupB
Creates a new group in Redmine.
Inputs: name (required), user_ids.
create_issueC
Creates a new issue in Redmine.
Inputs: project_id (required), subject (required), tracker_id, status_id, +14 more.
create_issue_categoryB
Creates a new issue category in a project.
Inputs: project_id (required), name (required), assigned_to_id.
create_issue_relationC
Creates a relation between two issues.
Inputs: issue_id (required), issue_to_id (required), relation_type (required), delay.
create_newsC
Creates a news item in a project.
Inputs: project_id (required), title (required), description (required), summary.
create_or_update_wiki_pageA
Creates or updates a wiki page. Uses PUT (idempotent by title). If the page exists it updates it, otherwise creates it.
Inputs: project_id (required), title (required), text (required), comments, +2 more.
create_projectC
Creates a new project in Redmine.
Inputs: name (required), identifier (required), description, homepage, +10 more.
create_project_fileA
Adds a previously uploaded file to a project. Requires a token obtained from upload_file.
Inputs: project_id (required), token (required), filename (required), description, +1 more.
create_project_membershipB
Adds a user or group to a project with the specified roles.
Inputs: project_id (required), role_ids (required), user_id, group_id.
create_time_entryB
Creates a new time entry. Requires either issue_id or project_id, and hours.
Inputs: hours (required), issue_id, project_id, activity_id, +4 more.
create_userB
Creates a new user in Redmine. Requires admin privileges.
Inputs: login (required), firstname (required), lastname (required), mail (required), +10 more.
create_versionB
Creates a new version (milestone) in a project.
Inputs: project_id (required), name (required), status, sharing, +3 more.
delete_agile_sprintC
Deletes a sprint from a project. Requires the RedmineUP Agile plugin.
Inputs: project_id (required), sprint_id (required).
delete_attachmentA
Deletes an attachment by its ID.
Inputs: id (required).
delete_groupB
Deletes a group permanently.
Inputs: id (required).
delete_issueC
Deletes an issue permanently.
Inputs: id (required).
delete_issue_categoryA
Deletes an issue category. Optionally reassigns its issues to another category.
Inputs: id (required), reassign_to_id.
delete_issue_relationB
Deletes an issue relation.
Inputs: id (required).
delete_membershipB
Removes a membership (user/group) from a project.
Inputs: id (required).
delete_projectA
Deletes a project and all its related data (issues, wiki, etc.).
Inputs: id (required).
delete_time_entryA
Deletes a time entry permanently.
Inputs: id (required).
delete_userA
Deletes a user permanently. Requires admin privileges.
Inputs: id (required).
delete_versionC
Deletes a version.
Inputs: id (required).
delete_wiki_pageB
Deletes a wiki page from a project.
Inputs: project_id (required), title (required).
get_agile_sprintA
Gets details of a specific sprint. Requires the RedmineUP Agile plugin.
Inputs: project_id (required), sprint_id (required).
get_attachmentA
Gets metadata of an attachment by its ID (filename, filesize, content_type, content_url, author, etc.).
Inputs: id (required).
get_current_userA
Gets the details of the currently authenticated user (the API key owner).
Inputs: include.
get_groupA
Gets details of a group by its numeric ID. Can include users and memberships.
Inputs: id (required), include.
get_issueA
Gets full details of a single issue by its numeric ID, optionally including related data.
Inputs: id (required), include.
get_issue_agile_dataB
Gets the agile fields (sprint, story points, position) of an issue. Requires the RedmineUP Agile plugin.
Inputs: issue_id (required).
get_issue_categoryB
Gets details of a single issue category by its ID.
Inputs: id (required).
get_issue_relationA
Gets details of a single issue relation by its ID.
Inputs: id (required).
get_membershipA
Gets details of a single project membership by its ID.
Inputs: id (required).
get_my_accountA
Gets the account details of the currently authenticated user.
Inputs: no named parameters.
get_newsB
Gets details of a single news item by its ID.
Inputs: id (required), include.
get_projectA
Gets details of a project by its numeric ID or string identifier.
Inputs: id (required), include.
get_roleA
Gets details of a role by its ID, including its list of permissions.
Inputs: id (required).
get_time_entryA
Gets details of a single time entry by its numeric ID.
Inputs: id (required).
get_userA
Gets details of a user by their numeric ID. Can include memberships and groups.
Inputs: id (required), include.
get_versionB
Gets details of a single version by its ID.
Inputs: id (required).
get_wiki_pageA
Gets the content of a wiki page by its title. Returns the page text in Textile/Markdown format.
Inputs: project_id (required), title (required), include.
get_wiki_page_versionC
Gets a specific version of a wiki page. Useful for viewing page history.
Inputs: project_id (required), title (required), version (required), include.
list_agile_sprintsB
Lists all sprints of a project. Requires the RedmineUP Agile plugin.
Inputs: project_id (required).
list_all_newsB
Lists news from all projects. Returns news with pagination.
Inputs: offset, limit.
list_custom_fieldsA
Lists all custom fields defined in Redmine. Requires administrator privileges.
Inputs: no named parameters.
list_document_categoriesA
Lists all document categories defined in Redmine.
Inputs: no named parameters.
list_groupsB
Lists all groups in Redmine.
Inputs: offset, limit.
list_issue_categoriesB
Lists all issue categories of a project.
Inputs: project_id (required).
list_issue_prioritiesA
Lists all issue priorities defined in Redmine.
Inputs: no named parameters.
list_issue_relationsC
Lists all relations of an issue.
Inputs: issue_id (required).
list_issuesB
Lists issues in Redmine with advanced filters, sorting and pagination.
Inputs: offset, limit, sort, include, +14 more.
list_issues_by_sprintA
Lists all issues assigned to a specific sprint. Uses the RedmineUP Agile plugin filter. More efficient than list_issues when you need to filter by sprint.
Inputs: sprint_id (required), project_id, status_id, limit, +3 more.
list_issue_statusesA
Lists all issue statuses defined in Redmine.
Inputs: no named parameters.
list_project_filesB
Lists all files attached to a project (available since Redmine 3.4).
Inputs: project_id (required).
list_project_membershipsA
Lists all memberships (users/groups with roles) of a project.
Inputs: project_id (required), offset, limit.
list_project_newsB
Lists news of a specific project with pagination.
Inputs: project_id (required), offset, limit.
list_projectsA
Lists all projects in Redmine with pagination and optional filters.
Inputs: offset, limit, include, status, +7 more.
list_project_versionsB
Lists all versions (milestones) of a project.
Inputs: project_id (required).
list_queriesA
Lists all saved (public and private) queries in Redmine.
Inputs: no named parameters.
list_rolesB
Lists all roles defined in Redmine.
Inputs: no named parameters.
list_time_entriesA
Lists time entries in Redmine with optional filters by user, project, issue, activity and date range.
Inputs: offset, limit, user_id, project_id, +5 more.
list_time_entry_activitiesB
Lists all time entry activities defined in Redmine.
Inputs: no named parameters.
list_trackersA
Lists all trackers available in Redmine.
Inputs: no named parameters.
list_usersB
Lists users in Redmine with optional filters. Requires admin privileges.
Inputs: offset, limit, include, status, +11 more.
list_wiki_pagesB
Lists all wiki pages (index) of a project. Returns titles, versions and dates.
Inputs: project_id (required).
remove_user_from_groupC
Removes a user from a group.
Inputs: group_id (required), user_id (required).
remove_watcherC
Removes a user from the watchers of an issue.
Inputs: issue_id (required), user_id (required).
searchB
Performs a global search across all Redmine resources (issues, news, documents, changesets, wiki pages, messages, projects).
Inputs: q (required), scope, all_words, titles_only, +9 more.
search_in_projectB
Searches within a specific project's scope (issues, wiki pages, news, etc.).
Inputs: project_id (required), q (required), scope, all_words, +10 more.
unarchive_projectA
Unarchives a previously archived project.
Inputs: id (required).
update_agile_sprintA
Updates an existing sprint. Requires the RedmineUP Agile plugin.
Inputs: project_id (required), sprint_id (required), name, start_date, +3 more.
update_attachmentA
Updates metadata of an attachment (filename, description). Only available since Redmine 3.4.
Inputs: id (required), filename, description.
update_groupB
Updates an existing group.
Inputs: id (required), name, user_ids.
update_issueC
Updates an existing issue. Can change fields, add notes/comments, or change status.
Inputs: id (required), project_id, subject, tracker_id, +16 more.
update_issue_categoryB
Updates an existing issue category.
Inputs: id (required), name, assigned_to_id.
update_journalA
Updates the notes of an issue journal entry (comment). Requires the user to be the author or an admin.
Inputs: id (required), notes (required).
update_membershipB
Updates the roles of an existing project membership.
Inputs: id (required), role_ids (required).
update_my_accountB
Updates the account details of the currently authenticated user.
Inputs: firstname, lastname, mail, language, +3 more.
update_newsB
Updates an existing news item.
Inputs: id (required), title, description, summary.
update_projectC
Updates an existing project in Redmine.
Inputs: id (required), name, identifier, description, +11 more.
update_time_entryC
Updates an existing time entry.
Inputs: id (required), issue_id, project_id, hours, +5 more.
update_userC
Updates an existing user. Requires admin privileges.
Inputs: id (required), login, firstname, lastname, +12 more.
update_versionB
Updates an existing version.
Inputs: id (required), name, status, sharing, +3 more.
upload_fileA
Uploads a binary file to Redmine and returns an upload token. IMPORTANT: Redmine requires the request to use Content-Type: application/octet-stream for all file uploads — always set content_type to 'application/octet-stream', regardless of the actual file type. Using any other MIME type (e.g. 'image/png', 'application/pdf') will cause Redmine to reject the upload with HTTP 406. The returned token must be passed in the 'uploads' field when creating or updating issues, wiki pages, etc.
Inputs: filename (required), content_type (required), file_path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 89 tools
Most tools have clearly distinct purposes due to descriptive names and detailed descriptions. However, the large number (89) introduces some potential overlaps, such as multiple ways to list/filter issues (list_issues, list_issues_by_sprint, search, search_in_project) and get_issue_agile_data vs get_issue. These could cause misselection if descriptions are not carefully read.
Tool names consistently follow a verb_noun pattern (e.g., create_issue, list_projects, update_user). The verbs are well-chosen and indicate the action clearly. There are very few deviations (e.g., create_or_update_wiki_page), and overall the pattern is predictable and uniform.
With 89 tools, the count is high for a single server, but it reflects the broad scope of Redmine's functionality (multiple entities, CRUD, Agile plugin, etc.). While each tool serves a specific purpose, the server could benefit from consolidation (e.g., merging some list/get tools). The count is borderline excessive but not unreasonable for the domain.
The tool set covers CRUD operations for most Redmine entities (projects, issues, users, groups, versions, news, wiki, time entries, etc.) and includes specialized operations like agile sprints and file uploads. Minor gaps exist (e.g., no direct custom field value management, no workflow transitions), but overall the surface is comprehensive for typical use.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for Product Management
Remote MCP server to read and edit GanttFather projects: tasks, dates, dependencies, critical path.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server providing 63 tools to interact with Redmine instances, covering issues, projects, time entries, and wiki pages. It utilizes streamable HTTP transport and supports per-client authentication for secure management of Redmine resources.13 npm-
- FlicenseAqualityDmaintenanceAn MCP server that connects AI agents to Redmine project data, enabling natural language access to issues, projects, time entries, and more via the REST API.21-
- AlicenseBqualityDmaintenanceMCP server that provides access to the Redmine REST API, enabling issue tracking, project management, and more through natural language.2610 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.MIT