Skip to main content
Glama
duytnb79

Backlog MCP Server

by duytnb79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      74 npm
      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.
      18 npm
      MIT

    • Backlog MCP Server

      nulab
      A
      license
      C
      quality
      A
      maintenance
      A Model Context Protocol server that enables Claude to interact with Backlog project management tools through API integration, allowing management of projects, issues, wiki pages and other Backlog resources.
      62
      6,379 npm
      235
      MIT

    • 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
      6,379 npm
      3
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions, such as get_issue vs. get_issue_comments or list_issues vs. list_pull_requests. There is no overlap or ambiguity that would cause misselection by an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as get_issue, list_projects, and read_notification. This predictability makes the set easy to navigate and understand.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing Backlog resources like issues, pull requests, projects, and notifications. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness3/5

    The toolset covers read operations comprehensively but lacks create, update, or delete actions for issues, pull requests, or comments, which are common in project management workflows. This creates notable gaps that agents might struggle with for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources