Skip to main content
Glama
Redmine MCP Server

Redmine MCP Server

Redmine MCP Server

stdio-based Model Context Protocol server that wraps a Redmine instance through its REST API (*.json endpoints). It runs as a separate Node.js process; no changes to the Redmine Rails app are required.

Requirements

  • Node.js 20+

  • A Redmine user with an API access key (My account → Show API access key)

  • Network access from this process to your Redmine REDMINE_BASE_URL

Related MCP server: Redmine MCP Server

Install

No install needed for normal use — coding agents launch it on demand via npx:

npx -y redmine-mcp-connector

See CONNECTING.md for exact setup instructions for Claude Desktop, Claude Code, Cursor, Windsurf, Cline, VS Code, Zed, and any other MCP client, plus a local-build and Docker alternative.

To hack on the server itself, clone this repo instead:

npm install
npm run build

Configuration

Environment variables (see .env.example):

Variable

Required

Description

REDMINE_BASE_URL

yes

Base URL, e.g. https://redmine.example.com (no trailing slash)

REDMINE_API_KEY

yes

X-Redmine-API-Key value

REDMINE_IMPERSONATE_USER

no

Sets X-Redmine-Switch-User (admin-only in Redmine)

REDMINE_READONLY

no

If true / 1, blocks all mutating HTTP methods

REDMINE_ALLOW_RAW_REQUEST

no

If true / 1, registers the redmine_request escape-hatch tool

REDMINE_HTTP_TIMEOUT_MS

no

Default 15000

REDMINE_MAX_PAGES

no

Max pages when using fetch_all on list tools (default 20)

REDMINE_MAX_DOWNLOAD_BYTES

no

Cap for redmine_attachment_download (default 5 MiB)

Run

REDMINE_BASE_URL=https://your-redmine.example.com REDMINE_API_KEY=secret npm start
# or during development:
REDMINE_BASE_URL=... REDMINE_API_KEY=... npm run dev

Connecting to a coding agent

Full per-client instructions (Claude Desktop, Claude Code, Cursor, Windsurf, Cline, VS Code, Zed, and generic MCP clients) live in CONNECTING.md. Quick example (Claude Desktop / Cursor / Windsurf all share this shape):

{
  "mcpServers": {
    "redmine": {
      "command": "npx",
      "args": ["-y", "redmine-mcp-connector"],
      "env": {
        "REDMINE_BASE_URL": "https://redmine.example.com",
        "REDMINE_API_KEY": "your_api_key_here"
      }
    }
  }
}

MCP resources (read-only)

URI

Description

redmine://projects

GET /projects.json (first 100)

redmine://me

GET /users/current.json

redmine://me/issues

GET /issues.json?assigned_to_id=me (limit 100)

redmine://projects/{id}

GET /projects/:id.json

Tools overview

Naming: redmine_<resource>_<action>.

Issues: redmine_issues_list, redmine_issue_get, redmine_issue_create, redmine_issue_update, redmine_issue_add_comment, redmine_issue_delete (requires confirm: true), watchers add/remove, relations list/add/remove.

Projects: redmine_projects_list, redmine_project_get, create/update/archive/unarchive/delete (confirm for delete).

Users: redmine_current_user, redmine_users_list, redmine_user_get, create/update/delete (confirm for delete).

Time entries: list/get/create/update/delete (confirm for delete).

News: list/get/create/update/delete (confirm for delete).

Wiki: list pages, get page, create/update (PUT), delete (confirm).

Versions & categories: versions CRUD (confirm on delete), issue categories CRUD (confirm on delete).

Queries & metadata: redmine_queries_list, redmine_enumerations_list, redmine_trackers_list, redmine_issue_statuses_list, redmine_roles_list, redmine_role_get, redmine_custom_fields_list.

Groups (read-only): redmine_groups_list, redmine_group_get.

Memberships: list/create/update/delete (confirm on delete).

Attachments & search: redmine_search, attachment get/update/delete/upload/download (download returns base64, size-capped).

Repository (limited REST in stock Redmine): redmine_repository_revision_link_issue, redmine_repository_revision_unlink_issue (confirm). Listing repositories/revisions over JSON is not exposed by core Redmine; use redmine_request if you enable it, or plugins.

Escape hatch: redmine_request — only if REDMINE_ALLOW_RAW_REQUEST=true; DELETE requires confirm: true.

Safety

  • Destructive tools require explicit confirm: true where noted.

  • Set REDMINE_READONLY=true for read-only deployments.

  • API keys are never logged by this server.

Docker

Build a local image:

docker build -t redmine-mcp-server:local .

Run it (stdio MCP server):

docker run --rm -i   -e REDMINE_BASE_URL="https://redmine.example.com"   -e REDMINE_API_KEY="your_api_key_here"   redmine-mcp-server:local

Use this image in MCP config:

{
  "mcpServers": {
    "redmine": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "REDMINE_BASE_URL",
        "-e", "REDMINE_API_KEY",
        "docker.io/<docker-user>/redmine-mcp-server:latest"
      ],
      "env": {
        "REDMINE_BASE_URL": "https://redmine.example.com",
        "REDMINE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Publish to Docker Hub Catalog

  1. Login:

docker login
  1. Create and use a buildx builder (one-time):

docker buildx create --name redmine-mcp-builder --use --bootstrap
  1. Build and push multi-arch image:

export IMAGE=docker.io/<docker-user>/redmine-mcp-server
export TAG=1.0.0

docker buildx build   --platform linux/amd64,linux/arm64   -t $IMAGE:$TAG   -t $IMAGE:latest   --push .
  1. In Docker Hub, set your repository description from this README and mark it as public for catalog discovery.

Development

npm run lint
npm test

Contributing

Contributions are welcome.

License

GPL-2.0-or-later (same family as Redmine).

Available Tools

69 tools
redmine_attachment_deleteA

Delete attachment (DELETE /attachments/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_attachment_downloadA

Download attachment binary (GET /attachments/download/:id.json or .bin). Returns base64 and content_type; size capped by REDMINE_MAX_DOWNLOAD_BYTES.

Inputs: id (required).

redmine_attachment_getA

Get attachment metadata (GET /attachments/:id.json).

Inputs: id (required).

redmine_attachment_updateC

Update attachment metadata (PUT /attachments/:id.json).

Inputs: id (required), attachment (required).

redmine_attachment_uploadA

Upload a file to Redmine (POST /uploads.json). Returns upload token; attach via issue/wiki update using uploads array.

Inputs: filename (required), content_base64 (required).

redmine_current_userC

Current user (GET /users/current.json).

Inputs: include.

redmine_custom_fields_listB

List custom fields (GET /custom_fields.json).

Inputs: type.

redmine_enumerations_listA

List enumeration values (GET /enumerations/:type.json) e.g. issue_priorities, time_entry_activities, document_categories.

Inputs: type (required).

redmine_group_getC

Get group (GET /groups/:id.json).

Inputs: id (required).

redmine_groups_listB

List groups (GET /groups.json). May require admin permissions.

Inputs: limit, offset, fetch_all.

redmine_issue_add_commentA

Add a journal note to an issue (same as update with notes only).

Inputs: id (required), notes (required), private_notes.

redmine_issue_add_relationC

Add a relation between issues (POST /issues/:id/relations.json).

Inputs: issue_id (required), relation (required).

redmine_issue_add_watcherB

Add a watcher to an issue (POST /issues/:id/watchers.json).

Inputs: user_id (required), issue_id (required).

redmine_issue_categories_listA

List issue categories for a project (GET /projects/:id/issue_categories.json).

Inputs: project_id (required).

redmine_issue_category_createC

Create issue category (POST /projects/:project_id/issue_categories.json).

Inputs: project_id (required), issue_category (required).

redmine_issue_category_deleteA

Delete issue category (DELETE /issue_categories/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_issue_category_getB

Get issue category (GET /issue_categories/:id.json).

Inputs: id (required).

redmine_issue_category_updateC

Update issue category (PUT /issue_categories/:id.json).

Inputs: id (required), issue_category (required).

redmine_issue_createC

Create an issue (POST /issues.json). Body uses Redmine issue JSON shape.

Inputs: issue (required).

redmine_issue_deleteB

Delete an issue (DELETE /issues/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_issue_getB

Get a single issue (GET /issues/:id.json).

Inputs: id (required), include.

redmine_issue_relations_listA

List relations for an issue (GET /issues/:id/relations.json).

Inputs: issue_id (required).

redmine_issue_remove_relationA

Delete an issue relation (DELETE /relations/:id.json). Requires confirm: true.

Inputs: confirm (required), relation_id (required).

redmine_issue_remove_watcherA

Remove a watcher from an issue (DELETE /issues/:issue_id/watchers/:user_id.json).

Inputs: user_id (required), issue_id (required).

redmine_issues_listB

List issues (GET /issues.json). Supports filters and optional fetch_all to merge pages.

Inputs: sort, limit, offset, include, +11 more.

redmine_issue_statuses_listA

List issue statuses (GET /issue_statuses.json).

Inputs: no named parameters.

redmine_issue_updateB

Update an issue including notes/comments (PUT /issues/:id.json). Pass issue fields and optional notes.

Inputs: id (required), issue (required).

redmine_membership_createC

Create membership (POST /projects/:project_id/memberships.json).

Inputs: membership (required), project_id (required).

redmine_membership_deleteB

Delete membership (DELETE /memberships/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_membership_updateC

Update membership (PUT /memberships/:id.json).

Inputs: id (required), membership (required).

redmine_news_createC

Create news (POST /projects/:project_id/news.json or POST /news.json with project identifier).

Inputs: news (required), project_id (required).

redmine_news_deleteB

Delete news (DELETE /news/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_news_getA

Get news item (GET /news/:id.json).

Inputs: id (required).

redmine_news_listC

List news (GET /news.json).

Inputs: limit, offset, fetch_all, project_id.

redmine_news_updateC

Update news (PUT /news/:id.json).

Inputs: id (required), news (required).

redmine_project_archiveC

Archive project (PUT /projects/:id/archive.json).

Inputs: id (required).

redmine_project_createC

Create project (POST /projects.json).

Inputs: project (required).

redmine_project_deleteA

Delete project (DELETE /projects/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_project_getA

Get project (GET /projects/:id.json).

Inputs: id (required), include.

redmine_project_memberships_listB

List project memberships (GET /projects/:id/memberships.json).

Inputs: project_id (required), limit, offset, fetch_all.

redmine_projects_listB

List projects (GET /projects.json).

Inputs: limit, offset, status, include, +1 more.

redmine_project_unarchiveA

Unarchive project (PUT /projects/:id/unarchive.json).

Inputs: id (required).

redmine_project_updateC

Update project (PUT /projects/:id.json).

Inputs: id (required), project (required).

redmine_queries_listA

List saved queries visible to the user (GET /queries.json).

Inputs: limit, offset, fetch_all.

redmine_role_getA

Get role (GET /roles/:id.json).

Inputs: id (required).

redmine_roles_listA

List roles (GET /roles.json).

Inputs: no named parameters.

redmine_time_entries_listC

List time entries (GET /time_entries.json).

Inputs: to, from, limit, offset, +5 more.

redmine_time_entry_createC

Create time entry (POST /time_entries.json).

Inputs: time_entry (required).

redmine_time_entry_deleteB

Delete time entry (DELETE /time_entries/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_time_entry_getA

Get time entry (GET /time_entries/:id.json).

Inputs: id (required).

redmine_time_entry_updateC

Update time entry (PUT /time_entries/:id.json).

Inputs: id (required), time_entry (required).

redmine_trackers_listA

List trackers (GET /trackers.json).

Inputs: no named parameters.

redmine_user_createD

Create user (POST /users.json).

Inputs: user (required).

redmine_user_deleteA

Delete user (DELETE /users/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_user_getC

Get user (GET /users/:id.json).

Inputs: id (required), include.

redmine_users_listC

List users (GET /users.json). Admin may be required.

Inputs: name, limit, offset, status, +2 more.

redmine_user_updateC

Update user (PUT /users/:id.json).

Inputs: id (required), user (required).

redmine_version_createB

Create version (POST /projects/:project_id/versions.json).

Inputs: version (required), project_id (required).

redmine_version_deleteA

Delete version (DELETE /versions/:id.json). Requires confirm: true.

Inputs: id (required), confirm (required).

redmine_version_getB

Get version (GET /versions/:id.json).

Inputs: id (required).

redmine_versions_listB

List versions / roadmap for a project (GET /projects/:id/versions.json).

Inputs: project_id (required).

redmine_version_updateC

Update version (PUT /versions/:id.json).

Inputs: id (required), version (required).

redmine_wiki_page_create_or_updateA

Create or update wiki page (PUT /projects/:project/wiki/:title.json). Redmine uses update for new pages.

Inputs: title (required), wiki_page (required), project_id (required).

redmine_wiki_page_deleteA

Delete wiki page (DELETE /projects/:project/wiki/:title.json). Requires confirm: true.

Inputs: title (required), confirm (required), project_id (required).

redmine_wiki_page_getC

Get wiki page (GET /projects/:project/wiki/:title.json).

Inputs: title (required), project_id (required), include.

redmine_wiki_pages_listA

List wiki pages for a project (GET /projects/:id/wiki/index.json).

Inputs: project_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 69 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action pair, so agents can usually tell them apart. The main overlap is redmine_issue_update and redmine_issue_add_comment, which are described as using the same endpoint, creating possible misselection.

    Naming Consistency4/5

    The redmine_ prefix and resource_action ordering are consistent across the set. Minor inconsistencies exist, such as pluralized list names (redmine_issues_list) versus singular item actions (redmine_issue_get), and project_memberships_list versus membership_create/update/delete.

    Tool Count1/5

    With 69 tools, this is far beyond the typical well-scoped MCP surface and falls into the extreme 50+ category. While Redmine has a large API, exposing nearly every endpoint as a separate tool makes the set unwieldy for an agent.

    Completeness4/5

    The tool set covers CRUD for the major Redmine resources and adds useful metadata/listing tools for trackers, statuses, roles, custom fields, and enumerations. Minor gaps exist, such as no dedicated watcher listing endpoint and no membership get, but agents can likely work around these.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      78
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables Claude Code to directly interact with Redmine project management systems, supporting issue management, project operations, and search features.
      22
      9
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to interact with Redmine projects, issues, time tracking, and members through natural language via the Model Context Protocol.
      -