Redmine

MCP办公协作

提供方 未标注

办公协作 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

将Claude AI与Redmine项目管理系统集成,以增强项目管理任务。

一句话选型结论

按资料字段整理

Redmine 属于办公协作类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

生产力

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Redmine当前 未标注 未标注 未标注 无 未标注
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类办公协作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.8 KB
来自项目仓库与上游目录的原文,未做删改

Redmine MCP Server - Claude Integration


Welcome to the NASCAR Era of DevOps

  • Company in a Box
  • Designed to breathe.
  • Built to think.
  • Yours to evolve.

An integration between Claude AI (or any MCP client - Like Windsurf) and Redmine using the Model Context Protocol (MCP).

Overview

You can use the existing tooling like Jira MCP servers to accomplish this. We disagree with Jira's structure and design as Redmine allows entire Projects to be shifted or rehomed without issue. If you want an 100% OpenSource solution, keep reading.

The Redmine MCP project provides a seamless connection between Claude AI and Redmine project management system. It allows Claude to access and manipulate Redmine data through a TypeScript implementation of the Model Context Protocol.

This project represents a paradigm shift in how organizations structure collaboration between humans and AI. As described in our NASCAR DevOps philosophy, we've entered an era where "everyone's driving the same car" through standardized protocols like MCP. The difference now lies in the team—how humans and AI coordinate, communicate, and collectively solve problems.

By implementing this system, you're not just deploying a tool but creating a Company in a Box —a central nervous system where:

  • AI agents handle routine operations while humans focus on strategy and creativity
  • Work becomes visible, traceable, and continuously improvable
  • Human value shifts from task execution to mentorship and process improvement
  • Organizational knowledge persists beyond individual contributors
  • Teams build a collective intelligence that compounds over time

The Redmine MCP integration transforms your organization into one where technology handles the routine, while humans focus on creativity, foresight, and meaning.

and NO - it's not 100% complete yet. There is ~ 90% more to go for full functionality and V2 will be where we start working on plugins. So jump in and help out.

Key Components

  • TypeScript MCP Server: A robust implementation that connects Claude to Redmine
  • Redmine Development Environment: A Docker-based Redmine setup for development and testing
  • CI/CD Integration: GitHub and GitLab pipeline configurations with bi-directional sync
  • Comprehensive Documentation: Guides and troubleshooting information

Features

  • Project Management: List and view Redmine projects with detailed information
  • Issue Tracking: Create, update, list and view issues with full parameter support
  • Parent-Child Relationships: Create and manage subtasks with hierarchical structure
  • Issue Relations: Create, view, and manage issue relationships (relates, blocks, etc.)
  • User Information: Access current user details and permissions
  • Robust Error Handling: Detailed error reporting and parameter validation
  • Mock Mode: Development and testing without requiring a Redmine instance

Mock Mode Functionality

The mock mode feature allows for development, testing, and demonstrations without requiring an active Redmine instance. This is particularly valuable for:

  • Offline development work
  • Isolated testing environments
  • Demonstrations and presentations
  • Consistent and reproducible behaviors

The TypeScript implementation includes a complete mock data provider that simulates all Redmine operations with predictable responses.

Quick Start

  1. Clone this repository
  2. Create a .env file with your Redmine API key (see .env.example in redmcp-typescript)
  3. Navigate to redmcp-typescript/ directory
  4. Install dependencies with npm install
  5. Build the project with npm run build
  6. Start the server with npm start
  7. Configure Claude Desktop to use the MCP server

Project Structure```

redmine-mcp/
├── .github/ # GitHub Actions workflows and configuration
├── docs/ # Project documentation
├── prompt.yaml # MCP protocol configuration and tool definitions
├── redmcp-typescript/ # TypeScript implementation of the MCP server
├── redmine-server/ # Development environment with Docker setup
└── README.md # This file


## MCP Server (redmcp-typescript)

The core of this project is the TypeScript implementation of the MCP server. It provides:

- Robust connection to Redmine API
- Type-safe parameter handling
- Comprehensive error management
- Full support for Redmine operations

For detailed information, see the redmcp-typescript README.

## Development Environment

The project includes a Redmine development environment in the `redmine-server/` directory. This provides a consistent PostgreSQL database setup using Docker with:

- Predefined users with API keys
- Sample projects and issues
- Default configuration

To use the development environment:

1. Navigate to the `redmine-server/` directory
2. Run `docker-compose up -d` to start the environment
3. Use the predefined API keys for testing:

| User     | API Key                                  | Role      |
|----------|------------------------------------------|-----------|
| admin    | 7a4ed5c91b405d30fda60909dbc86c2651c38217 | Admin     |
| testuser | 3e9b7b22b84a26e7e95b3d73b6e65f6c3fe6e3f0 | Reporter  |
| developer| f91c59b0d78f2a10d9b7ea3c631d9f2cbba94f8f | Developer |
| manager  | 5c98f85a9f2e34c3b217758e910e196c7a77bf5b | Manager   |

## Available MCP Tools

### Project Operations
- `redmine_projects_list`: List all accessible projects
- `redmine_projects_get`: Get details of a specific project

### Issue Operations
- `redmine_issues_list`: List issues with optional filtering
- `redmine_issues_get`: Get details of a specific issue
- `redmine_issues_create`: Create a new issue
- `redmine_issues_update`: Update an existing issue

### Parent-Child Issue Operations
- `redmine_issue_create_subtask`: Create a subtask under a parent issue
- `redmine_issue_set_parent`: Set or change the parent of an existing issue
- `redmine_issue_remove_parent`: Remove parent relationship (make top-level)
- `redmine_issue_get_children`: Get all child issues of a parent

### Issue Relation Operations
- `redmine_issue_relations_get`: Get all relations for an issue
- `redmine_issue_relation_create`: Create a relation between issues
- `redmine_issue_relation_delete`: Delete an issue relation
- `redmine_issue_comment_add`: Add a comment to an issue

### User Operations
- `redmine_users_current`: Get current user information

For detailed parameter information, see the redmcp-typescript README and the parent-child relationships documentation.

## Integration with Claude Desktop

To use this MCP server with Claude Desktop, add the following configuration to Claude Desktop's configuration file:

- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows**: `%APPDATA%/Claude/claude_desktop_config.json````json
{
  "mcpServers": {
    "redmine": {
      "command": "node",
      "args": ["/absolute/path/to/redmcp-typescript/build/index.js"],
      "env": {
        "REDMINE_URL": "http://your-redmine-instance.com",
        "REDMINE_API_KEY": "your-api-key-here",
        "LOG_LEVEL": "info"
      }
    }
  }
}

Example configurations are available in the redmcp-typescript/docs/ directory.

Troubleshooting

For detailed troubleshooting steps and solutions, see the TROUBLESHOOTING.md file.

Common issues:
- Ensure your Redmine instance is accessible and the API key has appropriate permissions
- When creating issues, ensure the priority_id field is included (required by Redmine)
- Check Claude Desktop logs at ~/Library/Logs/Claude/ (macOS) for error messages

Future Development

See TODO.md for planned enhancements and future development.

CI/CD Integration

The project includes comprehensive CI/CD configurations for both GitHub Actions and GitLab CI:

GitHub Workflows

Located in the .github/workflows/ directory:

  • Main CI/CD Pipeline: Mirrors the GitLab CI pipeline with install, lint, build, and test stages
  • GitLab Sync: Automatically syncs changes from GitHub to GitLab
  • GitHub Sync: Pulls changes from GitLab to GitHub on schedule or manual trigger

To use the GitHub workflows, the following secrets must be configured:
- GITLAB_URL: The URL of your GitLab repository
- GITLAB_TOKEN: GitLab Personal Access Token with repo write permissions
- GITLAB_PROJECT_ID: Your GitLab project ID
- SYNC_GITHUB_TOKEN: GitHub Personal Access Token for creating pull requests

GitLab CI

The .gitlab-ci.yml pipeline includes:
- Dependencies installation
- Code linting
- Project building
- Automated testing
- Special test for subproject creation

For more details, see the .github/README.md file.

Security Considerations

  • API keys are stored separately in .env files
  • Development API keys should never be used in production
  • Always use secure connections (HTTPS) for production deployments
  • CI/CD secrets should have minimal required permissions

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Redmine 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Redmine 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Redmine 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Redmine 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Redmine 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Redmine 能提供哪些能力?

资料显示能力标签包括 生产力。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。