redmine-mcp-stateless
The redmine-mcp-stateless server enables AI assistants like Claude to fully manage a Redmine instance via its REST API. Credentials are passed per-request via HTTP headers and never stored on the server, enabling secure multi-tenant deployment.
Issue Management
list_issues— Browse issues with filters for project, status, and assigneeget_issue— Retrieve full issue details including all comments (journals) and attachmentscreate_issue— Create issues with subject, description, tracker, status, priority, and assigneeupdate_issue— Modify issue fields and/or add commentsupdate_journal— Edit existing comments on issues (requires Redmine 5.0+)list_issues_with_journals— Retrieve issues with all comments, useful for progress reviews per assigneesearch_issues_full— Full-text search across issue subjects, descriptions, and all comments
Project Management
list_projects— Retrieve all available Redmine projectsget_project— Retrieve detailed information about a specific project
Master / Reference Data
list_statuses,list_trackers,list_priorities— Retrieve available statuses, trackers, and prioritieslist_users— Retrieve users (may require admin privileges), useful for resolving assignee IDs by name
Deployment: Runs as an HTTP server on RHEL (systemd) or Docker, with stdio mode available for local use.
Enables management of Redmine issues, projects, and journals, providing tools for listing, creating, and updating issues, performing full-text searches across comments and descriptions, and retrieving project metadata and user information.
RedmineMCP
An MCP (Model Context Protocol) server that lets Claude Code operate Redmine directly. Runs as an HTTP server on RHEL or Docker. Credentials are never stored on the server — they are passed per-request via HTTP headers from the Claude Code configuration file.
Key Features
Context-First Design Returns journals (comments) alongside issues so the AI can reason about history, generate accurate follow-up proposals, and summarize progress.
Stateless Design API keys are passed per-request from the client and never stored on the server. This brings three practical benefits:
Maximum security — Even if the server is compromised, there are no API keys stored on it to steal.
Multi-tenant out of the box — Deploy one server for the whole team. Each user simply sets their own API key on the Claude side; no per-user configuration is needed on the server.
Zero maintenance for credential changes — When a Redmine password or API key changes, only the client-side Claude configuration needs updating. The server requires no changes.
Powerful Full-Text Search
search_issues_fullsearches across subject, description, and all comments, returning results in an AI-friendly format.
Related MCP server: redmine-mcp
Requirements
Redmine 5.0+ (Redmine 5.0+ required for
update_journal)Python 3.12
RHEL (systemd deployment) or Docker
Redmine Initial Setup
Before using RedmineMCP, enable the Redmine REST API (disabled by default).
Log in as an administrator
Administration → Settings → API tab → check Enable REST web service and save
To get an API key:
Open My account from the top-right menu
Click Show next to API access key
Use this key as
X-Redmine-API-Keyin the Claude Code configuration
Architecture
Client PC (Claude Code / Mac or Windows)
↓ HTTP :8000 + headers (X-Redmine-URL / X-Redmine-API-Key)
Server (RHEL or Docker)
↓ REST API
RedmineInstallation
Option A — RHEL (systemd)
1. Transfer files to the server
ssh root@<server> "mkdir -p /tmp/redmine-mcp-stateless"
scp redmine_mcp_interface.py redmine_mcp_server.py requirements.txt \
redmine-mcp-stateless.service install.sh uninstall.sh \
root@<server>:/tmp/redmine-mcp-stateless/2. Run the installer
cd /tmp/redmine-mcp-stateless
chmod +x install.sh
./install.shinstall.sh performs the following:
Pre-flight checks (root, OS, Python 3.12, required files)
Creates a dedicated
redmine-mcp-statelesssystem userCopies files to
/opt/redmine-mcp-stateless/and creates a Python virtual environmentConfigures logrotate
Registers and starts a systemd service
Configures SELinux (registers port 8000 as
http_port_t)Opens port 8000 in firewalld
Verifies service startup and port listening
3. Verify
systemctl status redmine-mcp-stateless
journalctl -u redmine-mcp-stateless -fTo uninstall
bash uninstall.shOption B — Docker
Runs the MCP server as a container. Requires an existing Redmine instance accessible from the host.
1. Build and start
docker compose up -d --build2. Verify
docker compose ps
docker compose logs -f redmine-mcp-statelessStop
docker compose downClaude Code Configuration
Add the following to ~/.claude.json:
RHEL
{
"mcpServers": {
"redmine-mcp-stateless": {
"type": "sse",
"url": "http://<server-IP>:8000/sse",
"headers": {
"X-Redmine-URL": "https://<your-redmine>",
"X-Redmine-API-Key": "<your-api-key>"
}
}
}
}Docker
{
"mcpServers": {
"redmine-mcp-stateless": {
"type": "sse",
"url": "http://localhost:8000/sse",
"headers": {
"X-Redmine-URL": "https://<your-redmine>",
"X-Redmine-API-Key": "<your-api-key>"
}
}
}
}stdio transport (for registry inspection / local use)
The server normally runs with SSE (HTTP). Setting the environment variable MCP_TRANSPORT=stdio switches it to stdio transport. In this mode, credentials are passed via environment variables instead of HTTP headers:
MCP_TRANSPORT=stdio REDMINE_URL=https://<your-redmine> REDMINE_API_KEY=<your-api-key> \
python redmine_mcp_interface.pyThis mode exists mainly for MCP registry inspection (e.g. Glama). Use SSE for shared team deployment.
Available Tools
Issues
Tool | Description |
| List issues with optional filters (project, status, assignee) |
| Issue details including all comments and attachments |
| Create a new issue |
| Update an issue or add a comment |
| Edit an existing comment (requires Redmine 5.0+) |
| List issues with all comments — useful for per-assignee progress review |
| Full-text search across subject, description, and comments |
Projects
Tool | Description |
| List all projects |
| Project details |
Master Data
Tool | Description |
| Available issue statuses |
| Available trackers |
| Available priorities |
| User list (may require admin privileges) |
Retrievable Data
Category | Fields |
Project | ID, identifier, name, description, status |
Issue | ID, subject, description, status, project, tracker, priority, assignee, created/updated date |
Journal (comment) | comment ID, body, created date, author |
Attachment | file ID, filename, file size, MIME type, description, author, created date |
Status / Tracker / Priority | ID, name |
User | ID, login, first name, last name, full name |
File Structure
File | Description |
| MCP server entry point |
| Redmine REST API client |
| Python dependencies |
| Container image (python:3.12-slim) |
| Docker Compose configuration |
| systemd unit file |
| RHEL installation script |
| Uninstallation script |
| Example Claude Code configuration |
Security Notes
Redmine URL and API key are never stored on the server
Passed per-request via
X-Redmine-URLandX-Redmine-API-KeyheadersStored temporarily in a
ContextVarand discarded after each request completesOn RHEL, the service runs as a dedicated unprivileged user (
redmine-mcp-stateless)
License
MIT
Maintenance
Appeared in Searches
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/daiji-sshr/redmine-mcp-stateless'
If you have feedback or need assistance with the MCP directory API, please join our Discord server