Redmine OAuth

Name: Redmine OAuth
Author: tuzumkuru

•

Provides a centrally-deployed server for Redmine with OAuth 2.0 authentication, enabling Model Context Protocol (MCP) clients to interact with Redmine without per-user API key setup.

Redmine OAuth

bytuzumkuru

•

Herramientas de Colaboración

Productividad y Flujo de Trabajo

Desarrollo de API

Provides a centrally-deployed server for Redmine with OAuth 2.0 authentication, enabling Model Context Protocol (MCP) clients to interact with Redmine without per-user API key setup.

This tool acts as a secure intermediary, connecting MCP clients to a Redmine instance using OAuth 2.0. It eliminates the need for individual API keys or complex per-user configurations by deploying a central server that handles Redmine authorization. Users simply grant access via Redmine's OAuth flow, and the server manages the access tokens, never exposing them to the client. This setup provides access to various Redmine functionalities, including fetching issue details, searching issues, listing projects, and managing time entries, all through the familiar MCP interface.

Características Principales

013 GitHub stars

02OAuth 2.0 authentication with Redmine

03Centralized deployment for all MCP clients

04Server-side Redmine OAuth token management (JWT issued to client)

05Access to Redmine issues, projects, time entries, and more

06Docker support for easy deployment

Casos de Uso

01Integrating Redmine with AI assistants or other MCP-compatible clients for automated task management

02Providing a unified and secure interface for developers and project managers to access Redmine data through MCP tools

03Streamlining Redmine interactions for teams by centralizing authentication and eliminating per-user API key management