redmine-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | Yes | The URL of your Redmine instance | |
| REDMINE_API_KEY | Yes | Your Redmine API key | |
| REDMINE_ENABLE_WRITE | No | Set to 'true' to enable write tools | false |
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 |
|---|---|
| list_projectsA | List projects visible to the configured Redmine API user. |
| search_issuesA | Search Redmine issues by common filters. Optional text is applied client-side to subject and description. |
| get_issueA | Get a Redmine issue by id, optionally including journals, attachments, relations, children, or watchers. |
| get_my_issuesB | Get issues assigned to the configured Redmine API user. |
| create_issueB | Create a Redmine issue. Requires REDMINE_ENABLE_WRITE=true. |
| add_issue_noteB | Add a note/comment to a Redmine issue. Requires REDMINE_ENABLE_WRITE=true. |
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 6 tools
Each tool targets a distinct resource and action: projects vs. issues, search vs. by-id, create vs. note. Even search_issues and get_my_issues are clearly differentiated by scope (all issues vs. assigned to the API user).
All tool names follow the consistent verb_noun pattern with lowercase and underscores: list_projects, search_issues, get_issue, get_my_issues, create_issue, add_issue_note. No mixed conventions or vague verbs.
Six tools is a well-scoped count for a Redmine MCP server, covering core read and write operations without superfluous entries. The set feels neither thin nor bloated.
The server covers project listing, issue search/retrieval, issue creation, and note addition, but lacks update and delete operations for issues. This is a notable gap for full lifecycle management, as agents cannot change status, assignee, or priority.