Skip to main content
Glama
tmhr1850

Backlog MCP Server

by tmhr1850
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

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

    • bgl-mcp-server

      yuka-sakamaki777
      F
      license
      A
      quality
      D
      maintenance
      Enables users to interact with Backlog issues directly from VSCode/GitHub Copilot or Claude Desktop, providing tools to retrieve issues, list comments, and add comments.
      3
      -

    • 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.
      63
      3,586 npm
      237
      MIT

    • Redmine MCP Server

      StockLin
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Desktop and other MCP clients to browse projects and issues, create and update issues, log time, edit wiki pages, and read or save attachments on a self-hosted issue tracker through plain-language requests. It acts only with the user's own API permissions and asks for confirmation before destructive or bulk changes.
      MIT
    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 8 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting different resources: createIssue (create), getIssue (single read), getIssues (list read), getProjects (list), getSpaces (list), getUsers (list), getWebhooks (list), and getWikiPages (list). There is no ambiguity or overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with camelCase: createIssue, getIssue, getIssues, getProjects, getSpaces, getUsers, getWebhooks, and getWikiPages. The naming is predictable and readable throughout.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a Backlog server, covering core operations like issue management, project listing, and user retrieval. Each tool earns its place without being excessive or insufficient.

    Completeness3/5

    The server covers read operations extensively (get for issues, projects, spaces, users, webhooks, wiki pages) and create for issues, but lacks update and delete operations for issues, projects, or other resources. This creates notable gaps in CRUD coverage for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources