Redmine 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 (e.g., https://your-redmine.com) | |
| REDMINE_API_KEY | Yes | Your Redmine API key for authentication |
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 has a distinct purpose, clearly differentiated by the noun (e.g., issues vs. projects vs. time entries) and verb (list, get, create, update, delete). No two tools operate on the same resource-action combination, so an agent can reliably select the correct one.
All tools follow the strict pattern 'redmine_verb_noun' (e.g., redmine_list_issues, redmine_get_wiki_page, redmine_create_time_entry), using imperative present-tense verbs and consistent snake_case. No deviations or mixed conventions.
With 33 tools, the server covers a broad domain (issues, projects, wiki, time tracking, attachments, users, metadata, search). While slightly above the typical 15-25 range, each tool addresses a distinct feature of Redmine, and the count is justified by the platform's complexity.
The tool set provides CRUD operations for all major Redmine entities (issues, wiki pages, time entries, attachments, files) plus query capabilities for metadata and search. There are no obvious gaps for standard workflows; even edge cases like uploading files and custom requests are covered.