Redmine MCP Server
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. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesC | List issues with optional filters and pagination. |
| get_issueC | Get detailed information about a specific issue. |
| create_issueC | Create a new issue in a project. |
| update_issueD | Update an existing issue. |
| delete_issueC | Delete an issue permanently. |
| add_watcherC | Add a watcher to an issue. |
| remove_watcherC | Remove a watcher from an issue. |
| list_projectsB | List all accessible projects with pagination. |
| get_projectC | Get detailed information about a specific project. |
| create_projectD | Create a new project. |
| update_projectC | Update an existing project. |
| delete_projectC | Delete a project permanently. |
| archive_projectC | Archive a project. |
| unarchive_projectC | Unarchive a project. |
| searchD | Search across Redmine resources. |
| list_time_entriesB | List time entries with optional filters and pagination. |
| get_time_entryC | Get detailed information about a specific time entry. |
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 17 tools
Most tools target a distinct resource+action pair (issues, projects, watchers, time entries), making boundaries clear. The generic 'search' tool mildly overlaps with filtered list_issues/list_projects, but descriptions keep them separable.
Every tool follows a strict verb_noun convention: list_/get_/create_/update_/delete_/add_/remove_/archive_/unarchive_ plus a clear resource noun. Highly predictable with no deviations.
17 tools sits at the heavier end of the range but is justified by covering multiple resources: full issue CRUD, project CRUD plus archive/unarchive, watchers, and time entries. Nothing feels redundant.
Issues and projects have full lifecycle coverage including archive/unarchive and watchers. Time entries only support read (list/get) with no create/update/delete, a notable gap for a time-tracking-centric tool like Redmine.