Skip to main content
Glama
rubevg

Yandex Tracker MCP

by rubevg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Yandex Tracker MCP

No user-submitted related servers found.

    Related Servers

    • tracker-mcp

      sdamarketing
      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
      53 npm
      1
      MIT

    • Yandex Tracker MCP Server

      zolkinka
      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

    • YaTracker Connector

      Belkin-digital
      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

    • YouTrack MCP Server

      devstroop
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with JetBrains YouTrack 2025.2 for managing issues, sprints, dependencies, time tracking, and knowledge base content. Supports CRUD operations, bulk commands, analytics with Gantt charts and critical path analysis, and covers ~80% of the YouTrack REST API.
      8 npm
      52
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (issues, comments, checklist, worklogs, transitions, users). Minor overlap exists among get_user/search_users/list_users and between get_issue_time_report/get_time_report, but descriptions clarify the single-vs-search vs single-issue-vs-summary boundaries well.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_issue, create_issue, add_comment, delete_worklog, list_transitions). Verb choice (get/list/search/add/update/delete/execute) is used semantically and predictably throughout.

    Tool Count3/5

    With 30 tools this is heavier than the ideal 3-15 range, though the domain (issues, comments, checklist, worklogs, queues, fields, statuses, reports, transitions) is genuinely broad and most tools are distinct. Count sits borderline-heavy rather than clearly bloated.

    Completeness4/5

    Coverage is strong: issues (create/update/get/search), worklogs and checklist items (full CRUD), comments (list/add), plus metadata and reporting. Minor gaps remain—no comment update/delete and no issue delete—but core lifecycle workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources