Skip to main content
Glama
imdeniil

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ya-tracker-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-tracker-mcp

      brekhov-ilya
      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.
      45 npm
      1
      MIT

    • Yandex Metrika MCP

      theYahia
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Yandex.Metrica API providing 15 tools for managing counters, goals, reports, logs, traffic sources, and top pages with OAuth Bearer token authentication.
      15
      46 npm
      1
      MIT

    • yandex-mcp

      SvechaPVL
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.
      59
      MIT

    • yougile-mcp

      nebelov
      A
      license
      A
      quality
      F
      maintenance
      MCP server for YouGile project management. Provides 57 tools covering 100% of YouGile API v2, enabling natural language management of projects, boards, columns, tasks, chats, users, and more.
      57
      29 npm
      10
      MIT

    • Yandex Tracker MCP

      aikts
      A
      license
      A
      quality
      A
      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
      119
      Python
      Apache 2.0

    • ya360-mcp

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

    TDQS

    C2.7/5.0

    Scored across 135 tools

    Disambiguation3/5

    With 135 tools, many have overlapping purposes (e.g., create_issue, import_issue, create_from_preset; list_links vs. list_external_links). The entity-prefixed naming (issue vs. entity) helps, but the sheer volume and subtle differences (e.g., sync_directory vs. sync_all_directories) create ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_*, get_*, create_*, update_*, delete_*). Exceptions like issue_changelog, queue_overview, and bulk_list_links break the pattern but are still readable and predictable.

    Tool Count1/5

    At 135 tools, this is an extreme mismatch for an MCP server, far exceeding the 50+ threshold. Even for a full-featured API, this is overwhelming and likely to confuse agents.

    Completeness3/5

    Covers a broad domain: issues, queues, entities, boards, sprints, components, filters, dashboards, macros, triggers, and more. However, notable gaps exist: sprints have only list/create (no update/delete), dashboards only create, and components lack delete. Some resources have unbalanced CRUD, so it's not fully complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources