Redmine Enhanced MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | Yes | URL of your Redmine instance | |
| REDMINE_API_KEY | Yes | Your Redmine API key | |
| REDMINE_REQUEST_INSTRUCTIONS | No | Path to a file containing additional instructions for the redmine_request tool (optional) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmine_requestA | Make a request to the Redmine API Args: path: API endpoint path (e.g. '/issues.json') method: HTTP method to use (default: 'get') data: Dictionary for request body (for POST/PUT) params: Dictionary for query parameters mcp_filter: Optional MCP response filtering (use redmine_paths_info to discover options) Returns: str: YAML string containing response status code, body and error message |
| redmine_paths_listA | Return a list of available API paths from OpenAPI spec Retrieves all endpoint paths defined in the Redmine OpenAPI specification. Remember that you can use the redmine_paths_info tool to get the full specfication for a path. Returns: str: YAML string containing a list of path templates (e.g. '/issues.json') |
| redmine_paths_infoB | Get full path information including MCP capabilities Returns both native Redmine API specifications AND available MCP server capabilities for response processing. Args: path_templates: List of path templates (e.g. ['/issues.json', '/projects.json']) Returns: str: YAML string containing API specifications and MCP capabilities |
| redmine_uploadB | Upload a file to Redmine and get a token for attachment Args: file_path: Fully qualified path to the file to upload description: Optional description for the file Returns: str: YAML string containing response status code, body and error message The body contains the attachment token |
| redmine_downloadA | Download an attachment from Redmine and save it to a local file Args: attachment_id: The ID of the attachment to download save_path: Fully qualified path where the file should be saved to filename: Optional filename to use for the attachment. If not provided, will be determined from attachment data or URL Returns: str: YAML string containing download status, file path, and any error messages |
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 5 tools
The tools are mostly distinct: upload/download file operations, generic API request, and path discovery. However, redmine_paths_info and redmine_paths_list have overlapping purposes (both deal with paths), though their specific outputs differ.
All tools follow a consistent 'redmine_' prefix with descriptive suffixes (download, paths_info, paths_list, request, upload). The naming pattern is uniform and predictable.
With 5 tools, the server is well-scoped for a Redmine integration. It provides essential file upload/download, a generic API request tool, and discovery tools, avoiding unnecessary bloat.
The generic redmine_request tool covers all Redmine API endpoints, so agents can perform any operation. However, there are no dedicated tools for common tasks like issue CRUD or project management, which may make the server less intuitive.