# andrelaptenok/redmine-mcp-stdio [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/andrelaptenok/redmine-mcp-stdio  
**GitHub Stars:** 0  
**npm Downloads (last month):** 196  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/andrelaptenok-redmine-mcp-stdio

## Description
Search, read, create and update Redmine issues, projects and time entries from any MCP client. 12 tools with MCP safety annotations: full-text search, issue journals with attachments, comments and time tracking. npx -y redmine-mcp-stdio

## Tools
Capabilities this server exposes over MCP:

- **list_issues** — List/filter issues, paginated
- **get_issue** — Full details of one issue + comments/history + attachments
- **list_projects** — Accessible projects
- **get_project** — Project details, versions and members
- **create_issue** — Create an issue
- **update_issue** — Update issue fields
- **add_comment** — Add a note to an issue
- **log_time** — Log a time entry on an issue/project
- **list_time_entries** — List time entries, filtered
- **list_enumerations** — IDs of trackers/statuses/priorities/activities
- **search** — Full-text search (issues, wiki, news, …)
- **get_current_user** — Account behind the API key (id, login, name)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "redmine-mcp-stdio": {
    "command": "npx",
    "args": ["-y","redmine-mcp-stdio"],
    "env": {
      "REDMINE_URL": "",
      "REDMINE_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `REDMINE_URL`, `REDMINE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What andrelaptenok/redmine-mcp-stdio MCP server does

andrelaptenok/redmine-mcp-stdio MCP server exposes Redmine operations through the Model Context Protocol. It supports both read and write workflows for issues, projects, and time entries, using the permissions of the Redmine account associated with the API key.

The issue tools cover paginated listing and filtering, complete issue retrieval, creation, field updates, and comments. Issue details can include comments, history, and attachments. Project tools list accessible projects and retrieve project information, versions, and members. Separate tools handle time-entry creation and filtered time-entry listing.

A full-text search tool can search issues, wiki content, news, and other Redmine content. The server also provides the current API user and an enumeration lookup for tracker, status, priority, and activity IDs.

## How it works

The server runs locally and communicates with the MCP client over stdio. A client starts it on demand with `npx -y redmine-mcp-stdio`; npx downloads the package on first use and caches it afterward. Requests are sent to the configured Redmine REST API using the supplied credentials.

Each of the 12 tools includes MCP annotations such as read-only and destructive-operation hints. Clients can use those annotations when deciding whether read-only calls may be approved automatically. Write operations still depend on the Redmine user's permissions to create or edit the relevant records.

## Setup and configuration

andrelaptenok/redmine-mcp-stdio MCP server requires `REDMINE_URL` and `REDMINE_API_KEY` in the MCP client's environment. The URL should identify the Redmine instance, and the API key must belong to a user allowed to access the required projects and records. For write operations, that user also needs the relevant create or edit permissions.

Add a stdio server entry with `npx` as the command and `-y redmine-mcp-stdio` as its arguments. The README provides configuration examples for Cursor, VS Code, Claude Code, Claude Desktop, Codex CLI, Windsurf, Cline, Zed, and JetBrains AI Assistant. A local check can also launch the same command directly with both environment variables set.

The documented runtime requirement is Node.js 20 or newer. Keep the API key out of source control; the project recommends using an environment file for local development rather than committing credentials.

## Tools and capabilities

The available tools are:

- `list_issues` for filtered, paginated issue lists.
- `get_issue` for issue details, journals, and attachments.
- `create_issue` and `update_issue` for issue changes.
- `add_comment` for adding issue notes.
- `list_projects` and `get_project` for project data.
- `log_time` and `list_time_entries` for time tracking.
- `search` for Redmine full-text search.
- `list_enumerations` for IDs used by issue and time-entry fields.
- `get_current_user` for the account represented by the API key.

The andrelaptenok/redmine-mcp-stdio MCP server accepts filters such as project, status, assignee, date range, issue, user, and content type, depending on the tool. Issue updates can change fields including subject, status, priority, assignee, completion percentage, and notes.

_Full upstream README: https://allmcps.com/mcp/andrelaptenok-redmine-mcp-stdio/readme_