redmine-mcp

Q: What can you do with this server?

This server gives read-only access to a Redmine instance (acting as one dedicated bot user), letting you browse and search projects, issues, time, wiki, attachments and reference data — no write tools are registered. * Identify the acting user: get_current_user returns the bot's Redmine user plus its memberships. * Browse projects: list_projects (paged) and get_project for trackers, issue categories, enabled modules and time-entry activities. * Query issues: search_issues with filters (status, project, tracker, assignee, subject, parent, version, date ranges, custom-field filters, saved queries, sorting) and get_issue for full detail including journals, attachments, relations, subtasks, watchers, changesets and allowed statuses. * Inspect time tracking: list_time_entries filtered by project, issue, user and date range. * Check releases/milestones: list_versions per project, including shared versions. * See who is involved: list_project_members with roles. * Read the wiki: list_wiki_pages for a project index and get_wiki_page for content, optionally an older version. * Full-text search: search across issues, news, documents, changesets, wiki pages, messages and projects (optionally scoped to a project, titles-only, open-issues-only). * Look up IDs for filtering: list_reference_data for issue statuses, trackers, priorities, time-entry activities, document categories, custom fields, saved queries, roles and groups. * Read attachments: get_attachment returns metadata and, for text files, content with a size cap. * Reach anything else read-only: redmine_get and redmine_list work over any redminelib resource (e.g. news, files, issue categories, deal statuses) with filters, paging and generic params.

Q: Which integrations are available for this server?

Provides read-only by default (optionally write-enabled) tools for interacting with Redmine via its REST API. Covers projects, issues, journals, time entries, versions, wiki pages, full-text search, reference data, attachments, and supported Redmine plugins for helpdesk, agile, CRM, and checklists. Write tools include creating/updating issues, logging time, managing relations, saving wiki pages, creating helpdesk tickets without customer email, managing sprints, adding CRM notes, and editing checklist items.

Q: How do I use redmine-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@redmine-mcp show my open issues assigned to me in Redmine" 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.

by expertZentrale

Overview Schema Source Related Servers Discussions Admin

Python

Remote

redmine – Claude-Code-Plugin mit Redmine-MCP-Server

MCP-Server für Redmine auf Basis von python-redmine-expert (redminelib). Er arbeitet als ein dedizierter Redmine-User über dessen API-Key und läuft standardmäßig read-only.

Abgedeckt: Standard-Redmine (Projekte, Issues, Journals, Zeiterfassung, Versionen, Wiki, Volltextsuche, Stammdaten), redmine_expert_helpdesk, redmine_expert_agile und die RedmineUP-Plugins (CRM, Helpdesk, Agile, Checklists). Für alles ohne eigenes Tool gibt es redmine_get / redmine_list (nur lesend) über alle Ressourcen der Library.

Read-only-Modus

Drei unabhängige Ebenen:

Tools: Mit read_only (Default) werden Schreib-Tools gar nicht registriert, Claude sieht sie nicht.
HTTP: Der Redmine-Client nutzt dann ReadOnlyEngine, die jeden Nicht-GET-Request blockiert, bevor er gesendet wird – auch aus Code-Pfaden, die kein Tool sind.
Redmine-Rechte: Der Bot-User darf nur, was seine Rolle erlaubt (siehe unten).

Auch im Schreibmodus gibt es bewusst keine Lösch-Tools und nichts, was Kunden mailt. Abgelehnt werden die Felder uploads (redminelib würde lokale Dateien lesen und hochladen) und helpdesk_init (würde den Kunden anmailen). api_key und password werden aus allen Ergebnissen entfernt.

Related MCP server: Redmine Enhanced MCP Server

Redmine vorbereiten

Administration → Einstellungen → API: „REST-Schnittstelle aktivieren“.
Neuen User anlegen, z. B. claude-bot (kein Administrator; Login per Passwort kann gesperrt bleiben).
Eigene Rolle anlegen, z. B. „Claude (lesend)“: Issues/Zeit/Wiki/Helpdesk ansehen. Für den Schreibmodus eine zweite Rolle mit den nötigen Bearbeiten-Rechten.
Den User nur in den Projekten als Mitglied mit dieser Rolle eintragen, auf die Claude zugreifen soll.
Als claude-bot anmelden (oder als Admin über „Benutzer → API-Schlüssel“) und den API-Schlüssel kopieren.

Hinweis: Änderungen erscheinen in Redmine als Aktionen von claude-bot, nicht des jeweiligen Menschen.

Installation als Plugin

Keine Voraussetzungen: weder Python noch uv. Beim ersten Start lädt bin/redmine-mcp (Windows: bin/redmine-mcp.cmd) das fertige Binary für die eigene Plattform aus dem GitHub-Release, prüft es gegen die SHA256-Summe in bin/SHA256SUMS und legt es im Plugin-Datenverzeichnis ab. Danach startet es sofort. Unterstützt: Linux x64/arm64, macOS Apple Silicon/Intel, Windows x64.

/plugin marketplace add expertZentrale/claude-redmine-mcp
/plugin install redmine@expert-redmine

Beim Aktivieren fragt Claude Code die Optionen ab (der API-Key wird als sensibel im Keychain gespeichert):

Option	Env-Variable	Default
`redmine_url`	`REDMINE_URL`	–	z. B. `https://redmine.example.com`
`redmine_api_key`	`REDMINE_API_KEY`	–	API-Key des Bot-Users
`read_only`	`REDMINE_READ_ONLY`	`true`	`false` schaltet die Schreib-Tools frei
`toolsets`	`REDMINE_TOOLSETS`	`standard`	`standard,expert_helpdesk,expert_agile,redmineup` / `all`
`verify_ssl`	`REDMINE_VERIFY_SSL`	`true`
–	`REDMINE_TIMEOUT`	`30`	Sekunden pro Request

Lokal testen ohne Installation: claude --plugin-dir /pfad/zu/claude-redmine-mcp, dann /mcp.

Ohne Plugin (nur MCP-Server)

Mit uv direkt aus dem Repo, ohne Binary:

claude mcp add redmine \
  -e REDMINE_URL=https://redmine.example.com -e REDMINE_API_KEY=... -e REDMINE_TOOLSETS=all \
  -- uvx --from git+https://github.com/expertZentrale/claude-redmine-mcp redmine-mcp

Tools

Toolset	Lesen	Schreiben (nur `read_only=false`)
`standard`	`get_current_user`, `list_projects`, `get_project`, `search_issues`, `get_issue`, `list_time_entries`, `list_versions`, `list_project_members`, `list_users`, `get_group`, `list_wiki_pages`, `get_wiki_page`, `search`, `list_reference_data`, `get_attachment`	`create_issue`, `update_issue`, `log_time`, `create_issue_relation`, `save_wiki_page`, `add_project_member`, `update_project_member`, `remove_project_member`, `create_group`, `add_group_users`, `remove_group_users` (Mitglieder: Recht „Mitglieder verwalten“, Gruppen/Benutzer: Admin-API-Key)
`expert_helpdesk`	`search_helpdesk_tickets` (Kunde, wartet auf Antwort, SLA), `list_helpdesk_tickets`, `get_helpdesk_ticket`, `list_helpdesk_contacts`, `get_helpdesk_contact`, `list_helpdesk_mailboxes`, `get_helpdesk_project_settings`, `list_helpdesk_kb_entries`, `get_helpdesk_kb_entry` (Wissensbasis)	`create_helpdesk_ticket` (ohne Mail an den Kunden), `create_helpdesk_kb_entry`, `update_helpdesk_kb_entry`, `curate_helpdesk_kb_entry` (freigeben/ablehnen)
`expert_agile`	`get_sprint_overview` (Story Points gesamt/erledigt, pro Person und Status), `list_sprints`, `get_sprint`, `get_issue_agile_data`	`create_sprint`, `update_sprint`, `update_issue_agile_data`
`redmineup`	`list_contacts`, `get_contact`, `list_deals`, `get_deal`, `list_redmineup_tickets`, `get_redmineup_ticket`, `list_redmineup_sprints`, `get_checklist`	`add_crm_note`, `add_checklist_item`, `update_checklist_item`
immer	`redmine_get`, `redmine_list`	–

Listen sind gepaged (Default 25, max. 100, next_offset im Ergebnis); lange Texte werden in Listen gekürzt.

Welche Informationen aus Redmine und den Plugins genutzt werden, über welche Endpunkte, mit welchen Filtern und welchen Rechten: docs/redmine-data.md.

Entwicklung

uv venv && uv pip install -e '.[dev]' -e ../python-redmine   # lokaler Library-Checkout statt Git-Tag
uv run pytest
uv run ruff check . && uv run ruff format --check .
npx @modelcontextprotocol/inspector uv run redmine-mcp       # mit REDMINE_* im Environment

Lokales Binary bauen und über den Launcher starten (REDMINE_MCP_BINARY überspringt den Download):

pyinstaller --noconfirm --onedir --name redmine-mcp packaging/entry.py
python packaging/smoke_test.py dist/redmine-mcp/redmine-mcp
REDMINE_MCP_BINARY=$PWD/dist/redmine-mcp/redmine-mcp claude --plugin-dir .

Release

Actions → Release → Run workflow mit der neuen Version (z. B. 0.2.0). Der Workflow baut alle Plattformen, testet jedes Binary per MCP-Handshake, veröffentlicht das GitHub-Release und schreibt erst danach Version und Prüfsummen (bin/version.txt, bin/SHA256SUMS, plugin.json) nach main. Nutzer erhalten die neue Version mit /plugin marketplace update expert-redmine.

Available Tools

17 tools

get_attachmentB

Read-onlyIdempotent

Metadata of an attachment and, for text files, optionally its content.

Inputs: attachment_id (required), max_chars, include_content.

get_current_userA

Read-onlyIdempotent

The Redmine user this server acts as, with its memberships.

Inputs: no named parameters.

get_groupC

Read-onlyIdempotent

A group with its users and project memberships (admin only).

Inputs: group_id (required).

get_issueC

Read-onlyIdempotent

A single issue with its history (journals), attachments, relations and subtasks.

Inputs: issue_id (required), include.

get_projectC

Read-onlyIdempotent

A project with its trackers, issue categories, enabled modules and time entry activities.

Inputs: project (required).

get_wiki_pageC

Read-onlyIdempotent

A wiki page with its text, optionally an older version.

Inputs: title (required), project (required), version.

list_project_membersC

Read-onlyIdempotent

Members of a project with their roles.

Inputs: project (required), limit, offset.

list_projectsB

Read-onlyIdempotent

Projects visible to the server's Redmine user.

Inputs: limit, offset.

list_reference_dataA

Read-onlyIdempotent

Ids and names needed for filters and changes: issue statuses, trackers, priorities, time entry activities, document categories, custom fields (admin only), saved queries, roles, groups (admin only).

Inputs: kind (required).

list_time_entriesD

Read-onlyIdempotent

Spent time entries.

Inputs: user, limit, offset, project, +3 more.

list_usersA

Read-onlyIdempotent

Active users with their ids, needed for memberships and groups (admin only).

Inputs: name, limit, offset, group_id.

list_versionsC

Read-onlyIdempotent

Versions (milestones/releases) of a project, including shared ones.

Inputs: project (required), limit, offset.

list_wiki_pagesC

Read-onlyIdempotent

Index of the wiki pages of a project.

Inputs: project (required), limit, offset.

redmine_getC

Read-onlyIdempotent

Any single Redmine resource by id (read-only).

Inputs: resource (required), resource_id (required), params.

redmine_listC

Read-onlyIdempotent

Any Redmine resource list, filtered or all (read-only). Unknown names return the list of resources.

Inputs: resource (required), limit, offset, filters.

searchC

Read-onlyIdempotent

Redmine full text search across issues, wiki pages, news, documents, changesets and forum messages.

Inputs: query (required), limit, types, offset, +3 more.

search_issuesA

Read-onlyIdempotent

Issues matching the filters (long descriptions are shortened, use get_issue for the full issue).

Inputs: sort, limit, offset, status, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.7/5.0

Scored 2026-10-29 04:55 across 17 tools

Disambiguation3/5

Specific getters and listers overlap with the generic redmine_get and redmine_list tools, which can retrieve any resource by id or list any resource. An agent may be unsure whether to use list_projects or redmine_list, or get_issue or redmine_get. Search vs search_issues is distinguishable, but the catch-all tools create real boundary ambiguity.

Naming Consistency4/5

Most names follow a snake_case verb_noun pattern such as get_issue, list_projects, and search_issues. However, redmine_get and redmine_list introduce an inconsistent server prefix, and bare search breaks the verb_noun pattern. The set is still readable overall.

Tool Count3/5

17 tools is just over the typical 3-15 range and feels heavy for a mostly read-only surface. The generic redmine_get and redmine_list tools could absorb several specific get/list tools, so not every tool clearly earns its place.

Completeness2/5

Read coverage is broad across issues, wiki pages, projects, users, groups, attachments, and generic resources. However, there are no write operations: no create/update issue, wiki edit, time logging, or attachment upload. For a Redmine server this is a significant lifecycle gap that will block common agent workflows.

Maintenance

ActivityMaintained

ResponsivenessOutdated data

Resources

Related MCP Connectors

Redbooth
com.redbooth
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
Project Management Workplace & Productivity
1
https://redbooth.com/api/mcp
TimeUno
io.timeuno
Read your tracked time and projects, pause tracking or add a note, from Claude or ChatGPT.
Project Management Workplace & Productivity
1
https://app.timeuno.io/mcp
Platform7n
dog.p7n
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Workplace & Productivity Communication Project Management
1
https://api.p7n.dog/mcp
platform7n
tech.p7n
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Communication Project Management Workplace & Productivity
2
https://api.p7n.tech/mcp

Related MCP Servers

MCP Redmine
Project Management App Automation
runekaagaard
A
license
A
quality
B
maintenance
Connects Claude Desktop to Redmine for seamless project and issue management, including searching, creating, updating, and tracking tasks using Redmine's API.
Updated a month ago (2026-10-15 18:49 UTC)
5
1,506 PyPI
257
Mozilla Public 2.0
Redmine Enhanced MCP Server
Project Management Developer Tools
olssonsten
A
license
A
quality
D
maintenance
Connect Claude to your Redmine instance to search, browse, create and update issues, manage time entries, and upload/download attachments.
Updated a year ago (2025-09-13 20:27 UTC)
5
1
Mozilla Public 2.0
mcp-server-redmine
Project Management Developer Tools
mirceaion
A
license
Not graded
quality
C
maintenance
Enables AI assistants to create, update, and query Redmine issues and projects directly from conversations.
Updated 3 months ago (2026-08-28 10:31 UTC)
294 npm
1
MIT
Redmine MCP Server
Project Management Developer Tools
junstellar
A
license
A
quality
D
maintenance
Enables natural language interaction with Redmine via Claude Code or other MCP clients, supporting project, issue, and wiki management.
Updated 4 months ago (2026-07-03 22:39 UTC)
11
1
MIT

redmine – Claude-Code-Plugin mit Redmine-MCP-Server

Read-only-Modus

Redmine vorbereiten

Installation als Plugin

Ohne Plugin (nur MCP-Server)

Tools

Entwicklung

Release

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

MCP Redmine

Redmine Enhanced MCP Server

mcp-server-redmine

Redmine MCP Server