A
securityA
licenseA
qualityA Model Context Protocol server that provides access to MongoDB databases. This server enables LLMs to inspect collection schemas and execute read-only queries.
Last updated -
8
292
264
MIT License
The Redmine MCP Server integrates with Redmine's REST API to provide comprehensive management capabilities:
Issues Management: Search, create, update, and delete issues; filter by project, status, and custom fields; add/remove watchers.
Projects Management: List, create, update, archive, unarchive, and delete projects; configure modules, trackers, and members.
Time Entries Management: Log, update, and delete time entries; filter by user, project, and date range.
Users Management (Admin only): List, create, update, and delete users; manage account settings and notifications.
Integrates with Redmine's REST API to provide ticket and project information to LLMs. Supports managing issues, projects, users, and time entries through the Redmine REST API.
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.
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
Filter by project, status, assignee, etc.
Keyword search
Custom field support
Create/Update Issues
Set tracker, status, priority
Configure custom fields
Add comments
Delete Issues
Projects
Search Projects
Filter by active/archived/closed status
Keyword search
Get Project Details
Include trackers, categories information
Create/Update Projects
Configure modules and trackers
Set member inheritance
Archive/Unarchive Projects
Delete Projects
Time Entries
Search Time Entries
Filter by project, user, date range
Get Time Entry Details
Create/Update Time Entries
Record against project or issue
Specify activity
Custom field support
Delete Time Entries
Usage with Claude
To use this server with Claude, configure it as follows:
{
"mcp-server-redmine": {
"command": "npx",
"args": [
"-y",
"--prefix",
"/path/to/mcp-server-redmine",
"mcp-server-redmine"
],
"env": {
"REDMINE_HOST": "https://your-redmine.example.com",
"REDMINE_API_KEY": "your-api-key-here"
}
}
}
Configuration Options
command: Command to execute the npm packageargs:-y: Auto-respond "yes" to prompts--prefix: Specify installation directoryLast argument specifies the package name
env: Environment variablesREDMINE_HOST: Redmine server URLREDMINE_API_KEY: Your Redmine API key
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 settingsREDMINE_HOST: Redmine server URL (e.g.,https://redmine.example.com)
Testing
Unit Tests
# Run tests
npm test
For data safety, only GET operations are included in tests.
Inspector Testing
Use MCP Inspector to verify functionality:
# Build
npm run build
# Set execute permission (important)
chmod +x dist/index.js
# Launch inspector
npx @modelcontextprotocol/inspector dist/index.js
Permissions
Some features require administrator privileges:
User-Related Operations
list_users: Admin requiredcreate_user: Admin requiredupdate_user: Admin requireddelete_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 SDKzod: Schema validationtypescript: Type system
Directory Structure
.
├── src/
│ ├── tools/ # Tool definitions
│ │ ├── issues.ts
│ │ ├── projects.ts
│ │ ├── time_entries.ts
│ │ └── index.ts
│ ├── formatters/ # Formatters
│ │ ├── issues.ts
│ │ ├── projects.ts
│ │ ├── time_entries.ts
│ │ └── index.ts
│ ├── lib/ # Common libraries
│ │ ├── client.ts # Redmine API client
│ │ ├── config.ts # Configuration management
│ │ └── types.ts # Type definitions
│ ├── handlers.ts # Request handlers
│ └── index.ts # Entry point
├── docs/
│ └── adr/ # Architecture Decision Records
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
└── README.md # Documentation
Building
# Install dependencies
npm install
# Build
npm run build
# Start development server
npm run dev
Architecture Decision Records
Major design decisions are documented in docs/adr. Refer to these documents when adding or modifying features.
License
MIT
Related Projects
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
A Model Context Protocol server for interacting with Redmine using its REST API, enabling the management of tickets, projects, and user data through integration with LLMs.
Related Resources
Related MCP Servers
- AsecurityAlicenseAqualityA Model Context Protocol server that gives LLMs the ability to interact with Ethereum networks, manage wallets, query blockchain data, and execute smart contract operations through a standardized interface.Last updated -45138MIT License
- -securityAlicense-qualityA Model Context Protocol server that enables LLMs to interact with databases (currently MongoDB) through natural language, supporting operations like querying, inserting, deleting documents, and running aggregation pipelines.Last updated -MIT License
- AsecurityFlicenseAqualityA Model Context Protocol server that allows interaction with the RubyGems.org API to fetch metadata about Ruby packages, search gems, and explore dependencies and ownership information.Last updated -6