{"id":"aikts-yandex-tracker-mcp","name":"yandex-tracker-mcp","af_score":56.8,"security_score":66.0,"reliability_score":36.2,"what_it_does":"Provides an MCP server that lets AI assistants interact with Yandex Tracker: queue and field metadata, searching, and full issue lifecycle (read/create/update/transition/close), with optional Redis caching and OAuth2-based authentication and token refresh. Supports multiple transports including stdio, SSE (deprecated), and HTTP.","best_when":"When you want an MCP-native integration for Yandex Tracker workflows inside an AI client, and you can supply secure OAuth/IAM credentials plus the correct organization ID.","avoid_when":"When you cannot safely manage OAuth tokens/service account secrets via env vars, or when you require a clearly documented rate-limit and retry/error contract for automated agents.","last_evaluated":"2026-03-30T15:20:54.254683+00:00","has_mcp":true,"has_api":false,"auth_methods":["TRACKER_TOKEN (OAuth token)","TRACKER_IAM_TOKEN (IAM token)","Service account credentials: TRACKER_SA_KEY_ID, TRACKER_SA_SERVICE_ACCOUNT_ID, TRACKER_SA_PRIVATE_KEY"],"has_free_tier":false,"known_gotchas":["Writes (create/update/transition/close) may not be idempotent; agents should avoid repeated calls after timeouts without explicit idempotency support","Queue restrictions are enforced via configuration (TRACKER_LIMIT_QUEUES); agents may appear to 'miss' resources if limits are misconfigured","Transport choice matters (SSE is deprecated); ensure your MCP client supports the configured transport (stdio recommended in examples)"],"error_quality":0.0}