Redmine MCP Stateless

What the daiji-sshr/redmine-mcp-stateless MCP server does

The daiji-sshr/redmine-mcp-stateless MCP server connects an MCP client to Redmine’s REST API. It supports issue workflows, project lookup, master-data queries, and full-text issue search. Issue responses can include journals and attachments, giving an agent access to both the current record and its discussion history.

The available operations cover listing issues with project, status, or assignee filters; retrieving an issue; creating or updating issues; adding comments; and editing existing comments. Project details, issue statuses, trackers, priorities, and users can also be queried. User listing may require Redmine administrator privileges.

How it works

The server normally runs as an HTTP service using SSE. An MCP client sends the Redmine URL and API key in the X-Redmine-URL and X-Redmine-API-Key headers for each request. These values are held temporarily for request processing and are discarded afterward rather than being persisted by the server.

For local inspection or use, setting MCP_TRANSPORT=stdio switches the process to stdio. In that mode, REDMINE_URL and REDMINE_API_KEY provide the connection details through the environment. The server then calls Redmine’s REST API using those credentials.

Setup and configuration

Redmine must have its REST API enabled under Administration, Settings, and API. An administrator can enable the REST web service, after which a user can retrieve an API access key from My account. Redmine 5.0 or newer is required for the update_journal operation; the other documented capabilities are not stated to require that version.

The daiji-sshr/redmine-mcp-stateless MCP server requires Python 3.12 and can be deployed on RHEL with systemd or in Docker. The RHEL installer creates a dedicated service user, virtual environment, systemd service, log rotation, firewall and SELinux configuration, and listens on port 8000. Docker deployment uses the supplied Compose configuration and requires a Redmine instance reachable from the host.

Claude Code connects to the SSE endpoint at /sse. The client configuration supplies the endpoint and the two Redmine headers. The documented examples use a server address for RHEL or localhost for Docker.

Tools and capabilities

• Filter and list issues by project, status, or assignee.
• Retrieve issue details, journals, and attachment metadata.
• Create issues, change issue data, and add comments.
• Edit existing journals when Redmine 5.0 or newer is available.
• Search issue subjects, descriptions, and comments using full-text search.
• Review issues with their complete comment history for per-assignee progress checks.
• List and inspect projects, statuses, trackers, priorities, and users.

Limitations and notes

The daiji-sshr/redmine-mcp-stateless MCP server does not store Redmine credentials, but the client still needs to provide a valid API key and URL. Access to data and mutations is governed by the permissions of the Redmine account associated with that key. User enumeration may need administrator access.

The documented client integration is Claude Code over SSE. The README does not establish compatibility with other named MCP clients. The server is intended for HTTP deployment in shared team scenarios; stdio is described mainly for registry inspection or local use. Redmine 5.0+ is specifically necessary for journal editing, and the deployment environment must provide either RHEL with systemd or Docker.