mcp-redmine-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_API_KEY | Yes | Your Redmine API key | |
| REDMINE_BASE_URL | No | Base URL of the Redmine server (default: https://3cad.tech) | https://3cad.tech |
| REDMINE_PROJECT_ID | No | Default project ID (default: 8) | 8 |
| REDMINE_PROJECT_IDENTIFIER | No | Default project identifier (default: cad-tech) | cad-tech |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmine_get_issueA | Get detailed information about a Redmine issue including description, status, priority, assigned user, and comments |
| redmine_create_issueA | Create a new Redmine issue with specified title and description. Can optionally attach files by providing file paths. |
| redmine_add_commentA | Add a comment to an existing Redmine issue and optionally change its status |
| redmine_get_issues_by_statusB | Get all issues with a specific status (e.g., "New", "In Progress", "Resolved"). Can filter by project or get from all projects |
| redmine_get_issue_treeA | Get full issue tree including related issues and child/subtask issues |
| redmine_create_relationB | Create a relation between two issues (relates, blocks, duplicates, etc.) |
| redmine_start_fixA | Start fix workflow: creates git branch, updates issue status to "In Progress", and provides task analysis |
| redmine_complete_fixA | Complete fix workflow: updates issue status to "Resolved" and adds completion comment with commit details |
| redmine_get_statusesA | Get all available issue statuses in the Redmine project |
| redmine_get_projectsA | Get list of all available Redmine projects that the API key has access to |
| redmine_get_projectA | Get detailed information about a specific Redmine project including trackers and enabled modules |
| redmine_get_project_issuesA | Get issues from a specific project with optional filters |
| redmine_wiki_get_pageA | Get a wiki page content from a Redmine project by page title |
| redmine_wiki_get_indexA | Get a list of all wiki pages in a Redmine project |
| redmine_wiki_put_pageA | Create a new wiki page or update an existing one in a Redmine project. Uses PUT — creates if not exists, updates if exists. |
| redmine_wiki_delete_pageA | Delete a wiki page from a Redmine project |
| redmine_upload_fileA | Upload a file to Redmine and get an upload token. This token can be used later to attach the file to an issue. |
| redmine_add_attachmentsA | Add one or more file attachments to an existing Redmine issue. Files are uploaded and automatically attached. |
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 18 tools
Each tool generally maps to one resource/action, with only a few overlapping pairs like get_issue_tree vs get_issue and get_project_issues vs get_issues_by_status. The descriptions sufficiently clarify these boundaries, so an agent can usually select the right tool.
All tools use a consistent redmine_ prefix and snake_case with verb-first names such as get, create, add, start, complete, and upload. Even the wiki PUT operation is named predictably, and there is no mixing of naming conventions.
18 tools is at the upper end of a typical MCP server, but each tool serves a distinct purpose across issues, wiki, projects, attachments, and workflow. It feels slightly heavy but not bloated for the breadth of Redmine features covered.
Issue coverage lacks a generic update_issue or delete_issue; status changes are only available through add_comment or the start_fix/complete_fix workflow. Wiki and project access are well covered, but the core issue lifecycle is incomplete.