Redmine MCP Server

Created By
zacharyelstona year ago
A Model Context Protocol (MCP) server that enables AI assistants to interact with Redmine for focused and transparent project management.
Overview

what is Redmine MCP Server?

Redmine MCP Server is a Model Context Protocol (MCP) server that facilitates interaction between AI assistants and Redmine, enhancing project management through focused and transparent processes.

how to use Redmine MCP Server?

To use the Redmine MCP Server, clone the repository, install the required dependencies, configure the server with your Redmine URL and API key, and run the server. You can also deploy it using Docker for easier management.

key features of Redmine MCP Server?

  • Issue Management: Create and update issues with proper categorization.
  • Wiki Management: Manage wiki pages for documentation.
  • Project Tracking: Track project status and progress with defined processes.
  • API Endpoints: Access various MCP and resource endpoints for seamless integration.

use cases of Redmine MCP Server?

  1. Automating issue creation and updates in Redmine.
  2. Managing project documentation through AI assistants.
  3. Tracking project progress and status updates efficiently.

FAQ from Redmine MCP Server?

  • Can I use Redmine MCP Server with any AI assistant?

Yes! It is compatible with any MCP-compatible AI assistant like Claude Desktop.

  • Is there a specific Redmine version required?

The server requires a Redmine instance with API access, but no specific version is mandated.

  • How do I deploy the server?

You can deploy it by running the server directly or using Docker for containerized deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zacharyelston
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago