Skip to main content
Glama

Related Servers

Alternatives to tracker-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      This MCP enables access to Yandex Tracker issue management. Currently it supports all read operations to retrieve queues, issues and users from Yandex Tracker.
      55
      124
      Python
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.
      46 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Yandex Tracker through its API for managing tasks, comments, and attachments. It supports issue searching, status transitions, and metadata retrieval for automated project management.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Yandex.Tracker task management system through MCP protocol. Supports creating and managing issues, searching tasks, handling comments, managing projects and queues, and generating analytics reports.
      ISC
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to work with Yandex Tracker through its API, letting them search, create, edit, close, and bulk-manage issues, comments, checklists, time entries, attachments, queues, boards, dashboards, projects, and automation workflows. It also supports read-only mode for safe viewing integrations.
      187
      81 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: issue retrieval, attachment download, issue search, changelog retrieval, authentication status, and user lookup. The only nearby concepts, get_issue and get_issue_history, are explicitly separated by scope and pagination semantics.

    Naming Consistency4/5

    All tools use a consistent tracker_ prefix and snake_case, with mostly verb_noun names such as tracker_get_issue and tracker_search_issues. tracker_status is the minor deviation, being noun-only rather than verb-led.

    Tool Count5/5

    Six tools is well-scoped for a focused issue-tracker integration, covering core read, search, attachment, history, auth, and user-resolution workflows without redundant entries.

    Completeness3/5

    The server provides a solid read-only surface, including issue details, search, history, attachments, and user lookup. However, it lacks obvious lifecycle operations such as creating or updating issues, adding comments, and linking or transitioning issues, which limits full tracker workflows.