Skip to main content
Glama
snowild

Redmine MCP Server

by snowild
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Redmine MCP Server

No user-submitted related servers found.

    Related Servers

    • redmine-mcp

      dokkiitech
      A
      license
      B
      quality
      B
      maintenance
      MCP server to operate self-hosted Redmine from Claude Code, enabling project and issue management, search, and metadata retrieval via natural language.
      24
      MIT

    • Redmine MCP Server

      yonaka15
      A
      license
      Not graded
      quality
      F
      maintenance
      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.
      78
      MIT

    • Redmine MCP Server

      compasify
      A
      license
      C
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for Redmine that provides comprehensive access to the Redmine REST API, enabling users to operate Redmine from MCP clients such as Claude Desktop.
      90
      7 npm
      MIT

    • Redmine MCP Server

      onozaty
      A
      license
      C
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Redmine that provides comprehensive access to the Redmine REST API. It allows you to operate Redmine from MCP clients such as Claude Desktop.
      90
      624 npm
      28
      MIT

    • mcp-redmine

      mejtyas
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to interact with Redmine projects, issues, time tracking, and members through natural language via the Model Context Protocol.
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have distinct purposes focused on Redmine's core issue management workflow, with clear separation between CRUD operations, listing, and metadata retrieval. However, there is some potential overlap between 'update_issue_content' and 'update_issue_status' as both modify issues, though their scopes are differentiated by content vs. status changes.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with clear verb_noun structure throughout (e.g., 'create_new_issue', 'get_issue', 'list_users', 'update_issue_status'). The naming convention is predictable and readable across all 22 tools.

    Tool Count3/5

    With 22 tools, the count feels heavy for a Redmine server, though it covers extensive functionality. While comprehensive, it borders on being overwhelming compared to typical well-scoped servers (3-15 tools), suggesting some tools could potentially be consolidated or omitted.

    Completeness5/5

    The toolset provides complete coverage for Redmine's issue management domain, including full CRUD operations for issues (create, get, update, close), comprehensive listing and search capabilities, user management, project access, and metadata retrieval for statuses, priorities, and trackers. No obvious gaps exist for core workflows.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources