mcp-name: io.github.aikts/yandex-tracker-mcp

包括的なモデルコンテキストプロトコル(MCP)サーバーで、AIアシスタントがYandex Tracker APIとやり取りできるようにします。このサーバーは、Yandex Trackerの問題、キュー、コメント、作業ログ、検索機能への安全で認証済みのアクセスを提供し、パフォーマンス向上のためのオプションのRedisキャッシュも備えています。

ロシア語の文書はこちらで入手可能です / Документация на русском языке доступна здесь。

特徴

• 完全なキュー管理:ページネーション対応、タグ取得、詳細なメタデータを備えた利用可能なYandex Trackerキューをすべてリストアップ・アクセス
• プロジェクト、ポートフォリオ、目標:Trackerの「entities」API内の各エンティティタイプに明示的なスキーマを持つ専用の読み書きツール(TRACKER_ENTITIES_ENABLED経由のオプトイン)
• ユーザー管理:ログイン情報、メールアドレス、ライセンス状況、組織データなどのユーザーアカウント情報を取得
• フルイシューライフサイクル:カスタムフィールド、添付ファイル、ワークフロートランジションをサポートしながら、イシューの作成、読み取り、更新、管理
• ステータスワークフロー管理:ステータス遷移の実行、問題解決の完了、複雑なワークフローのナビゲーション

Yandex Tracker MCP Server

mcp-name: io.github.aikts/yandex-tracker-mcp

A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with Yandex Tracker APIs. This server provides secure, authenticated access to Yandex Tracker issues, queues, comments, worklogs, and search functionality with optional Redis caching for improved performance.

Documentation in Russian is available here / Документация на русском языке доступна здесь.

Features

• Complete Queue Management: List and access all available Yandex Tracker queues with pagination support, tag retrieval, and detailed metadata
• Projects, Portfolios and Goals: Dedicated read and write tools with explicit schemas for each entity type in the Tracker “entities” API (opt-in via TRACKER_ENTITIES_ENABLED)
• User Management: Retrieve user account information, including login details, email addresses, license status, and organizational data
• Full Issue Lifecycle: Create, read, update, and manage issues with support for custom fields, attachments, and workflow transitions
• Status Workflow Management: Execute status transitions, close issues with resolutions, and navigate complex workflows
• Field Management: Access global fields, queue-specific local fields, statuses, issue types, priorities, and resolutions
• Boards and Sprints: List agile boards and their sprints to find sprint IDs for issue planning
• Advanced Query Language: Full Yandex Tracker Query Language support with complex filtering, sorting, and date functions
• Performance Caching: Optional Redis caching layer for improved response times
• Security Controls: Configurable queue access restrictions and secure token handling
• Multiple Transport Options: Support for stdio, SSE (deprecated), and HTTP transports for flexible integration
• OAuth 2.0 Authentication: Dynamic token-based authentication with automatic refresh support as an alternative to static API tokens
• Organization Support: Compatible with both standard and cloud organization IDs

Organization ID Configuration

Choose one of the following based on your Yandex organization type:

• Yandex Cloud Organization: Use TRACKER_CLOUD_ORG_ID env var later for Yandex Cloud-managed organizations
• Yandex 360 Organization: Use TRACKER_ORG_ID env var later for Yandex 360 organizations

You can find your organization ID in the Yandex Tracker URL or organization settings.