Redmine MCP Server
This is a Model Context Protocol (MCP) server implementation for Redmine. It integrates with Redmine's REST API to provide ticket and project information to LLMs.
<a href="https://glama.ai/mcp/servers/55eg9u36cg"><img width="380" height="200" src="https://glama.ai/mcp/servers/55eg9u36cg/badge" alt="Redmine Server MCP server" /></a>
Features
Supports stable resources from Redmine REST API:
- Issues (1.0~)
- Projects (1.0~)
- Users (1.1~)
- Time Entries (1.1~)
Tools
Issues
- Search Issues
- Create/Update Issues
- Delete Issues
Projects
- Search Projects
- Get Project Details
- Create/Update Projects
- Archive/Unarchive Projects
- Delete Projects
Time Entries
- Search Time Entries
- Get Time Entry Details
- Create/Update Time Entries
- Delete Time Entries
Usage with Claude
To use this server with Claude, configure it as follows:
Configuration Options
command: Command to execute the npm package
args:
env: Environment variables
Setup
Getting an API Key
- Enable REST API in Redmine admin settings
- Get API key from user settings page
Environment Variables
Set the following environment variables:
REDMINE_API_KEY: API key obtained from Redmine user settings
REDMINE_HOST: Redmine server URL (e.g.,https://redmine.example.com)
Testing
Unit Tests
For data safety, only GET operations are included in tests.
Inspector Testing
Use MCP Inspector to verify functionality:
Permissions
Some features require administrator privileges:
User-Related Operations
list_users: Admin required
create_user: Admin required
update_user: Admin required
delete_user: Admin required
Available information varies based on user permission levels. For details, see Redmine API Documentation.
Development
Requirements
- Node.js 18 or higher
- npm 9 or higher
Libraries
@modelcontextprotocol/sdk: MCP SDK
zod: Schema validation
typescript: Type system
Directory Structure
Building
Architecture Decision Records
Major design decisions are documented in
docs/adr. Refer to these documents when adding or modifying features.License
MIT
Related Projects
Redmine MCP Server
This is a Model Context Protocol (MCP) server implementation for Redmine. It integrates with Redmine's REST API to provide ticket and project information to LLMs.
<a href="https://glama.ai/mcp/servers/55eg9u36cg"><img width="380" height="200" src="https://glama.ai/mcp/servers/55eg9u36cg/badge" alt="Redmine Server MCP server" /></a>
Features
Supports stable resources from Redmine REST API:
- Issues (1.0~)
- Projects (1.0~)
- Users (1.1~)
- Time Entries (1.1~)
Tools
Issues
- Search Issues
- Create/Update Issues
- Delete Issues
Projects
- Search Projects
- Get Project Details
- Create/Update Projects
- Archive/Unarchive Projects
- Delete Projects
Time Entries
- Search Time Entries
- Get Time Entry Details
- Create/Update Time Entries
- Delete Time Entries
Usage with Claude
To use this server with Claude, configure it as follows:
Configuration Options
command: Command to execute the npm package
args:
env: Environment variables
Setup
Getting an API Key
- Enable REST API in Redmine admin settings
- Get API key from user settings page
Environment Variables
Set the following environment variables:
REDMINE_API_KEY: API key obtained from Redmine user settings
REDMINE_HOST: Redmine server URL (e.g.,https://redmine.example.com)
Testing
Unit Tests
For data safety, only GET operations are included in tests.
Inspector Testing
Use MCP Inspector to verify functionality:
Permissions
Some features require administrator privileges:
User-Related Operations
list_users: Admin required
create_user: Admin required
update_user: Admin required
delete_user: Admin required
Available information varies based on user permission levels. For details, see Redmine API Documentation.
Development
Requirements
- Node.js 18 or higher
- npm 9 or higher
Libraries
@modelcontextprotocol/sdk: MCP SDK
zod: Schema validation
typescript: Type system
Directory Structure
Building
Architecture Decision Records
Major design decisions are documented in
docs/adr. Refer to these documents when adding or modifying features.License
MIT