Skip to main content
Glama
MCP Server for Lychee Redmine

MCP Server for Lychee Redmine

by ssoma-dev

MCP Server for Lychee Redmine

Model Context Protocol (MCP) server for integrating Lychee Redmine project management with AI assistants like Claude.

Requirements

  • Node.js 22.18.0 or higher

  • Lychee Redmine instance with API access

Related MCP server: Redmine MCP Server

Installation

npm install

Configuration

Set the following environment variables:

  • LYCHEE_REDMINE_URL: Your Lychee Redmine instance URL (HTTPS required)

  • LYCHEE_REDMINE_API_KEY: Your Redmine API key

  • LOG_LEVEL: (Optional) Log level: DEBUG, INFO, WARN, ERROR (default: INFO)

Setup for Claude Code

CLI で追加する場合

claude mcp add lychee-redmine \
  -e LYCHEE_REDMINE_URL=https://your-redmine-instance.example.com \
  -e LYCHEE_REDMINE_API_KEY=your-api-key \
  -- npx -y github:ssoma-dev/mcp-server-lychee-redmine

設定ファイルを直接編集する場合

グローバル設定 (~/.claude/settings.json) またはプロジェクト設定 (.claude/settings.json) に以下を追加してください:

{
  "mcpServers": {
    "lychee-redmine": {
      "command": "npx",
      "args": ["-y", "github:ssoma-dev/mcp-server-lychee-redmine"],
      "env": {
        "LYCHEE_REDMINE_URL": "https://your-redmine-instance.example.com",
        "LYCHEE_REDMINE_API_KEY": "your-api-key"
      }
    }
  }
}

動作確認

claude mcp list

一覧に lychee-redmine が表示されれば設定完了です。Claude Code からプロジェクト・チケット・スケジュール・ユーザー管理のツールが利用可能になります。

Development

# Run in development mode
npm run dev

# Build
npm run build

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Type checking
npm run typecheck

# Lint
npm run lint

# Format code
npm run format

Architecture

This MCP server follows Domain-Driven Design principles with clear separation:

  • /src/server/ - MCP Server Core

  • /src/redmine/ - Redmine Integration

  • /src/config/ - Configuration Management

  • /src/utils/ - Utilities (Logger, Error Handler, Retry Handler)

License

MIT

Available Tools

8 tools
create_issueB

Create a new issue in Lychee Redmine. Requires project_id and subject. Optional: description, priority, assignee, due date.

Inputs: project_id (required), subject (required), description, priority_id, +2 more.

get_projectB

Get project details by ID from Lychee Redmine. Returns project name, description, status, and members.

Inputs: id (required).

get_project_membersB

Get members and their roles for a specific project in Lychee Redmine. Includes user and group memberships. Supports pagination.

Inputs: project_id (required), limit, offset.

get_projectsB

Get list of accessible projects from Lychee Redmine. Supports pagination.

Inputs: limit, offset.

get_scheduleC

Get schedule information for a project in Lychee Redmine. Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis.

Inputs: project_id (required), include_critical_path.

get_usersB

Get list of users from Lychee Redmine. Filter by status (active, locked, all). Supports pagination.

Inputs: status, limit, offset.

search_issuesC

Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination.

Inputs: project_id, status_id, assigned_to_id, query, +2 more.

update_issueB

Update an existing issue in Lychee Redmine. Partial updates supported - only specify fields to change.

Inputs: id (required), subject, description, status_id, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers