Skip to main content
Glama
enesjakozh
papunoko

Redmine MCP Server for Cline

by papunoko
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Cline 的 Redmine MCP 服务器

这是一个与 Redmine 集成的自定义 MCP（模型上下文协议）服务器，允许您通过 Cline VS Code 扩展与您的 Redmine 项目和问题进行交互。

先决条件

  • **Node.js：**您需要在系统上安装 Node.js（版本 18 或更新版本）。

  • **Redmine 实例：**您需要一个正在运行并启用 REST API 的 Redmine 实例。

  • **Redmine API 密钥：**您需要一个用于 Redmine 用户帐户的 API 密钥。您可以在 Redmine 帐户设置中找到它（通常在“我的帐户”->“API 访问密钥”下）。

  • **Cline：**您需要安装并配置 Cline VS Code 扩展。

Related MCP server: Redmine MCP Server

安装

  1. 克隆存储库：

    git clone https://github.com/ilask/Redmine-MCP.git
cd Redmine-MCP

  2. 安装依赖项：

    npm install

配置

  1. **设置环境变量：**在项目目录的根目录中创建一个.env文件并添加以下内容，用实际的 Redmine 主机名和 API 密钥替换占位符：

    REDMINE_HOST=your-redmine-host.com
REDMINE_API_KEY=your-redmine-api-key

    **重要提示：**请勿将您的.env文件提交到版本控制！该文件包含敏感信息。此仓库中包含的.gitignore文件应该会阻止其被提交。

添加到 Cline

  1. **打开 Cline 设置：**在 VS Code 中，打开 Cline 扩展并转到 MCP 服务器选项卡。

  2. **编辑 MCP 设置：**单击“编辑 MCP 设置”以打开cline_mcp_settings.json文件。

  3. **添加服务器：**将以下条目添加到mcpServers对象，将args路径替换为系统上server.js文件的绝对路径：

    {
  "mcpServers": {
    "redmine-server": {
      "command": "node",
      "args": ["C:\\Users\\yourusername\\path\\to\\Redmine-MCP\\server.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

    **重要提示：**请确保在 Windows 上的路径中使用双反斜杠（ \\ ）。

  4. **保存：**保存cline_mcp_settings.json文件。Cline 会自动检测更改并启动服务器。

可用资源和工具

资源

  • **redmine://projects/{project_id} ：**此资源代表一个 Redmine 项目。请将{project_id}替换为您 Redmine 实例中项目的实际 ID。您可以使用 Cline 中的access_mcp_resource工具读取项目详情。例如：

    <access_mcp_resource>
<server_name>redmine-server</server_name>
<uri>redmine://projects/123</uri>
</access_mcp_resource>

（将123替换为有效的项目 ID）。这将以 JSON 格式返回项目详细信息。

工具

  • **create_issue ：**此工具允许您在 Redmine 中创建新问题。它采用以下参数：

    • project_id （字符串，必需）：应创建问题的项目的 ID。

    • subject （字符串，必需）：问题的主题。

    • description （字符串，必需）：问题的描述。

    您可以使用 Cline 中的use_mcp_tool工具来调用此工具。例如：

    <use_mcp_tool>
<server_name>redmine-server</server_name>
<tool_name>create_issue</tool_name>
<arguments>
{
  "project_id": "456",
  "subject": "My New Issue",
  "description": "This is a test issue created via Cline."
}
</arguments>
</use_mcp_tool>

    （将456替换为有效的项目 ID）。这将在指定项目中创建一个新问题，并以 JSON 格式返回问题详细信息。

故障排除

  • **连接已关闭错误：**如果您看到类似“MCP 错误 -1：连接已关闭”的错误，请确保您的REDMINE_HOST和REDMINE_API_KEY环境变量已正确设置。此外，请确保您的 Redmine 实例可以从您的计算机访问。

  • **检查服务器日志：**如果遇到问题，请在 VS Code 终端中检查服务器的输出，查看是否有任何错误消息。服务器会将错误记录到控制台中。

Available Tools

1 tool
create_issueC

Create a new Redmine issue

ParametersJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
subjectYesIssue subject
descriptionYesIssue description

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation but doesn't mention permissions required, whether it's idempotent, error handling, or what happens on success (e.g., returns an issue ID). For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, error conditions, or behavioral nuances. The agent lacks critical information needed to use this tool effectively in real scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all three parameters (project_id, subject, description) with basic descriptions. The tool description adds no additional parameter context beyond what's in the schema, resulting in the baseline score for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new') and resource ('Redmine issue'), making the purpose immediately understandable. However, it doesn't differentiate from siblings (though none exist) or specify what constitutes a 'Redmine issue' beyond the basic concept, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or contextual constraints. The description merely restates the tool's function without offering any usage context, which is a significant gap for effective agent decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (create_issue), which is consistent with itself. There are no other tools to create inconsistency, so the naming is perfectly predictable.

Tool Count2/5

A single tool is too few for a server named 'Redmine MCP Server for Cline', which implies broader functionality for interacting with Redmine (e.g., an issue tracking system). This minimal set severely limits the server's utility and scope.

Completeness2/5

The tool surface is severely incomplete for Redmine interaction, as it only allows creating issues without any ability to read, update, delete, or search issues, or handle other Redmine entities like projects or users. This creates significant gaps for agent workflows.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Redmine MCP Server

    yonaka15
    A
    license
    Not graded
    quality
    F
    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

  • Redmine MCP Server

    snowild
    A
    license
    B
    quality
    D
    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

  • mcp-redmine

    mejtyas
    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.

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/papunoko/Redmine-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server