redmine-mcp
A stateless server for . Drop it in front of any Redmine instance and let Claude (or any MCP-aware LLM client) read and write issues, log time, browse the wiki, and search projects on behalf of the user, with each user's own API key.
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
A stateless server for . Drop it in front of any Redmine instance and let Claude (or any MCP-aware LLM client) read and write issues, log time, browse the wiki, and search projects on behalf of the user, with each user's own API key.
Stateless MCP server for Redmine. Each user brings their own API key; no database, no shared secret.
REDMINE_URL. Each MCP client supplies its own Redmine API key
as a Bearer token. Permissions are whatever Redmine says they are.uv sync
REDMINE_URL=https://redmine.example.com uv run redmine-mcp
The MCP endpoint is now at http://127.0.0.1:8080/mcp.
docker run --rm -p 8080:8080 \
-e REDMINE_URL=https://redmine.example.com \
ghcr.io/kalvadtech/redmine-mcp:latest
The image is multi-stage Alpine, runs as a non-root user, and exposes 8080.
Find your Redmine API key in My account > API access key. The key goes in
the standard Authorization: Bearer header; both clients below talk to the
same MCP endpoint over Streamable HTTP.
.mcp.json in your project root:
{
"mcpServers": {
"redmine": {
"type": "http",
"url": "http://127.0.0.1:8080/mcp",
"headers": {
"Authorization": "Bearer your-40-char-key"
}
}
}
}
opencode.json in your project root (or your opencode config directory):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"redmine": {
"type": "remote",
"url": "http://127.0.0.1:8080/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer {env:REDMINE_API_KEY}"
}
}
}
}
opencode supports {env:VAR} interpolation in headers, so the API key
stays out of the config file: REDMINE_API_KEY=... opencode.
The legacy X-Redmine-API-Key header is still accepted. If both headers
are sent, the Bearer token wins.
CLI flags on redmine-mcp:
--host bind address (default 127.0.0.1)
--port port (default 8080)
--log-level uvicorn log level (default info)
The server fails fast on boot if REDMINE_URL is missing or not http(s).
The Redmine URL is not user-supplied; it is fixed per deployment via
REDMINE_URL. This eliminates SSRF risk: clients cannot point the server at
arbitrary hosts.
The only credential a client sends is its own Redmine API key, normally in
the Authorization: Bearer <key> header (the legacy X-Redmine-API-Key
header is accepted as a fallback). The server forwards it to Redmine as
X-Redmine-API-Key (so it does not land in Redmine access logs as a query
string), uses it to make one request, then discards it. There is no
caching, no shared service account, no impersonation.
Requests without valid credentials get a 401 with a
WWW-Authenticate: Bearer header and a JSON-RPC error body, so strict
MCP clients can surface the auth requirement properly.
59 tools cover every resource family Redmine exposes through its REST API.
List tools return {items, total_count, limit, offset} for easy paging.
list_issues (project, status, assignee, tracker, category, version,
saved query, free-text query, sort, include)get_issue (include: journals, attachments, relations, children, watchers)create_issue (incl. uploads tokens, custom_fields, watcher_user_ids)update_issue (incl. notes, private_notes)add_issue_note (thin wrapper)delete_issuelist_issue_relations, get_relation, create_issue_relation
(relates / blocks / precedes / etc., with delay for precedes/follows),
delete_relationupdate_journal_note - edit an existing note's text or privacy. Use
add_issue_note to add a new note.list_projects, get_projectlist_versions, get_version, create_version, update_version,
delete_versionlist_memberships, get_membership, add_project_member (user or
group), update_membership, remove_membershiplist_users, get_user (accepts the literal string "current")get_my_account, update_my_accountlist_groups, get_group, create_group, update_group,
delete_group, add_user_to_group, remove_user_from_grouplist_roles, get_role (with permissions)list_time_entries (date ranges, user, project, issue)create_time_entry (issue or project, hours, activity, spent_on, comments)update_time_entry, delete_time_entrylist_wiki_pages, get_wiki_page (with version)create_or_update_wiki_page (PUT-upsert)delete_wiki_pageget_attachment, download_attachment (capped at 25 MiB, base64 out)upload_attachment (returns a token to attach via uploads on
create_issue / update_issue)list_files, upload_file (one-shot upload + attach to a project's
Files area, with optional version_id and description)list_news (cross-project or per-project)list_queries (saved queries; pass the id as query_id to list_issues)search (full-text across issues, news, documents, wiki, etc.)list_issue_statuses, list_trackers, list_issue_categories,
list_custom_fieldslist_issue_priorities, list_time_entry_activities,
list_document_categoriesFor a single Redmine instance, run one container per environment:
docker run -d --name redmine-mcp \
--restart unless-stopped \
-p 8080:8080 \
-e REDMINE_URL=https://redmine.example.com \
ghcr.io/kalvadtech/redmine-mcp:latest
Place it behind your usual reverse proxy and TLS termination. The MCP protocol is HTTP-only on the server side; users get TLS via your proxy.
For multiple Redmine instances, run one container per instance with its own
REDMINE_URL and route by hostname / path at the proxy.
uv sync
uv run pytest
uv run ruff check .
uv run mypy src
The test suite is fully offline and uses respx to mock the Redmine HTTP
API. There are no integration tests against a live Redmine; bring-your-own.
Pull requests are welcome. Please:
pytest, ruff, and mypy clean before opening the PR.MIT (c) 2026 Kalvad.
Stateless MCP server for Redmine. Each user brings their own API key; no database, no shared secret.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Redmine ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Stateless MCP server for Redmine. Each user brings their own API key; no database, no shared secret.