Redmine MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_API_KEY | Yes | Your Redmine API key for authentication | |
| REDMINE_BASE_URL | Yes | The base URL of the Redmine instance (e.g., https://project.my-redmine.com) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmine_get_issue_contextA | Get Redmine issue by task key (e.g., PROJECT-123): returns JSON with id/key/tracker/subject/description/comments. |
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 a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly scoped to retrieving Redmine issue context by task key.
The tool name follows a clear snake_case verb_noun pattern with a server-specific prefix. With only one tool, there are no mixed conventions or inconsistencies to penalize.
A single tool for a Redmine server is far too few for the implied scope. The server name suggests a broader integration, and one tool provides minimal utility, making the count inappropriate.
The tool surface is severely incomplete for a Redmine integration. It only offers a read operation, lacking create, update, delete, list, search, or comment functionality, which are essential for meaningful issue management.