mcp -redmine

This MCP server provides a Redmine integration that exposes REST API-backed resources for issues, projects, users, and time entries to LLMs. It enables tools to search, retrieve details, create or update records, and manage related entities within Redmine, all through the MCP tooling framework. After starting the server with the configured environment variables, you can query and manipulate Redmine data via the supported tools (e.g., list_issues, get_issue, list_projects, show_project, list_time_entries, show_time_entry, and corresponding create/update/delete actions) through the MCP Inspector or programmatic calls, allowing LLMs to reason about Redmine data in a structured manner. To use with Claude, configure the server in your Claude deployment to point to this MCP server, and supply the required environment variables for Redmine authentication.

Prerequisites:

• Node.js and npm installed on your system
• Access to a Redmine instance with REST API enabled and an API key

Step-by-step installation:

1. Ensure Node.js and npm are installed
   • Check: node -v and npm -v
2. Install or initialize the MCP Redmine server package (via npx in this setup):
   • You don’t need a global install if you follow the MCP approach; ensure you have network access to fetch the package
3. Prepare environment variables:
   • Create a shell script or set them in your hosting environment: export REDMINE_HOST=https://your-redmine.example.com export REDMINE_API_KEY=your-api-key-here
4. Start the MCP server using the provided configuration:
   • The server is invoked via npx with the appropriate prefix and package name, as shown in the mcp_config
   • Example (adjust /path/to/mcp-server-redmine and environment as needed): npx -y --prefix /path/to/mcp-server-redmine mcp-server-redmine
5. Verify the server starts correctly and is reachable by your MCP client (Inspector or Claude integration).

Optional steps for testing locally:

• Build and prepare the dist artifacts if the project uses a build step (per repository instructions)
• Ensure the dist/index.js (or equivalent) is executable if required by your setup

Notes and tips:

• Environment variables REDMINE_HOST and REDMINE_API_KEY are required for authentication with Redmine REST API
• Ensure your Redmine instance allows API access from the MCP server host (CORS or reverse proxy considerations may apply)
• If you encounter permission errors in Redmine, verify that the API key has appropriate privileges for the requested operations (admin rights may be required for certain actions)
• When using npx with --prefix, the package will be installed/used in the specified directory; ensure the path exists and is writable
• For CLI testing, you can leverage the MCP Inspector to validate available tools and their arguments before integrating with an LLM
• If the Redmine API URL uses HTTPS with a self-signed certificate, you may need to configure TLS options or disable strict host checking in a development environment (not recommended for production)
• Regularly rotate the Redmine API key and update the environment variables accordingly in your deployment