MCP Server for Lychee Redmine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: DEBUG, INFO, WARN, ERROR | INFO |
| LYCHEE_REDMINE_URL | Yes | Your Lychee Redmine instance URL (HTTPS required) | |
| LYCHEE_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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectsB | Get list of accessible projects from Lychee Redmine. Supports pagination. |
| get_projectB | Get project details by ID from Lychee Redmine. Returns project name, description, status, and members. |
| search_issuesC | Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination. |
| create_issueB | Create a new issue in Lychee Redmine. Requires project_id and subject. Optional: description, priority, assignee, due date. |
| update_issueB | Update an existing issue in Lychee Redmine. Partial updates supported - only specify fields to change. |
| get_usersB | Get list of users from Lychee Redmine. Filter by status (active, locked, all). Supports pagination. |
| get_project_membersB | Get members and their roles for a specific project in Lychee Redmine. Includes user and group memberships. Supports pagination. |
| get_scheduleC | Get schedule information for a project in Lychee Redmine. Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis. |
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 8 tools
Each tool has a distinct purpose with clear boundaries: create_issue and update_issue handle issue lifecycle, get_project and get_projects manage project retrieval at different granularities, get_project_members and get_users focus on user/role data, get_schedule covers project scheduling, and search_issues enables issue discovery. No overlap or ambiguity exists between tools.
All tools follow a consistent verb_noun naming pattern (e.g., create_issue, get_project, search_issues) using snake_case throughout. The verbs are predictable (create, get, update, search) and align well with the actions performed, making the set highly readable and uniform.
With 8 tools, this server is well-scoped for managing Lychee Redmine projects and issues. It covers core operations like project and user retrieval, issue creation/updating/searching, and scheduling without being overly sparse or bloated, fitting typical MCP server expectations.
The tool set provides strong coverage for project and issue management, including CRUD for issues (create, update, search) and comprehensive project data retrieval. A minor gap is the lack of project creation/update/deletion tools, but agents can still perform core workflows effectively with the available operations.