yandex-tracker-mcp
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.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Supports OAuth2/IAM/service accounts and includes token handling/refresh claims, plus optional Redis caching. However, provided docs emphasize env-var configuration without showing detailed guidance about token storage hygiene, log redaction, scope least-privilege granularity, or security posture for all transports.
⚡ Reliability
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.
Use Cases
- • AI-assisted triage and issue search in Yandex Tracker using the Tracker Query Language
- • Automating common issue operations (create, update fields, transitions, closing with resolutions)
- • Generating summaries from issue comments/worklogs/work metadata
- • Fetching queue/field/status metadata to help an assistant create valid issue payloads
- • Integrating Tracker data access into MCP-compatible clients (Claude Desktop, Copilot Chat, Cursor, etc.)
Not For
- • Public/anonymous use without strong authentication and tenant restrictions
- • Use as a general-purpose Yandex API proxy unrelated to Tracker
- • High-governance environments where you need provable least-privilege scopes/permission mapping and formally documented error/retry semantics
Interface
Authentication
Readme indicates OAuth2 with automatic refresh as an option to static API tokens, plus IAM and service account credential flows. Specific scope/permission mapping is not documented in the provided content.
Pricing
Pricing not described; this appears to be a self-hosted/open-source MCP server with your own Yandex Tracker usage costs.
Agent Metadata
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)
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for yandex-tracker-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.