Skip to main content
Glama
onozaty

Redmine MCP Server

by onozaty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Redmine MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      20 npm
      MIT

    • Redmine MCP Server

      snowild
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude Code to directly interact with Redmine project management systems, supporting issue management, project operations, and search features.
      22
      9
      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

      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

      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

    C2.3/5.0

    Scored across 90 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but there are notable overlaps: getMyAccount and getCurrentUser appear to serve the same purpose, and addRelatedIssue/removeRelatedIssue overlap with createIssueRelation/deleteIssueRelation. The attachment upload/download tools also come in pairs differentiated only by input/output format, which could cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent camelCase verb+noun pattern (e.g., deleteIssue, getProjects, createTimeEntry). Derived operations like addWatcher, removeWatcher, and uploadAttachmentFromLocalFile maintain the same style. The few exceptions (getNewsList, getVersions) are minor and still readable within the pattern.

    Tool Count2/5

    At 90 tools, this is far beyond the typical 3-15 range. While the Redmine API is broad, the sheer number makes the tool surface unwieldy for an agent to navigate efficiently. Many tools could be consolidated or made optional, and the count borders on excessive for a usable MCP server.

    Completeness5/5

    The tool set covers nearly every major Redmine resource: issues, projects, users, time entries, news, relations, versions, wiki, attachments, plus configuration entities like statuses, trackers, roles, groups, and custom fields. The lifecycle (CRUD) is complete for most resources, and even advanced operations like archiving projects, adding users to groups, and uploading/downloading attachments are included.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources