Redmine MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | No | The URL of your Redmine instance | |
| REDMINE_API_KEY | No | Your Redmine API key | |
| REDMINE_CA_CERT | No | Path to CA certificate file for SSL verification | |
| REDMINE_PASSWORD | No | Your Redmine password (for basic auth if API key not used) | |
| REDMINE_USERNAME | No | Your Redmine username (for basic auth if API key not used) | |
| REDMINE_SSL_VERIFY | No | Enable or disable SSL certificate verification | true |
| REDMINE_MAX_RETRIES | No | Maximum number of retries for failed requests | 3 |
| REDMINE_REQUEST_TIMEOUT | No | Request timeout in milliseconds | 30000 |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmine_list_issuesA | List issues from Redmine with optional filters |
| redmine_get_issueA | Get a specific issue. Comments (journals) are OFF by default to save tokens; the total count is always shown. Enable and page through comments with the journals_* params. |
| redmine_create_issueC | Create a new issue in Redmine |
| redmine_update_issueC | Update an existing issue in Redmine |
| redmine_delete_issueB | Delete an issue from Redmine |
| redmine_list_projectsB | List all available Redmine projects |
| redmine_get_projectB | Get detailed information about a specific project |
| redmine_get_project_versionsA | Get versions/milestones for a specific project |
| redmine_list_usersC | List users in Redmine |
| redmine_get_current_userA | Get information about the currently authenticated user |
| redmine_get_userB | Get detailed information about a specific user |
| redmine_list_time_entriesB | List time entries with optional filters |
| redmine_get_time_entryA | Get detailed information about a specific time entry |
| redmine_create_time_entryC | Create a new time entry |
| redmine_update_time_entryB | Update an existing time entry |
| redmine_delete_time_entryB | Delete a time entry |
| redmine_list_time_entry_activitiesA | List available time entry activities |
| redmine_list_wiki_pagesA | List all wiki pages for a project |
| redmine_get_wiki_pageB | Get content of a specific wiki page |
| redmine_create_or_update_wiki_pageB | Create a new wiki page or update existing one |
| redmine_delete_wiki_pageC | Delete a wiki page |
| redmine_update_journalA | Update an existing journal (comment) on an issue |
| redmine_get_attachmentA | Get detailed information about a specific attachment |
| redmine_update_attachmentB | Update an existing attachment (filename or description) |
| redmine_delete_attachmentA | Delete an attachment from Redmine |
| redmine_list_filesB | List files for a specific project |
| redmine_create_fileA | Add a previously uploaded file to a project |
| redmine_upload_fileA | Upload a file to Redmine and get an upload token. The token can then be used with redmine_create_file or when creating/updating issues with attachments. |
| redmine_custom_requestC | Make a custom API request to Redmine |
| redmine_list_statusesA | List all available issue statuses |
| redmine_list_prioritiesA | List all available issue priorities |
| redmine_list_trackersA | List all available issue trackers |
| redmine_searchC | Search Redmine for issues, wiki pages, and more |
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 33 tools
Each tool targets a distinct resource-action pair (e.g., issues, wiki pages, time entries, users, attachments, projects). Overlap is minimal—the only compound tool, redmine_create_or_update_wiki_page, clearly handles both create and update. The catch-all redmine_custom_request is explicitly generic and optional, so it does not create ambiguity.
All tools follow a consistent redmine_<verb>_<resource> pattern in snake_case. Verbs are uniformly list, get, create, update, delete, with one exception (redmine_create_or_update_wiki_page) that uses a compound verb but remains readable and consistent in style. The single non-verb-noun tool, redmine_custom_request, is a deliberate generic fallback and does not break the established convention.
At 33 tools, the surface is oversized for a typical MCP server, exceeding the 25-tool threshold that indicates 'too many.' While Redmine is a feature-rich system, many tools could be consolidated (e.g., time entry activities and statuses/priorities/trackers could be grouped), and the breadth makes the server harder to navigate.
The tool set covers the major Redmine domains: issues (CRUD plus statuses, priorities, trackers), projects (list/get only), wiki pages (CRUD), time entries (full CRUD plus activities), users (read-only), attachments (get/update/delete), and files (upload/create/list). Notable gaps are the absence of project create/update/delete and user management, but the presence of redmine_custom_request mitigates these limitations for advanced use.