Skip to main content
Glama
nulab

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

    • FV Backlog MCP Server

      fv-forgevision
      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.
      5 npm
      MIT

    • Backlog MCP Server

      ducbachsong
      F
      license
      Not graded
      quality
      B
      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
    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.6/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools target a distinct Backlog resource/action, and the descriptions make each purpose fairly clear. However, clusters like get_space_activities vs get_user_recent_updates and get_watching_list_items vs get_notifications are conceptually close enough to create some misselection risk.

    Naming Consistency3/5

    The dominant get_/add_/update_/delete_ snake_case pattern is readable, but there are several inconsistencies: get_project_list vs get_users, count_issues vs get_wikis_count, delete_version vs update_version_milestone, and addDocument breaks the snake_case convention.

    Tool Count1/5

    62 tools is well beyond the 50+ threshold and creates an extreme navigation burden for an agent. Even though the Backlog API is broad, exposing every endpoint as a separate tool makes the set poorly scoped for MCP use.

    Completeness3/5

    Core workflows for projects, issues, wiki, pull requests, notifications, and watching are mostly covered. However, there are notable gaps such as no delete for wiki pages, documents, or comments, and document support is read/add only with no update or delete operations.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources