Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

by GonzaloRando03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Redmine MCP Server

No user-submitted related servers found.

    Related Servers

    • redmine-mcp

      yenpu
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server providing 63 tools to interact with Redmine instances, covering issues, projects, time entries, and wiki pages. It utilizes streamable HTTP transport and supports per-client authentication for secure management of Redmine resources.
      6 npm
      -

    • mcp-redmine

      beborico1
      F
      license
      A
      quality
      D
      maintenance
      MCP server for Redmine that lets coding agents read and write Redmine: search issues, view histories, comment, log time, browse wiki, and download attachments. Enforces explicit user permission for any write operations.
      18
      1
      -

    • Redmine MCP Server

      sba1966
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides an MCP server for interacting with Redmine's REST API, enabling LLMs to manage issues, projects, users, and time entries.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 89 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes due to descriptive names and detailed descriptions. However, the large number (89) introduces some potential overlaps, such as multiple ways to list/filter issues (list_issues, list_issues_by_sprint, search, search_in_project) and get_issue_agile_data vs get_issue. These could cause misselection if descriptions are not carefully read.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (e.g., create_issue, list_projects, update_user). The verbs are well-chosen and indicate the action clearly. There are very few deviations (e.g., create_or_update_wiki_page), and overall the pattern is predictable and uniform.

    Tool Count3/5

    With 89 tools, the count is high for a single server, but it reflects the broad scope of Redmine's functionality (multiple entities, CRUD, Agile plugin, etc.). While each tool serves a specific purpose, the server could benefit from consolidation (e.g., merging some list/get tools). The count is borderline excessive but not unreasonable for the domain.

    Completeness4/5

    The tool set covers CRUD operations for most Redmine entities (projects, issues, users, groups, versions, news, wiki, time entries, etc.) and includes specialized operations like agile sprints and file uploads. Minor gaps exist (e.g., no direct custom field value management, no workflow transitions), but overall the surface is comprehensive for typical use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources