Skip to main content
Glama
Sign In
Backlog MCP Server

Backlog MCP Server

by nulab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • Backlog MCP Server

      TanLeJS
      -
      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.
      -

    • Redmine MCP Server

      snowild
      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

    • FV Backlog MCP Server

      fv-forgevision
      A
      license
      Not graded
      quality
      D
      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.
      6 npm
      MIT

    • Backlog MCP Server

      ducbachsong
      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.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2.6/5.0

    Scored across 64 tools

    Disambiguation4/5

    Most tools clearly target a distinct resource and action, such as get_issue vs. add_issue_comment vs. get_pull_request_comments. A few boundaries could still be confused, especially the mixed count/list tools and version/milestone operations like get_version_milestone_list vs. delete_version.

    Naming Consistency3/5

    The dominant pattern is verb_noun, but counting tools are inconsistent: count_issues, count_notifications, get_pull_requests_count, get_wikis_count, and get_watching_list_count all use different structures. There are also singular/plural mismatches such as get_git_repositories vs. get_git_repository and delete_version vs. the version_milestone naming elsewhere.

    Tool Count2/5

    64 tools is excessive for an MCP server even given Backlog's broad surface area. The set includes many narrow list/count variants, and the cognitive load is high for an agent selecting among them.

    Completeness3/5

    Core issue workflows are well covered, including CRUD, comments, related issues, watching, wiki, pull requests, and documents. However, notable gaps remain: documents lack update/delete and comment creation, several metadata resources are read-only, and wiki/project/pull-request deletion or merge operations are absent.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Resources