Skip to main content
Glama

Related Servers

Alternatives to backlog-mcp

No user-submitted related servers found.

    Related Servers

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

    TDQS

    A4.2/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: retrieving projects, issue lists, single issues, comments, attachments, metadata, and exporting context. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'backlog_verb_noun' pattern (e.g., backlog_get_issue, backlog_download_attachment, backlog_export_issue_context). The naming is uniform and predictable.

    Tool Count5/5

    With 12 tools, the server covers all necessary read and export operations for Backlog without being bloated. Each tool serves a specific purpose within the domain.

    Completeness5/5

    The tool set provides comprehensive read and export capabilities for Backlog issues, including metadata retrieval, issue listing, comments, attachments, and full context export. There are no obvious gaps for its intended read-only scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues