redmine_mcp_server

This MCP server exposes a Model Context Protocol interface for Redmine data using Streamable HTTP. It implements four tools that allow clients to interact with Redmine projects and their content through JSON-RPC style requests: list_issues, list_wiki_pages, read_issue, and read_wiki_page. You can fetch all issues within a project with list_issues, enumerate all wiki pages with list_wiki_pages, read a single issue with read_issue by its id, and read a wiki page with read_wiki_page by its page identifier. Since the server uses Streamable HTTP, responses are delivered as a stream of JSON-RPC like messages, enabling efficient data transfer for large result sets. Note that this is an experimental concept and does not implement authentication or Server-Sent Events support.

Prerequisites:

• A Redmine installation with plugin support
• Git installed on the host
• Access to the Redmine plugin directory

Install steps:

1. Clone the MCP plugin into the Redmine plugins directory:

   git clone https://github.com/9506hqwy/redmine_mcp_server.git

2. Restart Redmine or reload plugins to register the MCP server plugin.

3. Ensure the server has network access to your Redmine instance (if running as a separate service).

4. Start the Redmine server as you normally would (for example via Docker, a system service, or local development server). The MCP server will be available through the plugin endpoint once Redmine is running.

5. Optional: configure any needed environment variables or plugin options within Redmine as required by your deployment.

Notes:

• This plugin is concept and experimental.
• It uses protocol version 2025-11-25.
• The HTTP endpoint does not require authentication.
• It does not support Server-Sent Events (Accept: text/event-stream).
• Features include: list_issues (all issues per project), list_wiki_pages (all wiki pages per project), read_issue (read a specific issue), and read_wiki_page (read a wiki page).
• See the MCP and Redmine references for compatibility and usage guidance. Environment considerations:
• Ensure the Redmine instance is reachable from the MCP server container or process.
• For production deployments, consider adding authentication at your gateway layer since this MCP server exposes data without internal auth.