Skip to main content
Glama
sdamarketing

tracker-mcp

by sdamarketing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to tracker-mcp

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

    • 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

    • Yandex Tracker MCP Server

      Hollway
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely interact with Yandex Tracker, covering queues, issues, comments, worklogs, checklists, boards, sprints, attachments, and advanced query-language search. Supports OAuth 2.0 or static token authentication, optional Redis caching, and stdio, SSE, or HTTP transports.
      Apache 2.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.5/5.0

    Scored across 187 tools

    Disambiguation2/5

    Multiple tool pairs have unclear boundaries, especially issue-vs-entity duplicates (add_comment/add_entity_comment, get_issue_attachments/list_entity_attachments), pagination variants (get_boards/get_boards_paginate, get_users/get_users_relative), field scopes (get_issue_fields/get_queue_fields/get_queue_local_fields), access-vs-permission tools (get_entity_access/get_entity_permissions, update_entity_access/update_entity_permissions), and attachment upload routes (upload_temp_attachment vs upload_issue_attachment). Descriptions help somewhat, but with 187 tools an agent will likely misselect among these closely related options.

    Naming Consistency3/5

    Names are consistently snake_case and mostly verb-first (get_, create_, update_, delete_), but the set mixes synonymous verbs: get_ vs list_, create_ vs add_, and update_ vs edit_. These synonyms are semantic and readable, yet they break strict predictability across otherwise similar operations.

    Tool Count1/5

    187 tools is far beyond the 50+ threshold for extreme mismatch and creates enormous context and selection overhead for an agent. Even though the domain is broad, the surface should be consolidated or grouped to be practically usable.

    Completeness3/5

    Core issue, board, project, entity, comment, attachment, link, and workflow operations are well covered, but notable lifecycle gaps remain: no delete_issue, no update_queue, no delete for triggers/autoactions, no delete for statuses/priorities/resolutions/issue types, and incomplete dashboard/report management. These gaps will create dead ends for common administrative workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources