mcp-redmine
Enables AI coding agents to interact with Redmine projects, issues, time tracking, and members through natural language via the Model Context Protocol.
README
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 |
|---|---|
redmine_get_users |
redmine_create_issue |
redmine_get_current_user |
redmine_edit_issue |
redmine_get_projects |
redmine_create_fixed_version |
redmine_get_issue |
redmine_add_member_to_project |
redmine_search_issues |
redmine_remove_member_from_project |
redmine_get_fixed_versions |
redmine_log_time |
redmine_get_project_members |
redmine_upload_attachment |
redmine_get_time_entries |
redmine_add_issue_relation |
redmine_execute_custom_request |
— |
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.
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 |
|---|---|
REDMINE_URL |
Base URL, e.g. https://redmine.example.com (no trailing slash required) |
REDMINE_API_KEY |
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:latest
Company 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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.