redmine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | Yes | Your Redmine API access key (obtained from personal settings). | |
| redmineUrl | Yes | The URL of your Redmine instance (e.g., https://your-redmine.example.com). |
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 |
|---|---|
| get_issueB | チケット 1 件を取得する |
| list_issuesA | チケット一覧を取得する（project_id, status_id, assigned_to_id, limit, offset で絞り込み可能） |
| create_issueA | チケットを新規作成する（project_id, subject 必須） |
| update_issueC | チケットを更新する（issue_id 必須。subject, description, status_id, assigned_to_id は任意） |
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 4 tools
Each tool targets a distinct operation on the issue resource: fetching one, listing many, updating, and creating. There is no overlap or ambiguity between the four tools.
All tool names follow a consistent verb_noun snake_case pattern: get_issue, list_issues, update_issue, create_issue. The naming is predictable and easy to infer.
Four tools is well-scoped for a Redmine issue-focused MCP server. Each tool provides a necessary and distinct capability without unnecessary bloat.
The core issue lifecycle is covered: create, read single, read list, and update. The only notable gap is the absence of a delete_issue operation, though this can often be worked around via update_issue.