Skip to main content
Glama
nulab

Backlog MCP Server

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables AI agents to interact with Backlog API for managing projects, issues, wikis, Git repositories, and other Backlog features.
      -
    • A
      license
      B
      quality
      C
      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
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for interacting with the Backlog API, enabling AI agents to manage projects, issues, wikis, and more, with support for restricting access to a subset of Backlog projects.
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Backlog project management as tools for Claude Desktop, enabling search and management of issues, comments, wiki pages, milestones, custom fields, notifications, and more.
      -

    TDQS

    C2.7/5.0

    Scored across 63 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs, and singular/plural or list/count variants are usually explicit. The separate count tools overlap with list tools for the same resource, but this is unlikely to cause frequent misselection.

    Naming Consistency4/5

    The tool set mostly follows a snake_case verb_noun convention, but count operations alternate between count_x and get_x_count, and some list tools use inconsistent suffixes such as get_project_list versus get_pull_requests.

    Tool Count1/5

    With 63 tools, the server is far beyond a well-scoped set for a single MCP server. This extreme count likely reflects unnecessary granularity or tools that should be split into multiple servers.

    Completeness3/5

    The surface covers many Backlog resources, including issues, projects, wikis, documents, pull requests, notifications, watching, versions, and users. However, CRUD coverage is uneven: many resources lack delete operations, and documents lack update/delete entirely, creating notable gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive