mcp-redmine
Provides tools for managing Redmine projects, issues, time entries, versions, members, attachments, and issue relations using the Redmine API.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-redmine
Connect coding agents to Redmine through the Model Context Protocol. Use a normal API key; the agent can search issues, update tickets, log time, and manage project basics without opening the web UI. Source: github.com/mejtyas/mcp-redmine.
Docker image: mejtyas/mcp-redmine:latest (run with docker run -i for stdio).
Tools (17)
Read | Create / update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| — |
Together these cover most day-to-day workflows: projects, issues (look up, search, create, edit), versions, members, time logging, attachments, and relations. For typical agent tasks—triage, updates, notes, light reporting—that is roughly 95% of what you need without custom glue code.
Related MCP server: Redmine MCP Server
Before you start
In Redmine, open My account and create an API access key if you do not have one.
Set credentials using the canonical names below (shell, Cursor
envblock, or inline Docker-eVAR=valueinargs—see Cursor). The server also acceptsredmine_urlandredmine_api_tokenas aliases.
Variable | Value |
| Base URL, e.g. |
| Your API key string |
Everything the agent does runs as the Redmine user tied to that key.
Run the server (Docker)
docker run --rm -i \
-e REDMINE_URL=https://your-redmine.example.com \
-e REDMINE_API_KEY=your_key \
mejtyas/mcp-redmine:latestCompany HTTPS deployment (Cursor url)
For a shared host (for example https://mcp-redmine.example.com/mcp), the server can keep one company Redmine URL and require a shared gate token plus each developer’s Redmine API key on every HTTP request.
Redmine URL — either set
REDMINE_URLin the container environment, or setCOMPANY_REDMINE_URLinmcp_redmine/config.py(used whenREDMINE_URLis unset).Server environment (deployment / GitLab CI variables, not in
mcp.json):MCP_TRANSPORT—streamable-http(recommended) orsseMCP_AUTH_TOKEN— long random secret shared inside the company (required for HTTP transport)Optional:
MCP_HOST,MCP_PORT(default0.0.0.0/8000),MCP_PATH(default/mcp)
Cursor — remote entry with two headers: company gate + personal Redmine key:
{
"mcpServers": {
"mcp-redmine": {
"url": "https://mcp-redmine.example.com/mcp",
"headers": {
"Authorization": "Bearer ${env:MCP_AUTH_TOKEN}",
"X-Redmine-API-Key": "${env:REDMINE_API_KEY}"
}
}
}
}Use the same header names if you terminate TLS in front of the app; the MCP process must still receive Authorization: Bearer … and X-Redmine-API-Key: …. Do not commit real tokens.
Cursor
Open Settings → MCP, or edit ~/.cursor/mcp.json. Use a top-level mcpServers object.
Option A — env block (recommended)
Cursor sets env on the MCP server process. Use bare -e VAR in Docker args so those variables are forwarded into the container (no secrets duplicated in the run argument list).
{
"mcpServers": {
"mcp-redmine": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"REDMINE_URL",
"-e",
"REDMINE_API_KEY",
"mejtyas/mcp-redmine:latest"
],
"env": {
"REDMINE_URL": "https://your-redmine.example.com",
"REDMINE_API_KEY": "your_key"
}
}
}
}Option B — inline -e in args
If you prefer everything in args, this shape also works:
{
"mcpServers": {
"mcp-redmine": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"REDMINE_URL=https://your-redmine.example.com/",
"-e",
"REDMINE_API_KEY=your_key",
"mejtyas/mcp-redmine:latest"
]
}
}
}Replace placeholders with your values. Do not commit real URLs or keys.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
Project memory, documentation and controlled secret access for AI coding agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for interacting with Redmine using its REST API, enabling the management of tickets, projects, and user data through integration with LLMs.78MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables Claude Code to directly interact with Redmine project management systems, supporting issue management, project operations, and search features.229MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to interact with Redmine project management systems for issue tracking, time logging, and project management through natural language.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Redmine issues, projects, time tracking, wiki, and files via the MCP protocol.3325 npm6Apache 2.0