Skip to main content
Glama
papunoko

Redmine MCP Server for Cline

by papunoko

Redmine MCP Server for Cline

This is a custom MCP (Model Context Protocol) server that integrates with Redmine, allowing you to interact with your Redmine projects and issues through the Cline VS Code extension.

Prerequisites

  • Node.js: You need Node.js (version 18 or newer) installed on your system.

  • Redmine Instance: You need a running Redmine instance with the REST API enabled.

  • Redmine API Key: You need an API key for your Redmine user account. You can find this in your Redmine account settings (usually under "My Account" -> "API access key").

  • Cline: You need the Cline VS Code extension installed and configured.

Related MCP server: Redmine MCP Server

Installation

  1. Clone the repository:

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

    npm install

Configuration

  1. Set environment variables: Create a .env file in the root of the project directory and add the following, replacing the placeholders with your actual Redmine hostname and API key:

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

    Important: Do not commit your .env file to version control! It contains sensitive information. The .gitignore file included in this repository should prevent it from being committed.

Adding to Cline

  1. Open Cline Settings: In VS Code, open the Cline extension and go to the MCP Server tab.

  2. Edit MCP Settings: Click "Edit MCP Settings" to open the cline_mcp_settings.json file.

  3. Add the server: Add the following entry to the mcpServers object, replacing the args path with the absolute path to the server.js file on your system:

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

    Important: Make sure to use double backslashes (\\) in the path on Windows.

  4. Save: Save the cline_mcp_settings.json file. Cline should automatically detect the changes and start the server.

Available Resources and Tools

Resources

  • redmine://projects/{project_id}: This resource represents a Redmine project. Replace {project_id} with the actual ID of a project in your Redmine instance. You can use the access_mcp_resource tool in Cline to read the details of a project. For example:

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

(Replace 123 with a valid project ID). This will return the project details as JSON.

Tools

  • create_issue: This tool allows you to create a new issue in Redmine. It takes the following parameters:

    • project_id (string, required): The ID of the project where the issue should be created.

    • subject (string, required): The subject of the issue.

    • description (string, required): The description of the issue.

    You can use the use_mcp_tool tool in Cline to call this tool. For example:

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

    (Replace 456 with a valid project ID). This will create a new issue in the specified project and return the issue details as JSON.

Troubleshooting

  • Connection closed error: If you see an error like "MCP error -1: Connection closed", make sure that your REDMINE_HOST and REDMINE_API_KEY environment variables are correctly set. Also, ensure that your Redmine instance is accessible from your computer.

  • Check server logs: If you encounter issues, check the server's output in the VS Code terminal for any error messages. The server logs errors to the console.

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.

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

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

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