Redmineflux MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | Yes | Your Redmine instance URL | |
| REDMINE_API_KEY | Yes | Admin or user API key (My Account → API access key) | |
| REDMINEFLUX_BETA | No | Set to false to disable the beta notice | true |
| REDMINEFLUX_BETA_NOTICE | No | Override with a custom message | |
| REDMINEFLUX_FEEDBACK_PROJECT | No | Redmine project where users should log feedback | ztmcp |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmineflux_core_list_projectsA | List all projects the API user has access to. Args: limit: Max results to return (default 25, max 100). offset: Skip this many results (for pagination). include: Comma-separated extras: trackers, issue_categories, enabled_modules, time_entry_activities. |
| redmineflux_core_get_projectA | Get details of a specific project by ID or identifier. Args: project_id: Numeric ID or string identifier (e.g. "my-project"). include: Comma-separated extras: trackers, issue_categories, enabled_modules, time_entry_activities. |
| redmineflux_core_list_issuesA | List issues with filters. Args: project_id: Filter by project identifier or ID. Empty = all projects. status_id: "open", "closed", "*" (all), or numeric status ID. tracker_id: Filter by tracker ID (0 = all). assigned_to_id: Filter by assignee user ID (0 = all). limit: Max results (default 25, max 100). offset: Pagination offset. sort: Sort field:direction, e.g. "priority:desc", "updated_on:desc". |
| redmineflux_core_get_issueA | Get full details of a specific issue. Args: issue_id: The issue number. include: Comma-separated extras: children, attachments, relations, changesets, journals, watchers, allowed_statuses. |
| redmineflux_core_create_issueA | Create a new issue. Args: project_id: Project identifier or numeric ID. subject: Issue title. tracker_id: Tracker ID (0 = project default). description: Issue body text (supports Textile/Markdown). priority_id: Priority ID (0 = default). assigned_to_id: User ID to assign to (0 = unassigned). status_id: Status ID (0 = default). estimated_hours: Estimated hours (0 = none). parent_issue_id: Parent issue ID for subtasks (0 = none). |
| redmineflux_core_update_issueA | Update an existing issue. Only provided fields are changed. Args: issue_id: The issue number to update. subject: New title (empty = no change). description: New description (empty = no change). status_id: New status ID (0 = no change). priority_id: New priority ID (0 = no change). assigned_to_id: New assignee user ID (0 = no change). done_ratio: New completion percentage 0-100 (-1 = no change). estimated_hours: New estimate (0 = no change). notes: Add a journal note/comment. |
| redmineflux_core_log_timeA | Log time against an issue. Args: issue_id: The issue to log time against. hours: Hours spent (e.g. 1.5). activity_id: Time entry activity ID (use list_time_entry_activities to find IDs). comments: Description of work done. spent_on: Date in YYYY-MM-DD format (empty = today). |
| redmineflux_core_list_time_entriesA | List time entries with filters. Args: project_id: Filter by project (empty = all). issue_id: Filter by issue (0 = all). user_id: Filter by user (0 = all). from_date: Start date YYYY-MM-DD (empty = no filter). to_date: End date YYYY-MM-DD (empty = no filter). limit: Max results (default 25, max 100). offset: Pagination offset. |
| redmineflux_core_list_usersA | List users (requires admin API key). Args: status: "active", "registered", "locked", or "*" (all). limit: Max results (default 25, max 100). offset: Pagination offset. |
| redmineflux_core_get_current_userA | Get details of the user associated with the API key. |
| redmineflux_core_list_statusesA | List all issue statuses. |
| redmineflux_core_list_trackersA | List all trackers (issue types like Bug, Feature, Task). |
| redmineflux_core_list_prioritiesA | List all issue priorities. |
| redmineflux_core_list_time_entry_activitiesA | List available time entry activities (Design, Development, etc.). |
| redmineflux_core_list_versionsA | List versions/milestones for a project. Args: project_id: Project identifier or numeric ID. |
| redmineflux_core_project_statsA | Get issue count statistics grouped by status for one or all projects. Returns total, open, in-progress, resolved, feedback, and closed counts. Much faster than calling list_issues multiple times. Use this when someone asks "how many issues?", "what's the progress?", or "give me numbers." Args: project_id: Project identifier. Empty = stats for ALL projects. |
| redmineflux_core_my_workloadA | Get the current user's assigned issues across all projects, sorted by priority. Use this when someone asks "what should I work on?", "what's on my plate?", or "my tasks". Returns top issues sorted by priority (Immediate first). Args: limit: Maximum issues to return (default 15). Use 5 for quick overview. |
| redmineflux_core_project_summaryA | Get a comprehensive summary of a project in one call. Returns: description, issue counts by status, version milestones, and recent activity. Use this when someone asks "tell me about this project", "what's the status of X?", or "give me an overview." Args: project_id: Project identifier or numeric ID. |
| redmineflux_system_onboardA | Get orientation information for the current user. Use this when someone is new, confused, or asks "where do I start?", "what should I do?", or "help me get started." Returns: who you are, your projects, your assigned tasks, and your teammates. |
| redmineflux_core_critical_issuesA | Get Urgent and Immediate priority open issues. Use this during incidents, fire drills, or when someone asks "what's critical?", "what's on fire?", or "show me the emergencies." Returns only the highest priority open issues. Args: project_id: Filter to one project (empty = all projects). limit: Maximum issues (default 20). |
| redmineflux_system_feedbackA | Submit feedback about your MCP session quality. Call this after using Redmineflux tools to help us improve. Your feedback is logged locally and never shared externally. Args: rating: Quality rating from 1 (poor) to 5 (excellent). comment: Optional comment about what worked or didn't. |
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 21 tools
Each tool targets a distinct resource and action, from project and issue CRUD to time logging and metadata lookups. Even the analytical tools (project_stats, project_summary, my_workload, critical_issues) have clearly defined, non-overlapping purposes that are well-explained in their descriptions.
Most core tools follow a consistent verb_noun pattern (list_projects, get_issue, create_issue), but a few use noun phrases like project_stats and my_workload, and system tools (onboard, feedback) break the pattern. The shared redmineflux_core_/redmineflux_system_ prefix helps maintain a sense of order.
At 21 tools, the server leans heavy, with several metadata lookup tools (list_statuses, list_trackers, list_priorities, list_time_entry_activities, list_versions) that could potentially be combined. Despite the count, each tool has a clear purpose and the set is scoped to Redmine project management.
The tool surface covers the core issue lifecycle (list, get, create, update) and time tracking, plus project views and useful aggregate summaries. Notable gaps include lack of project creation/update/delete and time entry update/delete, but these are not critical for common Redmine workflows.