Skip to main content
Glama
APonkratov

Yandex Tracker MCP Server

by APonkratov

Related Servers

Alternatives to Yandex Tracker MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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.
      44 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js MCP server that enables AI assistants to interact with Yandex Tracker task management system through a standardized protocol, supporting operations like creating, updating, and searching issues.
      433 npm
      3
      ISC
    • A
      license
      A
      quality
      A
      maintenance
      An unofficial MCP server that enables AI assistants to work with Yandex Tracker, Yandex Mail, and Yandex Calendar on the user's behalf, supporting reading, writing, and workflow automations such as meeting follow-ups, standups, and email-to-task creation.
      2
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for YouTrack integration, providing a standardized interface for LLMs to interact with YouTrack's issue tracking, agile management, and knowledge base features.
      12
      36 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Simple Model Context Protocol server that enables AI assistants to interact with Jira, allowing operations like fetching tickets, adding comments, and updating ticket status.
      1
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 57 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear descriptions that prevent confusion. Even the overlapping issue_close and issue_execute_transition are clearly distinguished as convenience vs generic transition.

    Naming Consistency2/5

    Naming is inconsistent: many tools use resource_action (issue_create, queue_get_metadata) but several use action_resource (get_priorities, get_statuses). Also pluralization varies (boards_list vs board_get, queues_get_all vs queue_get_metadata).

    Tool Count1/5

    With 57 tools, this is far beyond the typical well-scoped MCP server. While the domain is broad, the granularity is excessive, making it unwieldy.

    Completeness4/5

    The tool surface covers most CRUD operations for issues, comments, worklogs, attachments, links, and entities. Minor gaps include no filter deletion, board/sprint creation/update, and limited issue search options.

    Maintenance

    ActivityStale
    ResponsivenessNo issues