Skip to main content
Glama
jootsuki

Backlog MCP Server

by jootsuki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • Backlog MCP Server

      fleagne
      A
      license
      B
      quality
      Not graded
      maintenance
      An MCP server implementation that integrates with Backlog API, enabling project management operations including issues, projects, and wikis through natural language interactions.
      12
      7,061 npm
      3
      -

    • 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.
      3 npm
      MIT

    • Backlog MCP Server

      duytnb79
      A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server that enables users to retrieve and interact with Backlog projects, issues, pull requests, and notifications. It provides a secure way to query Backlog data through natural language using tools like Claude Desktop.
      10
      5 npm
      MIT

    • Jira MCP Server

      AlexVulaj
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for integrating with Jira Server instances, enabling natural language interactions to create, update, search, and manage issues and comments.
      30 npm
      1
      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.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getIssue retrieves a specific issue, getProjects lists projects, searchIssues finds issues based on criteria, and updateIssue modifies an issue. There is no overlap or ambiguity between these functions.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., getIssue, getProjects, searchIssues, updateIssue), with all tools using camelCase. The only minor deviation is that 'getProjects' uses a plural noun while others use singular, but this is still readable and predictable.

    Tool Count3/5

    With only 4 tools, the set feels thin for a Backlog server, as it lacks essential operations like creating issues or projects, deleting resources, or managing comments. While the tools cover basic retrieval and update, the scope is incomplete for typical issue-tracking workflows.

    Completeness2/5

    There are significant gaps in the tool surface for a Backlog server. Missing operations include create_issue, delete_issue, create_project, and update_project, which are core to issue lifecycle management. This will likely cause agent failures when trying to perform full CRUD operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources