Redmine MCP Server

Most developer tooling work still happens through a UI a human drives. Redmine MCP server moves it into the conversation instead. Redmine MCP 서버 — 일감 조회/상태변경/댓글/내보내기.

The short version

1. Releases에서 최신 redmine-vscode-x.y.z.vsix 다운로드 2. VS Code → Extensions 패널 → ⋯ 메뉴 → Install from VSIX (또는 code --install-extension 파일.vsix) 3. 설정(settings): - redmine.url — Redmine 서버 URL (필수) - redmine.projectIdentifier — (선택) '내 일감' 범위 한정 - redmine.downloadPath — (선택) 일감 다운로드 기본 경로. 절대/~/상대(워크스페이스 기준) 4. 명령 팔레트(Ctrl+Shift+P) → Redmine: Set API Key → 본인 API key 입력 - key 발급: Redmine → 내 계정 → 우측 "API 접근키" - key는 SecretStorage에 저장됨 (파일에 안 남음)

The tools it exposes

The server publishes 5 tools. What each one is for:

• redmine.url — Redmine 서버 URL (필수)
• redmine.projectIdentifier — (선택) '내 일감' 범위 한정
• redmine.downloadPath — (선택) 일감 다운로드 기본 경로. 절대/~/상대(워크스페이스 기준)
• code — -install-extension <파일>.vsix 로 설치
• MCP — 환경변수로만 주입. VS Code 확장: SecretStorage

Getting it running

The server ships on npm as @bizhost/redmine-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: REDMINE_URL, REDMINE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Redmine's toolset — redmine.url, redmine.projectIdentifier, redmine.downloadPath and 2 more — is a fair guide to whether it matches your workflow. It is maintained by juggeryo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.