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://redmine.example.com) | |
| REDMINE_API_KEY | Yes | API key from your account settings | |
| REDMINE_PASSWORD | Yes | Password for Basic Authentication | |
| REDMINE_USERNAME | Yes | Username for Basic 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issuesC | Get a list of Redmine issues/tickets with optional filters. Returns paginated results with issue details including status, priority, assignee, and more. |
| get_issueB | Get detailed information about a specific Redmine issue/ticket by ID. Includes journals (history), attachments, and relations. |
| get_projectsB | Get a list of all Redmine projects. Returns paginated results with project details. |
| get_projectC | Get detailed information about a specific Redmine project by ID. |
| get_project_membersA | Get a list of project members in a specific Redmine project. Returns paginated results with member details, user info, and their roles in the project. |
| get_project_versionsC | Get a list of versions for a specific project. |
| search_issuesB | Search for Redmine issues/tickets by keyword in the subject field. Returns paginated results. |
| get_time_entriesB | Get time entries logged in Redmine. Can be filtered by project, user, and date range. |
| create_issueC | Create a new issue/ticket in Redmine. Returns the created issue with its ID and details. |
| update_issueC | Update an existing Redmine issue/ticket. Only provided fields will be updated. |
| add_commentA | Add a comment/note to an existing Redmine issue. This is a simple way to add comments without updating other issue fields. |
| delete_issueC | Delete a Redmine issue/ticket by ID. |
| log_timeC | Log time stats for an issue or project. |
| get_time_entry_activitiesB | Get list of time entry activities (e.g. Design, Development). |
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 14 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in Redmine, such as issues, projects, time entries, and comments. There is no ambiguity or overlap, with tools like get_issues (list with filters) and search_issues (keyword search) serving complementary but non-conflicting functions.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_issue, get_project, and log_time. This predictability makes it easy for agents to understand and select the correct tool based on the intended action and resource.
With 14 tools, the server is well-scoped for managing Redmine's core features like issues, projects, time tracking, and comments. Each tool earns its place by covering essential operations without redundancy, fitting the typical range of 3-15 tools for a domain-specific server.
The tool set provides complete CRUD/lifecycle coverage for Redmine's key domains, including full issue management (create, get, update, delete, list, search, comment), project access, time tracking (log, list, activities), and version handling. There are no obvious gaps that would hinder agent workflows.