redmine-mcp-stdio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | Yes | Base URL of your Redmine instance (http/https) | |
| REDMINE_API_KEY | Yes | Personal API access key | |
| REDMINE_TIMEOUT_MS | No | Per-request timeout in milliseconds | 10000 |
| REDMINE_MAX_RETRIES | No | Retries on 429/5xx with exponential backoff | 2 |
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_issuesC | List Redmine issues with optional filters and pagination |
| get_issueA | Get full details of one Redmine issue by id, including attachments and, by default, comments/history (journals) |
| create_issueC | Create a new Redmine issue |
| update_issueC | Update fields of an existing Redmine issue |
| add_commentB | Add a comment (note) to a Redmine issue |
| list_projectsB | List accessible Redmine projects |
| get_projectA | Get a project's details, versions and members |
| log_timeA | Log a time entry against an issue or a project |
| list_time_entriesB | List time entries, filtered by issue, project, user or date range |
| list_enumerationsA | List trackers, statuses, priorities and time-entry activities with their IDs |
| searchA | Full-text search across Redmine: issues (subjects, descriptions, comments), wiki pages, news and more. Prefer this over list_issues when looking for text. |
| get_current_userA | Get the Redmine account behind the configured API key: numeric id, login and name. Use the id (or the literal 'me') wherever a user id is expected. |
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 12 tools
Each tool has a clear distinct purpose with no overlap. For example, 'list_issues' lists issues with filters, while 'search' provides full-text search across multiple object types, and 'add_comment' is specifically for adding notes. Even similar tools like 'get_issue' and 'list_issues' are distinct by returning one vs. many.
Most tools follow a consistent verb_noun pattern (e.g., create_issue, list_projects), but 'search' deviates as a single verb without a noun. This is a minor inconsistency, but overall the pattern is clear and predictable.
With 12 tools, the server covers core Redmine operations (issues, projects, time tracking, enumerations, user info, search) without being overwhelming or sparse. Each tool serves a necessary function for typical workflows.
The tool set covers most common CRUD operations for issues (create, read, update, list, comment) and time entries, but lacks a delete_issue tool and project creation/update. Search and enumeration tools fill gaps, but a few lifecycle operations are missing.