Skip to main content
Glama
DChuhin

Yandex Tracker MCP Server

by DChuhin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Yandex Tracker MCP Server

No user-submitted related servers found.

    Related Servers

    • Yandex Tracker MCP

      rubevg
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to read and manage issues, comments, checklists, worklogs, queues, users, metadata, and time reports through the Yandex Tracker REST API v3, requiring user confirmation before data-changing operations.
      30
      MIT

    • 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

    • tracker-mcp

      sdamarketing
      A
      license
      Not graded
      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.
      0
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose. Checklist operations are separated into add, list, update, delete, and clear. Issue operations are similarly granular. Even similar tools like search_issues and search_issues_scroll are differentiated by scroll capability, leaving no ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., add_checklist_item, list_components, update_issue). The naming is predictable and uniform across the entire set.

    Tool Count5/5

    With 21 tools, the server covers the typical lifecycle of an issue tracker: CRUD for issues and checklists, search, linking, comments, sprints, components, validation, and Miro sync. The count is well-scoped for the domain without being too sparse or excessive.

    Completeness4/5

    The tool surface covers most essential operations: issue creation, retrieval, update, checklist management, linking, commenting, validation, and sprint/component listing. Minor gaps exist, such as no tool for deleting an issue or removing a link, but these are not critical dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources