Redmine MCP Server for Cline
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_HOST | Yes | The hostname of your Redmine instance (e.g., your-redmine-host.com) | |
| REDMINE_API_KEY | Yes | Your Redmine API access key, which can be found in your Redmine account settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_issueC | Create a new Redmine issue |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.