mcp-server-redmine
An MCP server (stdio) that gives AI agents full read/write access to a Redmine instance's REST API through 34 tools.
Issues (stable): list with filters (project, status, tracker, assignee, priority, sort, pagination), get details with journals/attachments, create, update (incl. notes/comments and custom fields), and permanently delete issues, optionally attaching uploaded files.
Issue relations (alpha): list, get, create (relates, blocks, duplicates, precedes, follows, etc.), and delete relations between issues.
Projects (stable): list accessible projects, get by slug or ID, create, and update projects.
Users & account (stable): list users (admin), get a user, and fetch the authenticated user's profile or full account details including API key.
Time tracking (stable): list entries with project/issue/user/date filters, get one, log hours, update, and delete time entries.
Wiki pages (alpha): list, read, create/update (with version to avoid overwriting concurrent edits), and delete pages.
Files & attachments (alpha): list project files, upload a local file to get an attachment token (optionally restricted to
REDMINE_UPLOAD_DIR), download attachments (images inline, text inline/truncated, others as metadata), and attach uploaded files to a project's Files module.Search (alpha): full-text search across issues, wiki pages, news, documents, changesets, messages, projects, and attachments with scope and filtering options.
News (alpha): list news articles globally or scoped to a project.
Roles (alpha): list roles and get role details including permissions.
Allows interaction with the Redmine REST API, providing tools for managing issues, issue relations, projects, users, time entries, wiki pages, news, files, search, and roles within a Redmine instance.
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., "@mcp-server-redmine 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.
mcp-server-redmine
MCP server for the Redmine REST API. Exposes 34 tools covering Issues, Issue Relations, Projects, Users, My Account, Time Entries, Wiki Pages, News, Files, Search, and Roles via stdio transport.
Installation
For Codex, follow Codex Setup to register the server directly with
codex mcp add. No separate package installation is required.
To install the package as a project dependency:
pnpm add mcp-server-redmineOr use directly via npx:
npx -y mcp-server-redmineRelated MCP server: Redmine MCP Server
Configuration
Two environment variables are required, and one is optional:
Variable | Description |
| Base URL of your Redmine instance, e.g. |
| Your Redmine API access key (found in My account → API access key) |
| Optional. Absolute path; when set, |
Codex Setup
Make sure Node.js (including npx) and the Codex CLI are installed. Replace the
Redmine URL and API key below with your own values, then run:
codex mcp add redmine \
--env REDMINE_URL=https://redmine.example.com \
--env REDMINE_API_KEY=your-api-key \
-- npx -y mcp-server-redmineThis registers the stdio server in ~/.codex/config.toml. Codex launches it through
npx, which downloads the package when needed. The -y flag skips the package
installation prompt.
To restrict uploads, include --env REDMINE_UPLOAD_DIR=/absolute/path/to/uploads
before -- npx in the command above.
Verify that the server is registered:
codex mcp listStart a new Codex CLI session and run /mcp to check the active server and its tools.
Manual configuration
Alternatively, add the following to ~/.codex/config.toml, replacing the placeholder
values. Use either this method or the CLI command above.
[mcp_servers.redmine]
command = "npx"
args = ["-y", "mcp-server-redmine"]
[mcp_servers.redmine.env]
REDMINE_URL = "https://redmine.example.com"
REDMINE_API_KEY = "your-api-key"
# Optional: restrict uploads to this directory.
# REDMINE_UPLOAD_DIR = "/absolute/path/to/uploads"See the official MCP documentation for more Codex configuration options.
Claude Desktop Setup
Add to claude_desktop_config.json:
Note: In Claude Desktop, open Settings → Developer → Edit Config. This opens (or creates)
claude_desktop_config.jsonin your default editor. After saving, fully quit Claude Desktop (not just minimize) and reopen it for the changes to take effect.
{
"mcpServers": {
"redmine": {
"command": "npx",
"args": ["mcp-server-redmine"],
"env": {
"REDMINE_URL": "https://redmine.example.com",
"REDMINE_API_KEY": "your-api-key"
}
}
}
}Claude Code Setup
Run from your project root:
claude mcp add-json redmine '{"command":"npx","args":["mcp-server-redmine"],"env":{"REDMINE_URL":"https://redmine.example.com","REDMINE_API_KEY":"your-api-key"}}'Or add manually to .mcp.json at the root of your project:
{
"mcpServers": {
"redmine": {
"command": "npx",
"args": ["mcp-server-redmine"],
"env": {
"REDMINE_URL": "https://redmine.example.com",
"REDMINE_API_KEY": "your-api-key"
}
}
}
}Tools
Issues
Tool | Status | Description |
| ✓ | List issues with filters: project, status, tracker, assignee, priority, pagination |
| ✓ | Get a single issue by numeric ID |
| ✓ | Create a new issue in a project, optionally attaching uploaded files |
| ✓ | Update fields on an existing issue, optionally attaching uploaded files |
| ✓ | Permanently delete an issue |
Issue Relations
Tool | Status | Description |
| ⚠ | List all relations for a given Redmine issue |
| ⚠ | Get a single relation by its numeric ID |
| ⚠ | Create a relation between two issues (relates, blocks, precedes, duplicates, …) |
| ⚠ | Permanently delete a relation |
Projects
Tool | Status | Description |
| ✓ | List all accessible projects |
| ✓ | Get a project by identifier (slug) or numeric ID |
| ✓ | Create a new project |
| ✓ | Update an existing project |
Users
Tool | Status | Description |
| ✓ | List users (requires admin privileges) |
| ✓ | Get a user by numeric ID |
| ✓ | Get the authenticated user's profile |
My Account
Tool | Status | Description |
| ⚠ | Get the authenticated user's account details, API key, and custom fields |
Time Entries
Tool | Status | Description |
| ✓ | List time entries with filters: project, issue, user, date range |
| ✓ | Get a single time entry by numeric ID |
| ✓ | Log hours against an issue or project |
| ✓ | Update an existing time entry |
| ✓ | Permanently delete a time entry |
Wiki Pages
Tool | Status | Description |
| ⚠ | List all wiki pages in a project |
| ⚠ | Get wiki page content by project and title |
| ⚠ | Create or update a wiki page |
| ⚠ | Permanently delete a wiki page (requires admin) |
News
Tool | Status | Description |
| ⚡ | List news articles with optional project filtering |
Files
Tool | Status | Description |
| ⚠ | List all files in a project with metadata |
| ⚠ | Upload a local file and get an attachment token for issues or project files |
| ⚠ | Download an attachment; images and text are returned inline as context |
| ⚠ | Add an already-uploaded file (by token) to a project's Files module |
Search
Tool | Status | Description |
| ⚠ | Search issues, wiki pages, news, documents, changesets, messages, and projects |
Roles
Tool | Status | Description |
| ⚠ | List all roles with IDs and names |
| ⚠ | Get role details including permissions |
API Stability
The tools follow Redmine's API resource stability levels:
Status | Meaning |
✓ Stable | Feature complete, no major changes planned |
⚠ Alpha | Major functionality in place, needs feedback from integrators |
⚡ Prototype | Rough implementation, possible breaking changes. Not recommended for production |
Development
# Install dependencies
pnpm install
# Build
pnpm build
# Watch mode
pnpm dev
# Tests
pnpm test
# Type check
pnpm typecheckContributing
Contributions are welcome! Please read the Contributing Guide for setup instructions, the project structure, and how to add a new tool. Bug reports and feature requests go through the issue templates.
Security
Found a vulnerability? Please report it privately — see our Security Policy. Do not open a public issue for security problems.
License
MIT © Jesus Reikel Lopez Martin
Available Tools
34 toolscreate_issue_relationC
[Alpha] Create a relation between two Redmine issues. Supported types: relates, duplicates, duplicated, blocks, blocked, precedes, follows, copied_to, copied_from.
Inputs: issue_id (required), issue_to_id (required), delay, relation_type.
delete_issue_relationA
[Alpha] Permanently delete a Redmine issue relation by its numeric ID. This action cannot be undone.
Inputs: id (required).
get_issue_relationC
[Alpha] Get a single Redmine issue relation by its numeric ID.
Inputs: id (required).
list_issue_relationsA
[Alpha] List all relations for a given Redmine issue. Returns each relation's ID, related issue ID, type, and optional delay.
Inputs: issue_id (required).
redmine_create_issueC
[Stable] Create a new Redmine issue. Returns the created issue with its assigned ID.
Inputs: subject (required), project_id (required), uploads, due_date, +10 more.
redmine_create_projectC
[Stable] Create a new Redmine project. Returns the created project.
Inputs: name (required), identifier (required), is_public, description, +1 more.
redmine_delete_issueA
[Stable] Permanently delete a Redmine issue and all its journals and attachments. This action cannot be undone.
Inputs: id (required).
redmine_delete_time_entryB
[Stable] Permanently delete a Redmine time entry. This action cannot be undone.
Inputs: id (required).
redmine_delete_wiki_pageA
[Alpha] Permanently delete a Redmine wiki page. Requires admin privileges. This action cannot be undone.
Inputs: title (required), project_id (required).
redmine_download_attachmentA
[Alpha] Download a Redmine attachment by its numeric ID (find IDs with redmine_get_issue using include=attachments). Raster images (png, jpeg, gif, webp) are returned as viewable image content; text files, including JSON and SVG, are returned inline (long ones truncated); other types, images over 3.5 MB, and text over 5 MB return metadata instead.
Inputs: attachment_id (required).
redmine_get_current_userA
[Stable] Get the details of the currently authenticated Redmine user (identified by REDMINE_API_KEY).
Inputs: no named parameters.
redmine_get_issueA
[Stable] Get full details of a single Redmine issue by its numeric ID, including description, status, dates, and optional extras like journals (comments) and attachments.
Inputs: id (required), include.
redmine_get_my_accountA
[Stable] Get the full account details of the currently authenticated Redmine user, including email address, API key, and custom fields.
Inputs: no named parameters.
redmine_get_projectA
[Stable] Get details of a single Redmine project by its identifier (string slug) or numeric ID.
Inputs: id (required).
redmine_get_roleB
[Alpha] Get detailed information about a role including permissions, visibility settings, and assignability (requires Redmine 2.2+).
Inputs: id (required).
redmine_get_time_entryA
[Stable] Get details of a single time entry by its numeric ID.
Inputs: id (required).
redmine_get_userC
[Stable] Get details of a single Redmine user by numeric ID.
Inputs: id (required), include.
redmine_get_wiki_pageC
[Alpha] Get the content and metadata of a Redmine wiki page by project and page title.
Inputs: title (required), project_id (required).
redmine_list_filesC
[Alpha] List all files in a Redmine project. Returns file metadata including name, size, type, author, and download URL.
Inputs: project_id (required), limit, offset.
redmine_list_issuesA
[Stable] List Redmine issues with optional filters. Returns paginated results with issue ID, subject, status, priority, and assignee. Use this to browse or search for issues before fetching details.
Inputs: sort, limit, offset, include, +5 more.
redmine_list_newsA
[Alpha] List Redmine news articles. Returns paginated results with title, summary, author, project, and creation date. Omit project_id to fetch news across all projects, or provide it to scope results to a single project.
Inputs: limit, offset, project_id.
redmine_list_projectsB
[Stable] List all Redmine projects the API user has access to, with pagination support.
Inputs: limit, offset, include.
redmine_list_rolesB
[Alpha] List all roles in the Redmine instance. Returns role IDs and names for role assignment.
Inputs: limit, offset.
redmine_list_time_entriesC
[Stable] List Redmine time entries with optional filters. Returns hours logged, activity, issue, and project for each entry.
Inputs: to, from, limit, offset, +3 more.
redmine_list_usersB
[Stable] List Redmine users. Requires admin privileges. Returns user IDs, login names, and email addresses.
Inputs: name, limit, offset, status, +1 more.
redmine_list_wiki_pagesC
[Alpha] List all wiki pages in a Redmine project.
Inputs: project_id (required).
redmine_log_timeB
[Stable] Log time against a Redmine issue or project. Either issue_id or project_id is required. Returns the created time entry.
Inputs: hours (required), activity_id (required), comments, issue_id, +2 more.
redmine_searchB
[Alpha] Search Redmine content across issues, wiki pages, news, documents, changesets, messages, projects, and attachments. Use this to discover related work before fetching details.
Inputs: q (required), news, limit, scope, +11 more.
redmine_update_issueB
[Stable] Update an existing Redmine issue. Only provided fields are changed. Use 'notes' to add a journal comment.
Inputs: id (required), notes, subject, uploads, +11 more.
redmine_update_projectB
[Stable] Update an existing Redmine project. Only provided fields are changed.
Inputs: id (required), name, is_public, description, +1 more.
redmine_update_time_entryC
[Stable] Update an existing Redmine time entry. Only provided fields are changed.
Inputs: id (required), hours, comments, spent_on, +1 more.
redmine_update_wiki_pageA
[Alpha] Create or update a Redmine wiki page. If the page does not exist, it will be created. IMPORTANT: Always fetch the page first with redmine_get_wiki_page and pass the current 'version' number to avoid silently overwriting concurrent edits.
Inputs: text (required), title (required), project_id (required), version, +1 more.
redmine_upload_attachmentA
[Alpha] Upload a local file to Redmine and get an attachment token. Reads the file at the given absolute path and posts its content to Redmine's attachment API. Pass the returned token in the 'uploads' array of redmine_create_issue or redmine_update_issue to attach the file to an issue, or to redmine_upload_file to add it to a project's Files module. If the server is configured with REDMINE_UPLOAD_DIR, only files inside that directory can be uploaded.
Inputs: file_path (required), filename, content_type.
redmine_upload_fileA
[Alpha] Add an already-uploaded file to a Redmine project's Files module. First call redmine_upload_attachment to get an upload token, then pass that token here to associate the file with the project.
Inputs: token (required), project_id (required), filename, version_id, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 34 tools
Most tools target distinct Redmine resources and actions, and the upload/download/attachment sequence is clarified in descriptions. The main ambiguity is between redmine_get_current_user and redmine_get_my_account, which both retrieve the authenticated user with subtly different detail levels.
Nearly all tools use a predictable redmine_verb_noun snake_case pattern. The four issue-relation tools omit the redmine_ prefix, which is a visible but minor inconsistency.
At 34 tools, the surface is quite large and increases selection load even though Redmine is a broad domain. Many tools are justified by issues, projects, time entries, wiki, files, users, roles, and relations, but the total is still heavy.
Core issue, project, time-entry, wiki, file, relation, and search workflows are covered, but several areas are partial: news and roles are read-only, users lack create/update/delete, and common metadata endpoints such as statuses, trackers, and priorities are missing.
Maintenance
Related MCP Connectors
Reddit API as 69 MCP tools: search, subreddits, posts, comments, users, monitors, writes, feedback.
Read and update tickets, deals, tasks, and contacts in 18 Cores Tracker.
Read Weblate projects, strings, stats and changes; translate, suggest, comment and autotranslate.
Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Redmine projects, issues, users, time entries, memberships, groups, versions, custom fields, and queries via 53 API endpoints, with OAuth authentication.1MIT
- AlicenseBqualityDmaintenanceMCP server for Redmine project management, enabling tools for managing projects, issues, users, time entries, groups, memberships, versions, wiki, news, attachments, search, and Agile sprints via the Redmine REST API.891MIT
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for interacting with Redmine, including issues, projects, wiki pages, time entries, and more.1MIT
- AlicenseAqualityCmaintenanceA local Model Context Protocol server (stdio) for Redmine that allows you to work with Redmine issues, projects, and time entries directly from your editor.1267 npmMIT